# Protocol (disambiguation) A disambiguation topic for the term "protocol," including OOP interfaces and network or communication protocols. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## \[Podcast\] 'Just say no' isn't as simple as you think DevFeed: [\[Podcast\] 'Just say no' isn't as simple as you think]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-09-16T23:23:11Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [APNIC Labs](), [Protocol (disambiguation)](), [Server]() Tags: [apnic-labs](), [dns](), [measurement](), [podcast](), [protocol](), [tech-matters]() ### AI overview A PING podcast episode continues a discussion of surplus DNS queries observed in an APNIC Labs experiment. It examines how different ways of answering negatively affect query volume and the work required by servers, resolvers, and clients, and considers whether maintaining transport protocol state could reduce repeated-query work. ### Source excerpt A continuation of the discussion on surplus DNS queries seen at APNIC Labs, the implications of how you say 'no', and the transport used for the DNS ## AI DevFeed: [AI]() Original publisher: [Read original article]() Published: 2026-09-15T02:59:12.316196Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [Artificial Intelligence](), [AI Agent](), [Security](), [Google](), [Protocol (disambiguation)](), [Databases](), [CockroachDB]() Tags: [2026](), [agents](), [ai](), [cockroachdb](), [databases](), [google](), [security](), [vector-search]() ### AI overview An AI-focused Cockroach Labs blog category page listing articles about agent-to-agent communication, AI agent security, database isolation, compliance, resilience, identity, vector search, operations automation, and durable execution with CockroachDB. ### Source excerpt Blog ai A2A Is Now an Open Standard. The Data Layer Underneath It Isn't. In April 2025, Google released a protocol for agent-to-agent communication. Within three months, Google had donated it to the Linux Foundation... Quentin Packard August 19, 2026 Multi-Tenant AI Agents: Why Data Isolation Starts at the Database Most SaaS teams shipping agentic features focus on prompt safety and API-layer filtering. But effective AI agent security also depends on... ## Bringing QUIC to Seastar DevFeed: [Bringing QUIC to Seastar]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-09-14T13:02:07Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [Seastar](), [networking](), [Remote Procedure Call (RPC)](), [C++](), [Latency](), [Protocol (disambiguation)]() Tags: [benchmarks](), [c-plus-plus](), [collaboration](), [engineering](), [latency](), [network](), [networking](), [rpc](), [scylladb](), [seastar](), [udp]() ### AI overview This article describes a University of Warsaw student project conducted with ScyllaDB to implement a QUIC transport for Seastar using the sans-I/O ngtcp2 library. It also adapts Seastar's RPC layer to operate over QUIC and reports benchmark results showing predictable overhead on a lossless loopback and benefits when packets are dropped. ### Source excerpt We built a QUIC transport for Seastar on top of ngtcp2's sans-I/O state machine, then adapted RPC to it twice: 1) as a one-to-one socket replacement, and 2) a QUIC-aware approach that opens a fresh stream per call. ## KDE Plasma 6.8 Remote Desktop To Enjoy Lower Latency Performance DevFeed: [KDE Plasma 6.8 Remote Desktop To Enjoy Lower Latency Performance]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T10:07:48Z Content type: news Language: en Sources: [Phoronix]() Topics: [Latency](), [client](), [Wayland](), [Protocol (disambiguation)](), [configuration](), [GUI]() Tags: [configuration](), [desktop](), [desktop-linux](), [image](), [latency](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [performance](), [phoronix](), [phoronix-test-suite](), [release](), [remote](), [switching](), [time](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview KDE Plasma 6.8 improves KRDP remote desktop latency by dropping incoming frames when the encoder outpaces the client. The release also includes input-method, clipboard, Wayland protocol, wallpaper dialog, and XWayland session configuration fixes. ### Source excerpt Along with KDE Plasma 6.8 beta releasing this week, there were some other interesting Plasma changes this week worthy of a shout-out... ## How Neon made Postgres claimable for agents with auth.md DevFeed: [How Neon made Postgres claimable for agents with auth.md]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-10T14:21:50Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Database](), [Protocol (disambiguation)](), [API](), [OAuth]() Tags: [agents](), [api](), [auth](), [database](), [protocol]() ### AI overview Neon used auth.md to let agents provision bounded temporary Postgres projects before a human creates an account. People can later claim the projects into a Neon organization, while unclaimed projects expire. ### Source excerpt How Neon used auth.md to let agents provision bounded database projects before a human signs up, then later transfer them to people who want to keep them. ## Can you design a chip? Announcing the protocol emulator ASIC competition DevFeed: [Can you design a chip? Announcing the protocol emulator ASIC competition]() Original publisher: [Read original article]() Author: Benjamin Devlin Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [Jane Street]() Topics: [Chip design](), [Protocol (disambiguation)](), [Hardware](), [Open Source](), [Emulator](), [cpu](), [Reverse Engineering](), [fpga](), [Formal methods](), [Verilog]() Tags: [chip-design](), [cpu](), [emulator](), [ethernet](), [firmware](), [formal-methods](), [fpga](), [hardware](), [i2c](), [jtag](), [open-source](), [peripheral](), [protocol](), [reverse-engineering]() ### AI overview Jane Street announces a competition to design an open-source, general-purpose protocol emulator ASIC. The proposed chip would use a small programmable CPU to read and write pins, count cycles, and implement protocols in firmware, with fabrication planned through IHP and Tiny Tapeout. ### Source excerpt Last month, we asked you to reverse engineer a chip from nothing but its layout and teased a bigger challenge. Results and our favorite writeups are coming soon. In the meantime, here's our next challenge! This time, you're designing the chip, and we'll pay to fabricate our favorite designs! We're particularly interested in projects with unique functionality, as well as those that demonstrate novel approaches to design and verification methodologies! ## Android A2UI (AI to UI) Made Simple DevFeed: [Android A2UI (AI to UI) Made Simple]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-09T07:23:57Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Artificial Intelligence](), [Android](), [Jetpack Compose](), [Mobile](), [Protocol (disambiguation)](), [Google]() Tags: [a2ui](), [ai](), [android](), [android-app-development](), [api](), [artificial-intelligence](), [deprecated](), [google](), [jetpack-compose](), [mobile-app-development](), [software-development](), [user-interfaces]() ### AI overview This tutorial introduces A2UI, a protocol for rendering AI responses as user interfaces, and discusses trying it on Android with Jetpack Compose. It notes that an older Jetpack A2UI library is deprecated and that newer development is ongoing. ### Source excerpt Converting AI Prompt Output Into User Interface in Jetpack Compose Continue reading on Mobile App Development Publication " ## Join Us: EF Protocol Reddit AMA - September 16th, 2026 DevFeed: [Join Us: EF Protocol Reddit AMA - September 16th, 2026]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Cluster Published: 2026-09-09T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Protocol (disambiguation)](), [Formal verification]() Tags: [2026](), [community](), [development](), [ethereum](), [formal-verification](), [privacy](), [reddit](), [research-development](), [technical](), [upgrades]() ### AI overview The Ethereum Foundation announces a September 16, 2026 Reddit AMA with researchers and developers from its Protocol cluster. The discussion will cover Ethereum protocol development, including the Glamsterdam hard fork, Hegotá, post-quantum Ethereum, formal verification, privacy, client development, and related topics. ### Source excerpt Every year since January 2019, teams from the Ethereum Foundation have spent an afternoon or two on r/ethereum answering questions from the community. The format hasn't really changed: one thread, technical debates, detailed explanations, and community members asking whatever is on their mind. By now it is a tradition, and... ## Worth Reading: An Interactive Introduction to the STP DevFeed: [Worth Reading: An Interactive Introduction to the STP]() Original publisher: [Read original article]() Published: 2026-09-08T05:55:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Protocol (disambiguation)](), [WebAssembly]() Tags: [video](), [webassembly](), [worth-reading]() ### AI overview An enthusiastic recommendation for Vincent Bernat's interactive introduction to the spanning tree protocol, which begins with an STP implementation in WebAssembly and is also available as a video. ### Source excerpt I can't even start imagining how much time Vincent Bernat spent creating his interactive introduction to the spanning tree protocol (starting with STP implemented in WebAssembly); the results are simply phenomenal (there's also a video version for people who forgot how to read). I don't think we'll ever need another STP intro after this one ;) ## SCIM directory sync: A deep dive into deprovisioning DevFeed: [SCIM directory sync: A deep dive into deprovisioning]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-08T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Protocol (disambiguation)](), [Security](), [Parser](), [Entra ID]() Tags: [audit](), [deep-dive](), [filter](), [protocol](), [provisioning](), [reconciliation](), [security]() ### AI overview This deep dive explains how SCIM directory deprovisioning reaches applications, why identity providers commonly deactivate users instead of deleting them, and how provider-specific payloads and missed events can create security risks. It covers normalization, reconciliation, session termination, and inspecting provider requests. ### Source excerpt What actually happens when a user is removed: the event your app receives, the directories that never send one, and how to catch what gets dropped. ## EF Protocol: The Hegotá EIP Opinion Post and Tier List DevFeed: [EF Protocol: The Hegotá EIP Opinion Post and Tier List]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Cluster Published: 2026-09-07T00:00:00Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Protocol (disambiguation)](), [Testing](), [client]() Tags: [opinion](), [process](), [protocol](), [research-development](), [testing]() ### AI overview The EF Protocol cluster presents a unified tier list for 62 EIPs proposed for Hegotá. The assessment combines 397 tier grades from nine teams and individual contributors, with tiers defining delivery expectations and conditions for considering lower-tier proposals. ### Source excerpt This is the EF Protocol cluster's tier list for Hegotá. We evaluated the 62 EIPs proposed for inclusion, each with a tier and a short note on the grade. It is the first time the cluster has published one unified view rather than per-team opinions. Geth, of course, being... ## EF Protocol: Current and Emerging Priorities DevFeed: [EF Protocol: Current and Emerging Priorities]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Cluster Published: 2026-09-07T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Post-Quantum](), [Protocol (disambiguation)](), [migration](), [data](), [Cloudflare](), [Google](), [Microsoft]() Tags: [data](), [ethereum](), [migration](), [post-quantum](), [protocol](), [research-development]() ### AI overview The EF Protocol cluster outlines Ethereum Protocol priorities through 2029, including scoping the Hegotá upgrade and preparing Ethereum L1 to become quantum-resistant across the execution, consensus, and data layers by December 2029. The plan uses an intentionally aggressive assumption that Q-day could occur as early as 2030, with the deadline to be reassessed in January 2027. ### Source excerpt In May, the Protocol cluster welcomed a trio of new cluster coordinators and promised updates to follow. After months of settling in and aligning with contributors cluster-wide, across the EF and across the Ethereum ecosystem, we are now happy to share Protocol's priorities: what Protocol is for, the commitments... ## Latent Powers DevFeed: [Latent Powers]() Original publisher: [Read original article]() Author: Armin Ronacher Published: 2026-09-05T00:00:00Z Content type: opinion Language: en Sources: [Armin Ronacher]() Topics: [Dongle](), [Hacking](), [Rust](), [Embedded Software Dev](), [Protocol (disambiguation)](), [Raspberry Pi]() Tags: [ai](), [dongle](), [firmware](), [hacking](), [protocol](), [raspberry-pi](), [rust](), [soc](), [thoughts](), [usb]() ### AI overview A developer experiments with modifying a cheap CarPlay dongle to run custom code while preserving regular CarPlay functionality. After receiving a different SoC than expected, they use LLM-assisted discussions to flash the device and compile CatPlay, a Rust reimplementation of the CarPlay protocol, for the hardware. ### Source excerpt A few weeks ago I felt like it would be fun to see if I can make one of those cheap Chinese CarPlay dongles run something other than the stock firmware. The idea was that rather than just forwarding CarPlay, why not do something more interesting with them? They all work quite similarly: they act as bridges between your car and the phone. From there they deal with video and audio streams and pass some other data through. Most of them also bring up a custom UI for pairing and have a web interface that your phone can reach for updates. Long story short: I had a conversation with Fable and Sol via Pi about what could be done with such a dongle or whether I should use a Raspberry Pi instead if I wanted to do my own thing there. I figured it might be quite fun to run my own code while still allowing regular CarPlay to pass through. Through working with the LLM I learned about CatPlay, which is a Rust reimplementation of the CarPlay protocol that can run on Carlinkit devices. In particular, it can run on the Carlinkit Mini Ultra, which I figured would be easy enough to buy. I do have a few CarPlay adapters around, but I did not have that particular model, so I bought one on Amazon. Twenty-four hours later, I had a device in my hand that was branded as a Carlinkit Mini Ultra, but instead of being the Ingenic device that the original author used, it turned out to be something else. This is normally where the story would stop. However, it's 2026. Armed with a bit of knowledge about how these systems work, I managed to have some fruitful discussions with Kimi K3 and Sol and figure out how flash the device and in turn, how to make CatPlay compile for that SoC. I guess that hacking these USB devices is not necessarily hard, but it's laborious and you can easily end up bricking your devices. It also just sucks because sometimes you need to work with someone else's code that does not itself run on your machine. In the past, I would abandon many such projects for lack of tenacity. ## I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts DevFeed: [I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-04T12:32:34Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Availability](), [Linux](), [Proxmox](), [Network](), [Protocol (disambiguation)](), [Docker](), [Server](), [configuration]() Tags: [availability](), [dns](), [docker](), [high-availability](), [home-lab](), [home-server](), [linux](), [network](), [proxmox](), [servers](), [virtualization]() ### AI overview The article explains how Keepalived provides high availability for home lab servers by moving a virtual IP address between Proxmox hosts using VRRP. It focuses on track scripts, which allow failover decisions based on application-level checks rather than only complete server failure, with Docker-based DNS services as an example. ### Source excerpt I have used Keepalived in my home lab for quite some time and most of the time, I have thought of it in a very simple way as to what... The post I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts appeared first on Virtualization Howto. ## Video Streaming Protocols: 6 Preferred Formats for Professional Broadcasting DevFeed: [Video Streaming Protocols: 6 Preferred Formats for Professional Broadcasting]() Original publisher: [Read original article]() Author: Jon Whitehead Published: 2026-09-02T09:35:50Z Content type: tutorial Language: en Sources: [DaCast]() Topics: [Streaming](), [Protocol (disambiguation)](), [Latency](), [Low Latency](), [WebRTC](), [Playback](), [format](), [data]() Tags: [data](), [format](), [latency](), [low-latency](), [playback](), [protocols](), [streaming](), [the-video-experts-blog](), [video](), [video-streaming](), [webrtc]() ### AI overview This guide explains six video streaming protocols used in professional broadcasting: HLS, RTMP, WebRTC, SRT, RTSP, and MPEG-DASH. It compares their purposes, strengths, limitations, latency, compatibility, and suitable use cases. It presents HLS as a broadly compatible delivery default, RTMP as an ingest standard, WebRTC for real-time two-way interaction, SRT for one-way broadcasting over unreliable networks, RTSP for surveillance and IoT, and MPEG-DASH as an open alternative with limited Apple support. ### Source excerpt By Dacast Editorial Team | Reviewed by Jon Whitehead, COO at Dacast | Updated September 2026 A video streaming protocol is the set of rules that governs how video data moves from your encoder to your streaming host to the video player your audience watches on. Common examples include RTMP, HLS, WebRTC, and SRT, each [...] The post Video Streaming Protocols: 6 Preferred Formats for Professional Broadcasting appeared first on Dacast. ## fx is now available in the AI SDK harness layer DevFeed: [fx is now available in the AI SDK harness layer]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-08-31T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [SDKs](), [Vercel](), [AI-assisted coding](), [API](), [Protocol (disambiguation)]() Tags: [agent](), [agents](), [ai](), [api](), [building](), [claude](), [claude-code](), [codex](), [coding-agents](), [cursor](), [integration](), [open-source](), [opencode](), [sdk](), [vercel]() ### AI overview Vercel's AI SDK harness layer now supports fx, a lightweight open-source coding agent. Developers can run fx in their applications through the HarnessAgent interface using the official @ai-sdk/harness-fx adapter, which connects through the Agent Client Protocol via @ai-sdk/harness-acp. ### Source excerpt The AI SDK harness layer now supports fx, Vercel's lightweight, open-source coding agent. The harness layer provides one API for running coding agents in your application, so you can add fx without building a separate integration. Configure HarnessAgent with the official @ai-sdk/harness-fx adapter: The @ai-sdk/harness-fx adapter connects to fx over the Agent Client Protocol (ACP) using @ai-sdk/harness-acp. fx joins Claude Code, Cline, Codex, Cursor, Deep Agents, Grok Build, OpenCode, and Pi in the list of supported harnesses. Read the fx harness documentation to get started. Read more ## Before NTP there were Time and Daytime DevFeed: [Before NTP there were Time and Daytime]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-08-30T22:09:00Z Content type: article Language: en Sources: [Jeff Geerling]() Topics: [networking](), [Protocol (disambiguation)](), [Unix]() Tags: [apple](), [bug](), [daytime](), [history](), [network](), [ntp](), [rfc-867](), [rfc-868](), [server](), [time]() ### AI overview The article examines the pre-NTP Time and Daytime protocols, RFC 868 and RFC 867, and explains how they provided simple network-based time retrieval. It describes the protocols' low overhead and limitations, including one-second resolution, lack of network-delay measurement, and the 2036 32-bit rollover bug. ### Source excerpt In building an NTP time demo on old Macs for VCF Midwest, I came across RFC 867 and RFC 868, for the 'Daytime' and 'Time' Protocols, respectively. My first exposure to any form of network time was when I upgraded from a used PowerBook 180c to my first 'new' computer, a Power Mac G3, in 2000. With the introduction of Mac OS 8.5, Apple added a 'Network Time Server' option in the Date & Time Control Panel. ## 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. ## The lingering legacy of 'reserved' ports DevFeed: [The lingering legacy of 'reserved' ports]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-08-27T23:29:48Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Protocol (disambiguation)](), [Network](), [Process](), [Operating system](), [Unix](), [ssh](), [Firewall](), [Internet]() Tags: [dns](), [firewall](), [history](), [internet](), [network](), [ntp](), [opinion](), [process](), [processes](), [ssh](), [systems](), [tech-matters]() ### AI overview An exploration of why reserved TCP and UDP ports persist, tracing conventions such as ports 22, 53, 80, and 443 to early Internet services on multi-user systems. It explains the relationship between ports, protocol-specific daemons, operating-system administration, and modern firewall and service-discovery practices. ### Source excerpt Modern service discovery mechanisms increasingly allow services to run on arbitrary ports, yet DNS may remain the one protocol that cannot fully escape its dependency on the long-established convention of port 53. ## How to Live Stream the Raspberry Pi Camera (2 Easy Ways) DevFeed: [How to Live Stream the Raspberry Pi Camera (2 Easy Ways)]() Original publisher: [Read original article]() Author: Dhairya Parikh Published: 2026-08-27T04:21:36Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Streaming](), [webcam](), [real-time](), [Protocol (disambiguation)](), [Hardware](), [Web](), [Linux](), [Terminal](), [Software]() Tags: [guide](), [hardware](), [how-to](), [how-to-tutorials](), [linux](), [live-stream](), [process](), [raspberry-pi](), [raspberry-pi-os](), [real-time](), [software](), [streaming](), [video](), [web]() ### AI overview A tutorial explaining two ways to live-stream video from a Raspberry Pi Camera to another device: using an RTSP stream or a web page on the local network. It covers the required Raspberry Pi hardware, camera module, SD card, Raspberry Pi OS, and the initial terminal command for starting an RTSP stream. ### Source excerpt I've used Raspberry Pi cameras in many projects over the years, and live streaming is one of those features that sounds more complicated than it really is. Once the camera is working, there are a few simple ways to stream its feed to another device. Raspberry Pi Camera video can be live-streamed in two ways:... ## Propagating User Identity Chains Across JVM Service Calls DevFeed: [Propagating User Identity Chains Across JVM Service Calls]() Original publisher: [Read original article]() Author: Peter Firmstone Published: 2026-08-23T00:00:00Z Content type: article Language: en Sources: [Nicolas Fränkel]() Topics: [Security](), [Java](), [Authorization](), [Protocol (disambiguation)]() Tags: [authorization](), [dirtychai](), [java](), [jgdms](), [jini](), [jvm](), [microservices](), [protocol](), [security](), [technical](), [tls](), [tokens]() ### AI overview This article explains how a chain of user identities crosses service calls on the wire. It distinguishes TLS machine authentication from in-band user claims, describes receiver-side limits and principal handling, and notes that standard Java 24 lacks the required authorization support without DirtyChai on both ends. ### Source excerpt Alice calls the order service. The order service calls the ledger on her behalf. At the second hop, the ledger has to decide whose authority the debit is being made under. Most stacks answer badly. Forward Alice's bearer token verbatim, and the ledger cannot tell her from the service that relayed it. Drop the token and the ledger sees a machine, with no record that a human started the chain. Neither option lets the ledger authorize the combination. ## \[GSoC 2026\] Modernizing Haiku's Bluetooth stack: Implementing support for HFP profile - Progress Report DevFeed: [\[GSoC 2026\] Modernizing Haiku's Bluetooth stack: Implementing support for HFP profile - Progress Report]() Original publisher: [Read original article]() Author: vighnesh-sawant Published: 2026-08-21T18:04:07Z Content type: article Language: en Sources: [Haiku Project]() Topics: [Bluetooth](), [Protocol (disambiguation)](), [implementation](), [bug](), [USB]() Tags: [bluetooth](), [bug-fixes](), [gsoc](), [haiku](), [implementation](), [progress-report](), [software](), [usb]() ### AI overview This GSoC 2026 progress report describes work modernizing Haiku's Bluetooth stack for the Hands-Free Profile (HFP). It covers RFCOMM implementation, xHCI improvements, Bluetooth stack and media fixes, HFP session functionality, and a Bluetooth SCO Media Kit add-on. RFCOMM and SCO are nearly ready for merging, while HFP still needs to be split, reviewed, and prepared for merging. ### Source excerpt Introduction The goal of this post is to document the changes I made during the GSoC period and the current state of the project. I would also like to thank waddlesplash for his continued support throughout the project. Progress So Far RFCOMM Protocol RFCOMM is now almost ready to be merged. It acts as the control channel required by HFP. The implementation includes: RFCOMM socket addressing and connection management DLCI multiplexing over a shared L2CAP connection SABM, UA, DM, DISC, and UIH frame handling MCC commands Credit-based flow control USB and xHCI Improvements During implementation, I found that the xHCI driver assumed all isochronous packets had the same size, which is not always true. The xHCI driver now supports variable-length isochronous packets and processes completed transfers in FIFO order instead of LIFO order. Bug Fixes A part of this period was spent fixing issues in the existing Bluetooth stack. The main fixes include: Correcting ACL packet splitting when packets exceed the L2CAP MTU. Holding socket references while working on them. Related changes include the L2CAP refactor,send-status fix, socket lifetime changes, and MTU packet fix Media Stack Fixes While working on Bluetooth audio integration, I found some bugs in the media stack. After initial work, waddlesplash took over these changes and implemented the actual changes. The improvements landed in the media auto-stop change and the live output reconnection change. Hands-Free Profile The first pass for HFP is done. It includes: Hands-Free service discovery through SDP. HFP session management. Basic AT-command parsing. The implementation is functional but work is needed to split the changes, getting it reviewed and making it merge ready. Bluetooth SCO Media Add-on The Bluetooth SCO Media Kit add-on has also been implemented. It discovers Bluetooth audio devices, exposes them through the Media Kit, and creates media nodes for headset playback and capture. It includes: Bluetooth headset disco ## Lowering Slot Time and Validator Economics DevFeed: [Lowering Slot Time and Validator Economics]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-19T10:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Latency](), [Protocol (disambiguation)]() Tags: [blockchain](), [blockchain-technology](), [consensus](), [crypto-news](), [cryptocurrency](), [defi](), [infrastructure](), [latency](), [nfts](), [performance](), [podcasts](), [protocol](), [reports](), [solana](), [solana-ecosystem](), [upgrades](), [web3]() ### AI overview Solana plans to reduce slot times from 400 ms to 200 ms. The article examines possible effects on latency, arbitrage, sandwich MEV, validator rewards and costs, voting frequency, and consensus performance, while noting that some impacts require empirical mainnet monitoring. ### Source excerpt Solana will reduce its slot times from 400ms to 200ms. This change will make the protocol more competitive in terms of latency. Here we explore some possible implication on validators economic. ## BGP Role model: tracking the adoption of RFC 9234 DevFeed: [BGP Role model: tracking the adoption of RFC 9234]() Original publisher: [Read original article]() Author: Mingwei Zhang Published: 2026-08-18T15:21:32Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [BGP](), [networking](), [Networks](), [Routing (disambiguation)](), [Protocol (disambiguation)](), [Cloudflare](), [Monitoring]() Tags: [analysis](), [bgp](), [cloudflare](), [internet](), [monitoring](), [network](), [networks](), [research](), [router](), [routing](), [routing-security](), [rpki]() ### AI overview This article examines the adoption of RFC 9234, which uses BGP Roles and the Only to Customer (OTC) attribute to help routers prevent and detect route leaks. Cloudflare measured deployment through its global peering presence and found that two large Tier-1 networks were stripping OTC attributes from forwarded routes. ### Source excerpt RFC 9234 lets routers reject route leaks on their own, using BGP Roles and the Only to Customer attribute. We measured who has deployed it, and found two Tier 1 networks unexpectedly stripping OTC. [Next page]()