# Bridge Published articles for Bridge. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Our Transition to React Native DevFeed: [Our Transition to React Native]() Original publisher: [Read original article]() Author: Khan Academy Published: 2020-07-09T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [React Native](), [Android](), [iOS](), [Mobile](), [React]() Tags: [android](), [android-apps](), [architectures](), [backend](), [bridge](), [business-logic](), [change](), [code](), [engineering](), [ios](), [mobile](), [news](), [react-native]() ### AI overview Khan Academy describes completing its transition to React Native for its iOS and Android apps. The article explains why the team moved away from separate platform codebases and outlines the transition's exploration, straddling, and extinction phases. ### Source excerpt In 2017, Khan Academy started using React Native in our iOS and Android apps. As of this year, we've reached a big milestone: our transition to React Native is complete! Every screen in the app is rendered in React Native. ## ML based ranking using Nrtsearch DevFeed: [ML based ranking using Nrtsearch]() Original publisher: [Read original article]() Author: Mohammad Mohtasham (Software Engineer); Tao Yu (Software Engineer) Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [Inference](), [Scalability](), [Latency](), [recommendation systems](), [Open Source]() Tags: [bridge](), [inference](), [machine-learning](), [overhead](), [performance](), [pipeline](), [scalability](), [service]() ### AI overview Yelp's Nrtsearch Inference Plugin embeds machine-learning ranking directly in the search layer. The article explains the scoring workflow, including model configuration, feature extraction, candidate ranking, and application-specific business logic. It describes how co-locating feature storage and inference reduces network transfer, serialization overhead, and latency compared with a standalone inference service. ### Source excerpt We've extended Nrtsearch with the Inference Plugin, which embeds ML-based ranking directly in the search layer -- eliminating the need for a standalone scoring service. We use Nrtsearch (read more information on the blog post), a Lucene-based open-source search engine built by Yelp, to power a variety of applications such as business search, reviews search, ad delivery and photo search. In this blog post, we give a high-level overview of the Machine Learning (ML) based scoring workflow in Nrtsearch. We'll show how ML models are configured and loaded, and how different applications use custom business logic to develop, test, and... ## Rootless Podman: Preserving Source IPs DevFeed: [Rootless Podman: Preserving Source IPs]() Original publisher: [Read original article]() Author: Jan Rodak Published: 2026-09-04T14:25:02Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [Containers](), [Networks](), [Access Control](), [Logging]() Tags: [blog](), [bridge](), [container](), [containers](), [ipv4](), [ipv6](), [logging](), [networks](), [podman](), [port](), [rate-limiting](), [routing](), [tips-and-tricks]() ### AI overview This article explains how Pesto, a companion tool from the passt project, addresses Rootless Podman's inability to preserve incoming client source IPs on bridge networks. Pesto updates pasta's forwarding table so traffic reaches containers without source-address rewriting, while retaining existing port-mapping capabilities. The article also documents configuration steps, traffic flow, supported networking features, and limitations when switching from the current forwarder. ### Source excerpt Rootless Podman has a long-standing limitation reported since 2020: containers on bridge networks can't see the real source IP of incoming connections. The `rootlessport` userspace proxy rewrites the source to the container's own subnet address, breaking IP-based access control, logging, and rate limiting. Pesto, a new companion tool from the passt project solves this. Pesto [...] ## Migrating Doximity's iOS Newsfeed to SwiftUI Without Disrupting Users or Development DevFeed: [Migrating Doximity's iOS Newsfeed to SwiftUI Without Disrupting Users or Development]() Original publisher: [Read original article]() Author: Doximity Published: 2026-09-04T10:50:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [iOS](), [SwiftUI](), [Development](), [App]() Tags: [app](), [architecture](), [bridge](), [development](), [incremental](), [ios](), [migration](), [swiftui]() ### AI overview This article describes Doximity's incremental migration of its iOS Newsfeed from UIKit to SwiftUI. The team moved one section at a time, kept UIKit and SwiftUI compatible, continuously measured behavior, and made each step reversible. The feed's server-driven card and section architecture, with state and logic managed in The Composable Architecture, provided the migration boundary. ### Source excerpt The Newsfeed is one of the most-used features in the Doximity iOS app. It is the first thing many users see when they open the app. For doctors checking in between patients or residents catching up during a break, it has to be fast and efficient. Those expectations defined success for the migration. Feature work had to continue, analytics had to remain reliable, and the experience had to remain familiar to users even as the underlying implementation changed. We approached the migration less like a rewrite and more like a controlled rollout. We moved one section at a time, kept the UIKit and SwiftUI implementations compatible, measured behavior continuously, and made each step reversible. The technical bridge enabled the migration, but this incremental approach reduced the risk to the product. The Newsfeed brings several types of content together in a single scrolling experience. Here are a few examples of the different cards users may encounter: The Architecture Behind the Newsfeed Before discussing the migration, it helps to understand the architecture that made our incremental approach possible. The Newsfeed is not one large custom view. It is a server-driven list built from cards, with each card assembled from smaller sections. The server controls the composition of the feed. It tells the app which cards should appear, which sections belong inside each card, and the order in which those sections should render. The iOS app owns the rendering and behavior of each known section type. This separation makes the feed flexible. Rather than relying on a fixed set of hardcoded card types, the server can compose cards from reusable sections such as headlines, authors, summaries, media, polls, and social actions. By combining and ordering those sections differently, the server can create different card layouts without requiring a new implementation in the app. This is roughly what the model looks like: Server-driven feed response Newsfeed ├─ Card │ ├─ Section: author │ ├─ S ## Networking Aspects of Running VMs in Containers DevFeed: [Networking Aspects of Running VMs in Containers]() Original publisher: [Read original article]() Published: 2026-09-02T05:44:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Containers](), [virtualization](), [networking](), [Linux](), [Orchestration]() Tags: [bridge](), [containers](), [docker](), [ethernet](), [linux](), [netlab](), [networking](), [podman](), [qemu](), [virtual-machines](), [virtualization]() ### AI overview The article explains how vrnetlab and a containerlab fork package virtual machines, especially network devices, as containers so container orchestration can provision network topologies. It focuses on connecting QEMU virtual network interfaces, Linux tap interfaces, bridges, and container veth pairs, including why data-plane and management interfaces require different handling. ### Source excerpt The vrnetlab project and its containerlab fork implement a wonderful idea: let's package virtual machines (primarily network devices that cannot be containerized) as containers to use reliable orchestration tools like containerlab to provision network topologies. That approach might have a few drawbacks (depending on how the container images are built), but the obvious elephant in the room is: how do you make the virtual network plumbing work? Read more ... ## Build connected lighting systems with the ESP DALI component DevFeed: [Build connected lighting systems with the ESP DALI component]() Original publisher: [Read original article]() Author: John Lee Published: 2026-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Espressif](), [Embedded Software Dev](), [Internet of things](), [Protocol (disambiguation)](), [API](), [Matter](), [Home Assistant]() Tags: [api](), [architecture](), [blog](), [bridge](), [caching](), [dali](), [esp-idf](), [esp-iot-solution](), [espressif](), [firmware](), [lighting](), [matter](), [mqtt](), [ota](), [security]() ### AI overview This tutorial introduces the ESP DALI component, which implements an IEC 62386 master on Espressif SoCs using the RMT peripheral. It covers DALI control, commissioning, sensors, DT8 color gear, and a Matter-to-DALI bridge. ### Source excerpt The ESP DALI component implements an IEC 62386 master on the RMT peripheral, with support for commissioning, dimming, color control, sensors, and Matter-to-DALI bridges. ## Migrating Live Enterprise SCIM Directories to WorkOS with SCIM Bridge DevFeed: [Migrating Live Enterprise SCIM Directories to WorkOS with SCIM Bridge]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-14T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [migration](), [Provisioning]() Tags: [architecture](), [bridge](), [database](), [migration](), [okta](), [provisioning](), [proxy](), [rollback]() ### AI overview The article presents SCIM Bridge, a reversible migration proxy for moving live enterprise directories from a home-grown SCIM endpoint to WorkOS Directory Sync. It describes dual-writing, backfilling, verification, staged authority, and rollback before final cutover. ### Source excerpt How SCIM Bridge moves live enterprise directories onto WorkOS Directory Sync with zero downtime, staged authority, and lossless rollback until the last step. ## Chat SDK adds Novu support DevFeed: [Chat SDK adds Novu support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-06-22T14:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Command-line interface](), [Microsoft Teams](), [Slack]() Tags: [agent](), [bridge](), [channel](), [cli](), [documentation](), [identity](), [mapping](), [microsoft-teams](), [oauth](), [sdk](), [slack](), [support](), [telegram](), [tokens](), [whatsapp]() ### AI overview Chat SDK adds Novu support through a vendor-official adapter, allowing one handler set to connect agents to Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu manages credentials, identity, delivery, OAuth, and tokens, while a CLI command configures a channel and adds its credentials to the project. ### Source excerpt Chat SDK now supports Novu with the new vendor-official adapter. One handler set puts your agent on Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu handles credentials, identity, and delivery, keeping OAuth and tokens outside your app and mapping each channel to one user. Your agent always knows who they're talking to. Your agent can also send proactive notifications and handle the replies in the same loop, on whichever channel the customer used. One CLI command connects a real channel to your agent: It signs you in, creates a bridge agent, sets up the channel you pick (e.g., Slack), and adds the credentials to your project. Read the Novu documentation to get started. Read more ## Ethereum Interop Layer proposal aims to unify cross-L2 transactions DevFeed: [Ethereum Interop Layer proposal aims to unify cross-L2 transactions]() Original publisher: [Read original article]() Author: Yoav Weiss; Account; Chain Abstraction Team Published: 2025-11-18T00:00:00Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [interoperability](), [Protocol (disambiguation)](), [Transactions](), [Security]() Tags: [bridge](), [complexity](), [ethereum](), [interoperability](), [protocol](), [research-development](), [security](), [transactions]() ### AI overview This proposal from Ethereum's Account Abstraction team introduces the Ethereum Interop Layer (EIL), which aims to make rollups feel like a unified chain. It describes signing once for cross-L2 transactions while preserving self-custody, censorship resistance, and verifiable onchain execution without adding new trust assumptions. ### Source excerpt Disclaimer: The following blog is a proposal from the Account Abstraction team. Content may not imply consensus views, and the EF is a broad organization that includes a healthy diversity of opinion across Protocol and beyond that together strengthen Ethereum. Since the early days of Ethereum, the promise has... ## ESPHome 2025.10.0: Z-Wave Proxy and Arduino as an IDF component DevFeed: [ESPHome 2025.10.0: Z-Wave Proxy and Arduino as an IDF component]() Original publisher: [Read original article]() Author: Jesse Hills Published: 2025-10-15T00:00:00Z Content type: release Language: en Sources: [ESPHome - Smart Home Made Simple - Blog]() Topics: [ESP32](), [ESP-IDF](), [Home Assistant](), [Security](), [Architecture & Design](), [Ethernet](), [Low Latency]() Tags: [2025](), [api-security](), [architecture](), [bridge](), [communication](), [connectivity](), [esp-idf](), [esp-idf-component](), [esp32](), [ethernet](), [framework](), [hardware](), [home-assistant](), [latency](), [low-latency](), [memory](), [network](), [new-features](), [performance](), [releases](), [security]() ### AI overview ESPHome 2025.10.0 adds a Z-Wave Proxy for connecting Z-Wave hardware to Z-Wave JS over Wi-Fi or Ethernet, changes ESP32 Arduino builds to use Arduino as an ESP-IDF component, and introduces a unified SPI ePaper component. The release also includes OTA and API security hardening, memory optimizations, API improvements, and new temperature sensor components. ### Source excerpt ESPHome 2025.10.0 adds the Z-Wave Proxy component, rebuilds ESP32 Arduino builds on top of ESP-IDF, introduces a unified SPI ePaper component, and hardens OTA and API security. ## Deploy a Spin Application to Send Azure Monitor Alerts to Slack DevFeed: [Deploy a Spin Application to Send Azure Monitor Alerts to Slack]() Original publisher: [Read original article]() Author: Kate Goldenring Published: 2025-09-18T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Azure](), [Slack](), [notifications](), [monitor](), [App]() Tags: [application](), [azure](), [bridge](), [deploy](), [monitor](), [notifications](), [slack]() ### AI overview A tutorial on deploying a Spin application that transforms Azure Monitor alerts into formatted Slack notifications. ### Source excerpt Deploy a Spin application that transforms Azure Monitor alerts into beautifully formatted Slack notifications ## netlab 2.0: Routers, Hosts, Gateways and Bridges DevFeed: [netlab 2.0: Routers, Hosts, Gateways and Bridges]() Original publisher: [Read original article]() Published: 2025-06-11T06:20:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Network architectures](), [Routing (disambiguation)](), [BGP](), [Cisco](), [Containers](), [Test coverage]() Tags: [bgp](), [bridge](), [cisco](), [container](), [netlab](), [network](), [router](), [routing](), [test-coverage]() ### AI overview The article explains how netlab 2.0 models routers, hosts, gateways, and bridges in network topologies. It describes their forwarding behavior, loopback interfaces, routing choices, IPv6 router advertisements, VLAN support, and possible uses of Cisco IOS, Arista EOS, BGP, and container-based devices. ### Source excerpt In a previous blog post, I explained how you can use bridges in a netlab topology to create custom LAN segments. Netlab supports two other node roles (host and router), and we'll eventually add gateways. netlab assumes that most network devices are routers (it considers a firewall to be a router in disguise), apart from Linux hosts, but you can always change what a node is with the role node attribute: Read more ... ## Switching, Routing, and Bridging Terminology DevFeed: [Switching, Routing, and Bridging Terminology]() Original publisher: [Read original article]() Published: 2025-04-25T05:45:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Routing (disambiguation)](), [Network]() Tags: [bridge](), [network](), [networking](), [networking-fundamentals](), [router](), [routing](), [switching]() ### AI overview This article explains networking terminology for moving packets across a network. It distinguishes forwarding, switching, routing, and bridging, describes hubs, bridges, and routers, and introduces different forwarding paradigms, including virtual circuits and segment routing. ### Source excerpt After discussing networking layers and addressing, it's time to focus on moving packets across a network. Vendors love to use ill-defined terms like switching instead of forwarding, routing, or bridging, so let's start with the terminology. Connecting all relevant devices to a single cable would indubitably simplify any networking stack, but unfortunately, we're almost never that lucky. We need devices in the network (typically with multiple interfaces) that perform packet forwarding between end nodes. Read more ... ## Bridging Compose and View: Seamless Interop Communication with CompositionLocal DevFeed: [Bridging Compose and View: Seamless Interop Communication with CompositionLocal]() Original publisher: [Read original article]() Author: Julien Salvi Published: 2025-03-05T13:42:13Z Content type: tutorial Language: en Sources: [Stories by Julien Salvi on Medium]() Topics: [Compose](), [interoperability](), [Dependency injection](), [ui]() Tags: [android](), [android-development](), [androiddev](), [bridge](), [compose](), [dependency-injection](), [interface-implementation](), [interoperability](), [jetpack-compose](), [sharedflow](), [stateflow](), [ui](), [viewmodel]() ### AI overview This tutorial explains how to bridge Jetpack Compose and traditional Android Views using CompositionLocal. It shows how to provide a FeedbackMessageInterop implementation so composables can trigger View-based feedback, and describes the reverse direction through an interface and reactive streams such as StateFlow or SharedFlow. ### Source excerpt Migrating to Compose exposed the team to several interoperability challenges as we integrated new Composables into our existing codebase. One key hurdle was figuring out how to trigger events from Compose and dispatch them to the main View holder, such as a Fragment or Activity. After some exploration, we found an efficient solution using CompositionLocal. Here's how we made it work! 🚀 What is a CompositionLocal? Think of CompositionLocal as a localized dependency injection system built directly into Compose's composition model. You create a CompositionLocal instance, which acts as a key for a specific type of data. Then, using the CompositionLocalProvider, you define a scope within your UI tree and associate a value with that CompositionLocal key. Any composable within that scope can then access the provided value using the CompositionLocal.current property, without needing to know where the value originated. This not only simplifies code but also makes it more maintainable and reusable. Furthermore, CompositionLocal values can be dynamic, triggering recomposition when they change, and they are thread-safe, making them a powerful tool for managing shared state within your Compose UI. Interop Communication with CompositionLocal In the following code, LocalFeedbackInterop is a staticCompositionLocalOf that will hold an implementation of the FeedbackMessageInterop interface. This interface defines the methods for showing feedback alerts, and the staticCompositionLocalOf ensures that the implementation is unlikely to change as it cannot be re-provided. This allows any composable within the scope to access the FeedbackMessageInterop implementation and trigger feedback messages without explicit dependencies. import androidx.compose.runtime.ProvidableCompositionLocal import androidx.compose.runtime.staticCompositionLocalOf val LocalFeedbackInterop: ProvidableCompositionLocal = staticCompositionLocalOf { null } interface FeedbackMessageInterop { fu ## Weekend Wireless Wizardry DevFeed: [Weekend Wireless Wizardry]() Original publisher: [Read original article]() Author: Techno Tim Published: 2024-11-22T13:00:00Z Content type: article Language: en Sources: [Techno Tim]() Topics: [Ubiquiti](), [Network](), [Hardware]() Tags: [bridge](), [devices](), [hardware](), [homelab](), [network](), [ubiquiti](), [upgrade](), [video](), [wi-fi]() ### AI overview A three-day video documents a wireless upgrade using Ubiquiti devices, including the UniFi U7 Outdoor, UniFi Device Bridge, and UniFi Device Bridge Pro. It evaluates what works while extending home Wi-Fi range and improving a wireless bridge to a garage. ### Source excerpt This is how my weekends usually go... 📺 Watch Video Disclosures Ubiquiti devices were provided for testing and upgrading my existing devices, which is why you see the sponsored banner. I was not paid. Info This video follows my wireless upgrade adventure over 3 days. I try to figure out what works, what doesn't, and how to extend the range of my home Wi-Fi while trying to improve the... ## Coppercomm -- One interface to unite them all DevFeed: [Coppercomm -- One interface to unite them all]() Original publisher: [Read original article]() Author: Kenneth Karlsson Published: 2024-05-27T06:54:56Z Content type: tutorial Language: en Sources: [Volvo Cars Engineering - Medium]() Topics: [interfaces](), [Testing](), [Python](), [Library](), [ssh](), [Wireless Debugging]() Tags: [adb](), [bridge](), [communication](), [interfaces](), [libraries](), [open-source](), [python](), [ssh](), [test](), [testing]() ### AI overview The article introduces Coppercomm, a Python-based bridge intended to let teams share and rerun the same test cases across organizations. It maps logical or physical interfaces to communication methods such as SSH, serial, and Android Debug Bridge, hiding interface-specific details from test cases through configuration. ### Source excerpt Coppercomm -- One interface to unite them allHow to share test cases across organizations and companiesBackgroundInterface overview Have you ever faced the challenge of reusing test cases when testing the same Device Under Test (DUT) across different organizations and companies? You are not alone. One of the main problems is the different libraries used. And it is not at all unusual for an organization to use different libraries for the same purpose. It could be that one team is not aware of the existence of a library, and decides to create a new one. Suddenly, there are two libraries doing the same thing! It's like having two different keys to the same lock. The problem grows when there is a need to share the same test cases between different companies and organizations. You might want to run a specific test case before delivering to a customer, and then after the customer has applied some changes, they might want to re-run the same test case again to make sure that it still works. You would want to run the same test case, the same way. This is where Coppercomm comes into play. It is written in Python and functions as a bridge between the host and DUT, for different types of communication interfaces, like SSH, serial, and Android Debug Bridge (ADB). This enables us to run the same test case at different departments without modifying the test case, as long as the test case is using Coppercomm and the Coppercomm library is available on the host. How Coppercomm worksCoppercomm overview Coppercomm is pretty basic. You create a configuration file that maps the different interfaces to a logical or physical interface. The configuration file is then used under the hood by Coppercomm. This hides the mapping from the user, and the test cases only need to specify what type of interface they want to use. Voilà! The host communicates with the DUT, without any specifics in the test case. Open sourcing Coppercomm"Given enough eyeballs, all bugs are shallow" - Linus Torvalds Sharin ## Ibis: Because SQL is everywhere and so is Python DevFeed: [Ibis: Because SQL is everywhere and so is Python]() Original publisher: [Read original article]() Author: Phillip Cloud, Cole Bowden Published: 2023-07-03T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [Python](), [SQL](), [Data analysis](), [data]() Tags: [analysis](), [bridge](), [bridging](), [data](), [performance](), [python](), [sql]() ### AI overview The article presents Ibis as a lightweight Python library that bridges Python data wrangling and SQL query engines. It converts Python code into SQL for multiple engines, including Trino, allowing users to combine Python's usability with Trino's performance for large-scale queries. ### Source excerpt The PyData stack has been described as "unreasonably effective," empowering its users to glean insights and analyze moderate amounts of data with a high level of flexibility and excellent visualization. The large-scale, production data stack using a query engine like Trino sits on the other side of the world, capable of handling petabytes and exabytes, but perhaps not integrating as seamlessly with the Python ecosystem as one would hope. SQL has been a means of bridging this gap, but we've now got an exciting solution to bridge it even better: Ibis. ## Config 2023: Reimagining where teams design and build together DevFeed: [Config 2023: Reimagining where teams design and build together]() Original publisher: [Read original article]() Author: Dylan Field Published: 2023-06-21T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [GitHub](), [Storybook](), [vs-code](), [Code]() Tags: [bridge](), [config](), [design](), [design-systems](), [dev](), [developers](), [development](), [figma](), [github](), [plugins](), [product-development](), [production](), [prototyping](), [tools](), [updates](), [vs-code]() ### AI overview Figma's Config 2023 recap introduces Dev Mode, variables, advanced prototyping, and quality-of-life improvements designed to connect design and development. Dev Mode helps developers translate designs to code, connect tools and codebases through plugins, track production work, and inspect files in VS Code. ### Source excerpt We're launching Dev Mode, variables, advanced prototyping, and a series of quality of life updates to help you go from design to build. ## Diving into polymorphic table functions with Trino DevFeed: [Diving into polymorphic table functions with Trino]() Original publisher: [Read original article]() Author: Kasia Findeisen, Brian Olsen, and Cole Bowden Published: 2022-07-22T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [SQL](), [data]() Tags: [blog](), [blog-post](), [bridge](), [connectors](), [data](), [external](), [post](), [sql]() ### AI overview This Trino blog post introduces polymorphic table functions (PTFs), whose returned table schema is determined dynamically from their arguments. It explains how table functions differ from scalar, aggregate, and window functions, and describes Trino's release 381 support, including connector-executed table functions and query pass-through for JDBC-based connectors and Elasticsearch. ### Source excerpt In the Trino community, we know that being the coolest query engine is a tough job. We boldly face the intricacies of the SQL standard to bring you the newest and most powerful features. Today, we proudly announce that as of release 381, Trino is on its way to full support for polymorphic table functions (PTFs). In this blog post, we are explaining the concept of table functions and exploring how they can be leveraged. We also look at what we have already implemented, and take a sneak peek into the future. ## Troubleshooting Kubernetes Networking Issues DevFeed: [Troubleshooting Kubernetes Networking Issues]() Original publisher: [Read original article]() Author: sasha@goteleport.com (Sasha Klizhentas) Published: 2022-04-26T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Kubernetes](), [Kubernetes networking](), [Kubernetes clusters](), [networking]() Tags: [bridge](), [firewall](), [ip](), [kernel](), [kubernetes](), [kubernetes-clusters](), [kubernetes-networking](), [modules](), [networking](), [troubleshooting](), [udp](), [vxlan]() ### AI overview Part 1 of a Kubernetes troubleshooting series focuses on networking failures, including traffic forwarding, bridge-netfilter settings, and firewall rules affecting overlay network traffic. It explains how these failures manifest and outlines ways to diagnose and fix them. ### Source excerpt Part 1 of our Troubleshooting Kubernetes series focuses on networking, listing common issues we have encountered along with easy ways to troubleshoot them. ## ESP USB Bridge DevFeed: [ESP USB Bridge]() Original publisher: [Read original article]() Author: John Lee Published: 2022-04-13T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [USB](), [ESP-IDF](), [Esp32 S2](), [Microcontroller](), [ESP32-S3](), [Espressif]() Tags: [apache](), [blog](), [bridge](), [esp-idf](), [esp32-s2](), [esp32-s3](), [espressif](), [flashing](), [jtag](), [microcontrollers](), [usb]() ### AI overview ESP USB Bridge is an ESP-IDF project for ESP32-S2, optionally ESP32-S3, that bridges a computer with a target microcontroller. It provides serial, JTAG, and USB mass-storage functions, including UF2-based flashing. ### Source excerpt The ESP USB Bridge is an ESP-IDF project utilizing an ESP32-S2 (or optionally, an ESP32-S3) chip to create a bridge between a computer and a target microcontroller. It can serve as a replacement for USB-to-UART chips (e.g. CP210x). ESP USB Bridge creates a composite USB device accessible from the computer when they are connected through a USB cable. The main features are the following. ## Matter: Bridge for Non-Matter Devices DevFeed: [Matter: Bridge for Non-Matter Devices]() Original publisher: [Read original article]() Author: John Lee Published: 2021-12-14T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Matter](), [Internet of things](), [zigbee](), [Protocol (disambiguation)]() Tags: [blog](), [bridge](), [esp32](), [espressif](), [iot](), [matter](), [protocol](), [standard](), [zigbee]() ### AI overview This tutorial explains how Matter Bridges allow non-Matter IoT devices, such as Zigbee devices, to operate within a Matter ecosystem. It introduces bridged devices, the Matter data model, and the commissioning workflow for a Matter-Zigbee Bridge. ### Source excerpt Several big IoT ecosystems have announced integrated support for Matter, e.g., Amazon, Apple, Google and Samsung. It's exciting to expect that more and more devices from multiple brands work natively together, under a bigger Matter ecosystem. Meanwhile, people may have a question: There are many IoT products in the consumers' home already, these can be the devices based on Zigbee, Z-Wave, BLE Mesh and others. Could these non-Matter devices work together with Matter ecosystem? The answer is YES. ## Bridge Mode with UniFi Access Points DevFeed: [Bridge Mode with UniFi Access Points]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-09-19T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Tutorial](), [Ubiquiti](), [Ethernet](), [Hardware]() Tags: [bridge](), [ethernet](), [guide](), [homelab](), [tutorial](), [ubiquiti](), [unifi](), [unifi-access-points](), [wireless]() ### AI overview A step-by-step tutorial for configuring two Ubiquiti UniFi AP AC PRO devices as a wireless bridge to extend Ethernet to a remote site, including a throughput test. ### Source excerpt Do you have some places where you can't run ethernet? Do want to extend your ethernet without pulling more cable? Well this is the guide for you.In this step-by-step tutorial we'll use a Ubiquiti UniFi AP AC PRO and connect a second as a guest, giving use remote ethernet to a remote site! This is the pro tip guide to setting up a wireless bridge! Bonus, we'll even do a live throughput test ... ## Flutter or React Native, a cross-platform dilemma - How they work - (Part 3) DevFeed: [Flutter or React Native, a cross-platform dilemma - How they work - (Part 3)]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2020-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [React Native](), [cross-platform](), [event driven](), [Flutter](), [interfaces]() Tags: [asynchronous](), [bridge](), [cross-platform](), [event](), [flutter](), [list](), [react-native](), [render](), [serialization]() ### AI overview This third-part article explains, at a high level, how React Native and Flutter work under the hood. The supplied text focuses on React Native's Bridge, which connects JavaScript and native code through asynchronous, serialized messages, and describes how message queues can introduce delays for complex interfaces. It also mentions Facebook's Fabric architecture as an effort to address those delays. ### Source excerpt Welcome to the third part of this article series about React Native and Flutter. In the latest episode, we have talked about User Interfaces and how to build them in the two frameworks. In this article, we'll go deeper under the hoods to understand how things work. But I will not go deeper with lot's of details and implementation things, because I want to make you understand how the thing works at a high level. If you are interested to go deeper, I will leave across the article some links for further information. [Next page]()