# protocols Published articles for 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. ## GNOME 51 Released With Improved Frame Scheduling, Many App Improvements DevFeed: [GNOME 51 Released With Improved Frame Scheduling, Many App Improvements]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T16:25:21Z Content type: news Language: en Sources: [Phoronix]() Topics: [releases](), [Wayland](), [Release notes](), [Software](), [ui](), [legacy](), [Nvidia]() Tags: [desktop](), [desktop-linux](), [driver](), [experience](), [faster](), [improvements](), [legacy](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [notes](), [nvidia](), [offline](), [open-source-graphics](), [other](), [phoronix](), [phoronix-test-suite](), [protocols](), [release](), [release-notes](), [settings](), [software](), [time](), [ubuntu](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui](), [wayland](), [workstation]() ### AI overview GNOME 51 has been released with improved frame scheduling and desktop responsiveness, new Wayland protocol support, removal of legacy NVIDIA EGLStreams driver support, and updates to several GNOME applications and settings. ### Source excerpt Right on schedule and in time for appearing in the likes of Ubuntu 26.10 and Fedora Workstation 45, the GNOME 51 desktop is officially released... ## 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. ## New Keycloak Maintainer: Ricardo Martin DevFeed: [New Keycloak Maintainer: Ricardo Martin]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2026-05-07T00:00:00Z Content type: news Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Security](), [Authentication](), [Passkeys](), [saml]() Tags: [authentication](), [bugs](), [community](), [contributors](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [protocols](), [pull-requests](), [saml](), [security](), [sso]() ### AI overview Keycloak announces Ricardo Martin as an official maintainer. The article highlights his contributions to core Keycloak areas, authentication protocols, community support, bug fixes, pull-request reviews, and security issue resolution. ### Source excerpt Ricardo joined the Keycloak IBM team at the beginning of 2023 and became one of the top Keycloak contributors since then. Ricardo has very deep knowledge in many core Keycloak areas. He is the most knowledgeable person from the whole team in areas like for example SAML, Passkeys or FIPS. His expertise is not limited to just those areas, but rather he has deep knowledge around pretty much every aspect of protocols and authentication in Keycloak. Additionally, Ricardo is very active in helping the community, joining discussions, fixing bugs, reviewing pull requests, as well as an active participant in triaging and resolving security issues. Congratulations to Ricardo becoming an official Keycloak Maintainer. ## HTTP/2 System Design: How It Fixes HTTP/1.1 DevFeed: [HTTP/2 System Design: How It Fixes HTTP/1.1]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [HTTP](), [Latency](), [Concurrency](), [Compression]() Tags: [compression](), [concurrency](), [http](), [http1-1](), [http2](), [latency](), [networking](), [parallel](), [performance](), [protocols](), [reliability](), [rest](), [system-design](), [tcp](), [tls](), [web-performance]() ### AI overview This article explains how HTTP/2 addresses HTTP/1.1 limitations through binary framing, multiplexed streams over one TCP connection, HPACK header compression, server push, and stream prioritisation. It also describes how HTTP/2 preserves HTTP semantics while improving latency and reducing application-layer head-of-line blocking. ### Source excerpt HTTP/1.1 hit concurrency limits that forced hacks like domain sharding and sprite sheets. HTTP/2 keeps HTTP semantics but replaces the wire format with binary framing, multiplexed streams over a single TCP connection, HPACK header compression, server push, and stream prioritisation, which removes most head-of-line blocking at the HTTP layer. ## A bit more on Twitter/X's new encrypted messaging DevFeed: [A bit more on Twitter/X's new encrypted messaging]() Original publisher: [Read original article]() Author: Matthew Green Published: 2025-06-09T18:22:31Z Content type: article Language: en Sources: [Matthew Green]() Topics: [End-to-End Encryption](), [X (Twitter)](), [Encryption](), [Security](), [vulnerability](), [public key](), [Ratchet](), [Server](), [passwords](), [Meta]() Tags: [e2e](), [encryption](), [instagram](), [messaging](), [messenger](), [protocol](), [protocols](), [public-key](), [secret-storage](), [security](), [signal](), [technology](), [vulnerability]() ### AI overview This article examines XChat, X's end-to-end encrypted messaging protocol, focusing on its lack of forward secrecy and its server-side storage of user private keys. It explains the Juicebox key-storage design and argues that the security of the system depends heavily on its deployment and server protections. ### Source excerpt Update 6/10: Based on a short conversation with an engineering lead at X, some of the devices used at X are claimed to be using HSMs. See more further below. Matthew Garrett has a nice post about Twitter (uh, X)'s new end-to-end encryption messaging protocol, which is now called XChat. The TL;DR of Matthew's post ... Continue reading A bit more on Twitter/X's new encrypted messaging -> ## Shadow Calls and Circuit Breakers: Uber's Safe Approach to Mobile Network API Migration DevFeed: [Shadow Calls and Circuit Breakers: Uber's Safe Approach to Mobile Network API Migration]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2024-09-24T20:06:25Z Content type: article Language: en Sources: [Ishan Khanna]() Topics: [gRPC](), [migration](), [API](), [Mobile](), [Latency](), [payload](), [client](), [Remote Procedure Call (RPC)](), [Developer experience]() Tags: [android](), [api](), [apis](), [experimentation](), [latency](), [migration](), [mobile](), [mobile-app-performance](), [mobile-apps](), [network](), [networking](), [payload](), [performance](), [protocols](), [rest](), [software-engineering](), [talks](), [tech-talk-review](), [technical]() ### AI overview This article discusses Uber's migration from REST to gRPC for mobile network APIs. It describes the motivation around payload size and latency, a three-phase migration strategy, technical challenges, and reported improvements including a 45% payload reduction and 27% latency improvement. ### Source excerpt Ishan discusses Uber's journey from REST to gRPC, showcasing a 45% payload reduction and 27% latency improvement. Dive into the three-phase migration strategy, technical challenges, and innovative solutions that transformed Uber's mobile app performance. ## What Is AAA Security? What Are the AAA Protocols? DevFeed: [What Is AAA Security? What Are the AAA Protocols?]() Original publisher: [Read original article]() Author: sakshyam.shah@goteleport.com (Sakshyam Shah) Published: 2022-02-16T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Security](), [Networks](), [Authentication](), [Authorization](), [Single sign-on (SSO)]() Tags: [access-control](), [authentication](), [authorization](), [blog-post](), [network](), [protocols](), [security](), [sso]() ### AI overview This blog post explains AAA security--authentication, authorization, and accounting--and how AAA protocols provide centralized access control for network services and devices. It also reviews their use in corporate networks, ISPs, cellular networks, and network equipment. ### Source excerpt This blog post explains how AAA (Triple-A) security works for network access controls and reviews three popular AAA protocols. ## WHOIS: An Unstructured Look at an Older Internet Protocol DevFeed: [WHOIS: An Unstructured Look at an Older Internet Protocol]() Original publisher: [Read original article]() Published: 2022-01-02T04:17:25Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [Internet]() Tags: [internet](), [protocols]() ### AI overview An unstructured look at WHOIS, described as one of the older internet protocols. ### Source excerpt A rather unstructured look at one of the older and infuriatingly trivial internet protocols: WHOIS ## What I Wish I Knew About U2F and Other Hardware MFA Protocols DevFeed: [What I Wish I Knew About U2F and Other Hardware MFA Protocols]() Original publisher: [Read original article]() Author: info@goteleport.com (Andrew Lytvynov) Published: 2021-04-15T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [MFA](), [Hardware](), [Authentication](), [Protocol (disambiguation)](), [OpenSSH]() Tags: [authentication](), [cryptographic](), [hardware](), [mfa](), [openssh](), [protocols](), [usb]() ### AI overview This article explains U2F and related hardware MFA protocols, including how U2F devices use challenge-response authentication and verify both possession of the device and user presence. It also describes Teleport 6.0 improvements that allow TOTP and U2F together and support multiple registered devices. ### Source excerpt We revamped the second-factor authentication in Teleport 6.0. This post provides a birds-eye view of U2F and other cryptographic hardware standards. ## When You Can't Ping, You Dig DevFeed: [When You Can't Ping, You Dig]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-07-22T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Internet](), [Amazon Web Services]() Tags: [attacks](), [aws](), [internet](), [protocols]() ### AI overview The article explains that ping checks whether an Internet service is available, while dig can be used to validate a service's address when ping is unavailable. It also notes that ping may be disabled because of ping flooding attacks. ### Source excerpt Normally when I'm trying to validate that an Internet service is available, well, I ping. Ping is one of those Internet bedrock protocols that I'm firmly in the camp of "SHOULD ALWAYS, ALWAYS, ALWAYS BE TURNED ON". But there are ping flooding attacks, etc so there are reasons why it isn't always a default (looking at you here AWS; staring you dead in the eyes with the 'ol stink eye). I recently realized that while it isn't example the same, if you're trying to validate something's address (as opposed to knowing if it is actually up), you can actually use dig. So instead of: ping foo.bar.com try: dig foo.bar.com ## Thought experiment on protocols and noise DevFeed: [Thought experiment on protocols and noise]() Original publisher: [Read original article]() Author: Nate Lawson Published: 2014-11-04T18:42:52Z Content type: opinion Language: en Sources: [rdist]() Topics: [Security](), [Protocol (disambiguation)](), [sha-256](), [hash]() Tags: [crypto](), [hash](), [hmac](), [network](), [protocol](), [protocols](), [security](), [sha-256]() ### AI overview A security thought experiment examines how to respond when an HMAC does not verify, including whether comparing MAC differences could distinguish network noise from tampering. It questions the security risks of exposing error details or accepting messages with altered MAC bits. ### Source excerpt I hesitate to call this an interview question because I don't think on-the-spot puzzle solving equates to a good engineering hire. On the other hand, I try to explore some simple thought experiments with candidates that have a security background. One of these involves a protocol that has messages authenticated by an HMAC. There's a message ... Continue reading Thought experiment on protocols and noise ## Protocols in Swift With Core Data DevFeed: [Protocols in Swift With Core Data]() Original publisher: [Read original article]() Author: Matt Long Published: 2014-10-29T16:52:07Z Content type: tutorial Language: en Sources: [Cocoa Is My Girlfriend]() Topics: [Protocol (disambiguation)](), [Swift](), [Xcode](), [classes](), [Code]() Tags: [classes](), [code](), [core-data](), [how-to](), [intermediate](), [protocols](), [swift](), [xcode]() ### AI overview A screencast demonstrates how to use Swift protocols with Core Data to display different managed object types generically in a table view controller. ### Source excerpt Sometimes you have a set of objects you want to display in the same form-say, for example, in a table view controller. What if those objects have, by design, nothing in common and nothing to do with each other? This is a case where you can create and conform to a protocol-known in some languages [...]