# client A client is a program that establishes a connection to a server to send requests. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Раскрыта уязвимость BrokenPipe в клиенте Steam, которая позволяет повысить привилегии в Windows до SYSTEM DevFeed: [Раскрыта уязвимость BrokenPipe в клиенте Steam, которая позволяет повысить привилегии в Windows до SYSTEM]() Original publisher: [Read original article]() Author: denis-19 Published: 2026-09-17T02:25:27Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [vulnerability](), [Exploit](), [client](), [Windows](), [Windows 11]() Tags: [2026](), [brokenpipe](), [poc](), [steam](), [vulnerability](), [windows]() ### AI overview A developer disclosed BrokenPipe, a critical zero-day privilege-escalation vulnerability in Steam Client Service on Windows. The published proof of concept reportedly allows a local user with code execution to run a launcher with SYSTEM privileges. The issue was reportedly disclosed to Valve in March 2026 and had not been fixed at the time described. ### Source excerpt Разработчик Джейдип Модхвадия (aka KillaBoi) раскрыл информацию о критической уязвимости нулевого дня (BrokenPipe - Steam Client Service LPE Vulnerability) в клиенте Steam в Windows, использование которой позволяет любому обычному пользователю незаметно повысить права в системе до полных привилегий SYSTEM. Читать далее ## Khan Academy Uses Local Storage and Request Queues to Handle Offline Actions DevFeed: [Khan Academy Uses Local Storage and Request Queues to Handle Offline Actions]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-08-17T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [LocalStorage](), [client](), [Code](), [Internet](), [servers]() Tags: [architecture](), [change](), [code](), [engineering](), [function](), [hints](), [linear](), [local](), [news](), [offline](), [queue](), [request](), [server](), [web-frontend]() ### AI overview This article explains how Khan Academy addressed offline hint cheating by changing the client's request architecture. Actions are stored in local storage and placed in a queue for retry when connectivity returns, with linear backoff to avoid repeated requests during outages. ### Source excerpt By Phillip Lemons The problem Recently, a number of students on Khan Academy found a way to cheat ... Read more ## MCP went stateless: What changed in the 2026-07-28 spec DevFeed: [MCP went stateless: What changed in the 2026-07-28 spec]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Model Context Protocol](), [migration](), [HTTP](), [servers](), [client]() Tags: [api](), [client](), [http](), [load-balancer](), [mcp](), [replacement](), [request](), [routing](), [server](), [servers](), [sessions](), [stateless](), [stream]() ### AI overview The 2026-07-28 MCP specification removes protocol-level sessions, the initialize handshake, and stream resumability, making the protocol behave more like an ordinary HTTP API. Most migrations are mechanical, but lost stream requests can cause reliability regressions or duplicated side effects when retried, so side-effecting tools need application-level idempotency keys. The elicitation change also requires architectural rework. ### Source excerpt Sessions, the initialize handshake, and stream resumability are all gone. Here is what replaced them, and what breaks if you ignore it. ## How end-to-end SLO monitoring detected a livestream failure that component dashboards missed DevFeed: [How end-to-end SLO monitoring detected a livestream failure that component dashboards missed]() Original publisher: [Read original article]() Author: Whatnot Engineering Published: 2026-09-15T16:31:01Z Content type: article Language: en Sources: [Whatnot Engineering]() Topics: [dashboards](), [observability](), [incident](), [Monitoring](), [Web](), [client](), [Network]() Tags: [dashboards](), [distributed-systems](), [incident](), [monitoring](), [observability](), [security](), [server](), [site-reliability-engineer](), [software-engineering](), [web]() ### AI overview The article examines a June 8, 2026 incident in which a third-party client-side security script fetched from a provider CDN added URL validation that the video provider did not pass, causing black screens for newly loaded web clients. Most component-level dashboards remained green, while end-to-end service-level objective monitoring detected the broken livestream experience and paged the owning teams within five minutes. ### Source excerpt Karol Gil | Reliability Platform (Poland) On June 8, 2026, newly loaded web clients began showing black screens instead of livestream video. For our platform, that's a serious problem: it's pretty hard to sell Pokémon cards that no one can see. It turned out that a third-party script we use for client-side security monitoring wasn't bundled with our release, but was rather fetched live from the provider's CDN. When the provider updated the script all new web clients fetched it, and it included an additional URL validation which our video provider didn't pass. The result? Black screens for users of the affected web clients, with most internal dashboards staying green. 3,000 users were impacted in the first 30 minutes of the incident. One system did catch it. Our end-to-end service-level objective (E2E SLO) monitoring was already in production and paged the owning teams within five minutes. Here's what it saw. The real problem Most of our dashboards stayed green because they monitor component-level health: a server, an endpoint, a specific function. These are all useful, but can all be healthy while the actual user experience is completely broken. This problem gets worse the more external dependencies there are, or the more sophisticated an experience you want to deliver. In complex, integrated product experiences like ours, a "small" problem can have an outsize impact on the user experience. Measuring this requires a different approach to observability, namely, to model the user journey across multiple surfaces that must be true for a customer to have a good experience. So how do we measure this in a complex distributed application? Joining a livestream is not one thing Joining a livestream sounds like one action, but the user expects at least three things: Video to be playing Auction details to be shown Chat to be visible and up to da Each of those can succeed or fail completely independently of the other two. Our video depends on third-party providers and CDN netwo ## 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... ## Gitte As Git Client For GNOME Continues Maturing Quite Nicely DevFeed: [Gitte As Git Client For GNOME Continues Maturing Quite Nicely]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T00:35:39Z Content type: news Language: en Sources: [Phoronix]() Topics: [Git](), [client](), [Submodules](), [Linux](), [App]() Tags: [app](), [bug-fixes](), [desktop](), [desktop-linux](), [git](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [submodules](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui]() ### AI overview Gitte 0.10 is a GTK4-based graphical Git client for GNOME and Linux. The release adds side-by-side diffs, Git LFS and submodule support, workflow shortcuts, UI improvements, and bug fixes. ### Source excerpt For those in pursuit of a graphical Git client for GNOME or the Linux desktop at large, the GTK4-powered Gitte continues advancing rather well and out this week is its v0.10 release... ## HTTP/3 Support in HTTP Client API in Java 26 DevFeed: [HTTP/3 Support in HTTP Client API in Java 26]() Original publisher: [Read original article]() Author: Rajat Garg Published: 2026-09-10T18:50:56Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Java HttpClient](), [client](), [Networks](), [Latency]() Tags: [api](), [http](), [java](), [java-httpclient](), [latency](), [networking](), [networking-java-httpclient](), [networks](), [popular](), [tls](), [tutorial]() ### AI overview A tutorial on using Java 26's HttpClient API with HTTP/3, including protocol preference and server-support discovery. ### Source excerpt Learn how HttpClient API supports HTTP/3 now, and how to set your apps to use HTTP/3. The post HTTP/3 Support in HTTP Client API in Java 26 first appeared on Baeldung. ## Kubernetes access via an identity provider: Public client, not confidential DevFeed: [Kubernetes access via an identity provider: Public client, not confidential]() Original publisher: [Read original article]() Author: Kolawole Olowoporoku | CNCF Ambassador and Senior Platform Engineer Published: 2026-09-08T11:30:00Z Content type: tutorial Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Kubernetes](), [Authorization](), [client]() Tags: [api](), [architecture](), [authentication](), [blog](), [browser](), [iam](), [identity](), [integration](), [kubernetes](), [on-prem](), [operations]() ### AI overview The article explains how to replace static Kubernetes credentials with identity-provider login using a public OIDC client and PKCE. It describes kubectl with kubelogin, Keycloak, kube-apiserver token validation, and RBAC-based access decisions. ### Source excerpt Access control belongs on the same day-zero checklist as networking and storage. On most on-prem clusters, it never makes the list. The Identity Gap Managed cloud Kubernetes ships IAM or SSO integration out of the box.... ## What Is the x402 Protocol? HTTP 402 Payments for AI Agents DevFeed: [What Is the x402 Protocol? HTTP 402 Payments for AI Agents]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [AI Agent](), [API](), [client](), [Model Context Protocol]() Tags: [agent](), [agents](), [ai](), [ai-agent](), [ai-agents](), [api](), [autonomous](), [coinbase](), [guide](), [http](), [mcp](), [model-context-protocol](), [payments](), [tools]() ### AI overview A technical guide to x402, an open payment standard that uses HTTP 402 to let clients pay for individual API requests without accounts, API keys, sessions, or subscriptions. It explains the payment handshake, the roles of clients, resource servers, and facilitators, plus x402's use over HTTP, MCP, and A2A transports. ### Source excerpt A technical guide to the x402 protocol: how the HTTP 402 payment handshake works, the PAYMENT-REQUIRED and PAYMENT-SIGNATURE headers, facilitators, payment schemes, and where x402 fits next to card rails. ## A countdown that stays accurate in a background tab DevFeed: [A countdown that stays accurate in a background tab]() Original publisher: [Read original article]() Author: Marko Published: 2026-09-05T06:30:19Z Content type: tutorial Language: en Sources: [Marko Denic Tech]() Topics: [web applications](), [client](), [Server]() Tags: [blog-for-developers](), [browsers](), [bug](), [build-faster](), [code-productivity](), [code-smarter](), [content-monetization](), [css-animation](), [css-performance](), [developer-growth](), [developer-resources](), [email-newsletter-for-coders](), [front-end-development](), [github-profile-automation](), [html](), [html-tips](), [http](), [javascript](), [javascript-tricks](), [learn-to-code](), [responsive-design-tips](), [server](), [ui](), [web-dev-newsletter](), [web-development](), [web-development-tips](), [weekly-dev-tips](), [workflow-optimization]() ### AI overview A tutorial on building accurate web countdowns despite background-tab timer throttling. It recommends calculating remaining time from an absolute deadline, forcing a render when a tab returns, and treating the server clock as the authority for consequential expirations. ### Source excerpt Your checkout timer says 4:55 when the cart already expired. Why background tabs break setInterval countdowns, and the three-line fix. ## The Evolution of HTTP, Clearly Explained DevFeed: [The Evolution of HTTP, Clearly Explained]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-09-04T16:39:02Z Content type: article Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [HTTP](), [client](), [servers](), [Caching](), [Web]() Tags: [browser](), [caching](), [encoding](), [evolution](), [http](), [http-3](), [protocol](), [request](), [responses](), [server](), [tcp]() ### AI overview An explanatory article traces HTTP from versions 0.9 through 1.1, describing how headers, status codes, persistent connections, caching, and chunked transfer encoding addressed the web's growing scale and performance needs. It introduces HTTP/3 as part of that broader evolution. ### Source excerpt From 0.9 to 3.0: What changed and why? ## Fixed window, sliding window, or token bucket? Choosing a rate limit strategy in Appwrite Firewall DevFeed: [Fixed window, sliding window, or token bucket? Choosing a rate limit strategy in Appwrite Firewall]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-04T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Firewall](), [Algorithms](), [HTTP](), [client]() Tags: [firewall](), [http](), [rate-limiting](), [security](), [strategy]() ### AI overview This article explains the fixed window, sliding window, and token bucket rate-limiting strategies supported by Appwrite Firewall. It compares how they handle bursts and time-window boundaries, describes IP- and User ID-based limits, and explains how to choose a strategy. ### Source excerpt Appwrite Firewall rate limit rules support three strategies. Learn how fixed window, sliding window, and token bucket work, where each one breaks down, and how to pick the right one for your traffic. ## JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled DevFeed: [JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-03T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Databases](), [Latency](), [client](), [Code]() Tags: [batching](), [bulk-load](), [client](), [cost](), [database](), [database-performance](), [durability](), [jdbc](), [latency](), [mysql](), [postgresql](), [server](), [sql]() ### AI overview For small database writes, network round trips and transaction overhead can dominate the actual insert work. The article explains that JDBC batching may accept rows into a client-side batch while still sending separate statements unless driver-side statement rewriting is enabled, and that autocommit adds a transaction and durability barrier per row. ### Source excerpt For small writes the per-statement overhead dominates the actual work, so throughput is set by round trips rather than by the database. JDBC batching is the usual fix and it silently does nothing on the wire unless the driver is told to rewrite the statements, so addBatch can look correct while still issuing one round trip per row. Autocommit compounds it by turning every row into its own transaction and its own durability barrier, which is the difference between one fsync and a hundred thousand. ## Finding three-way API drift with the AI Engineer DevFeed: [Finding three-way API drift with the AI Engineer]() Original publisher: [Read original article]() Author: Talia Kohan Published: 2026-09-01T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [API](), [Postman](), [OpenAPI Specification](), [Claude](), [Tooling](), [client](), [servers]() Tags: [ai-engineer](), [api](), [api-drift](), [apis](), [ci](), [fintech](), [general](), [openapi](), [postman-ai-engineer](), [production](), [qa]() ### AI overview The article explains how to detect three-way API drift by comparing an OpenAPI specification, the requests in Postman Collections, and the responses returned by a running server. It argues that pairwise checks can miss cases where all three sources disagree, and describes using Postman AI Engineer and the Context Graph to identify these inconsistencies. ### Source excerpt Find three-way API drift with Postman AI Engineer and the Context Graph. Compares your OpenAPI spec, collection requests, and live server responses. The post Finding three-way API drift with the AI Engineer appeared first on Postman Blog. ## If you have to ask, is it accessible? DevFeed: [If you have to ask, is it accessible?]() Original publisher: [Read original article]() Author: George Joeckel Published: 2026-08-31T20:02:26Z Content type: opinion Language: en Sources: [WebAIM Blog]() Topics: [Accessibility](), [ACR](), [configuration](), [client](), [Hardware](), [Software]() Tags: [accessibility](), [acr](), [customer](), [hardware](), [internet](), [legal](), [product](), [software](), [uncategorized]() ### AI overview The article examines why vendors often require potential customers to request a VPAT instead of publishing it publicly. It explains that a VPAT translates accessibility requirements into testing criteria, while a completed VPAT is called an Accessibility Conformance Report (ACR). The article also introduces possible vendor concerns involving customized information, competitive information, and accurate product or configuration details. ### Source excerpt As one of the researchers identifying products and tools for inclusion in the NCADEMI EdTech Accessibility Directory, VPATs have been on my mind. Most of the product vendors in the directory that do have VPATs do not provide them publicly, but instead require a potential customer to request the VPAT. This really surprised me, and [...] ## Tailcat: Tailscale without Tailscale, by Tailscale DevFeed: [Tailcat: Tailscale without Tailscale, by Tailscale]() Original publisher: [Read original article]() Author: Brad Fitzpatrick Published: 2026-08-31T14:00:00Z Content type: article Language: en Sources: [Blog on Tailscale]() Topics: [Go Language](), [Command-line interface](), [Open Source](), [client](), [Encryption](), [Server](), [Security](), [Linux](), [Android](), [Single sign-on (SSO)]() Tags: [android](), [cli](), [encryption](), [go](), [identity](), [linux](), [open-source](), [remix](), [security]() ### AI overview Tailcat is an open-source Go package and CLI that uses Tailscale's data plane--WireGuard encryption, NAT traversal, and DERP--to provide netcat-like client and server connectivity without the Tailscale control plane, accounts, or administrative controls. ### Source excerpt A netcat-ish way to use Tailscale's data plane without its control plane ## How to verify WorkOS access tokens in your own API DevFeed: [How to verify WorkOS access tokens in your own API]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-28T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [API](), [Android](), [SDKs](), [servers](), [client]() Tags: [android](), [api](), [how-to](), [http](), [jwks](), [node]() ### AI overview This tutorial explains how to verify WorkOS access tokens in a Node API, using an Android client as the example. It covers bearer-token handling, JWKS-based signature verification, claim extraction, caller identity, and distinct responses for invalid tokens, temporary verification failures, and expired tokens. ### Source excerpt Using an Android client and a Node API, including the JWKS failure mode that quietly returns the wrong status code ## How to Work With Your Client's Next (Or Previous) Developer DevFeed: [How to Work With Your Client's Next (Or Previous) Developer]() Original publisher: [Read original article]() Author: Eric Karkovack Published: 2026-08-25T11:20:05Z Content type: article Language: en Sources: [Speckyboy Design Magazine]() Topics: [client](), [Processes]() Tags: [developer](), [developers](), [freelance-business](), [freelance-career](), [freelance-design](), [how-to](), [payment](), [wordpress](), [wordpress-agency](), [work]() ### AI overview This article offers practical advice for managing website handoffs between a client's current and incoming developers. It recommends staying professional, documenting processes, responding promptly, avoiding conflict, and ensuring outstanding payments are settled before transferring site assets or access. ### Source excerpt Website handoffs between developers can get awkward. Learn how to stay professional, get paid before transferring assets, and share logins, licenses, and access without creating risk. The post How to Work With Your Client's Next (Or Previous) Developer appeared first on Speckyboy Design Magazine. ## HTTP Client SSRF Mitigation with InetAddressFilter in Spring Boot DevFeed: [HTTP Client SSRF Mitigation with InetAddressFilter in Spring Boot]() Original publisher: [Read original article]() Author: Hamid Reza Sharifi Published: 2026-08-22T23:16:19Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Spring Boot 4](), [Vulnerabilities](), [Security](), [client]() Tags: [how-to](), [http](), [security](), [spring](), [spring-boot](), [spring-boot-4](), [spring-boot-spring-boot-4](), [tutorial](), [vulnerability]() ### AI overview A tutorial on mitigating Server-Side Request Forgery (SSRF) in Spring Boot applications with InetAddressFilter. It explains how filtering resolved IP addresses can prevent HTTP clients from reaching unintended internal, loopback, or cloud metadata destinations, and introduces built-in filters and composable allowlist and blocklist rules. ### Source excerpt Learn how to use the InetAddressFilter class in a Spring-based application to limit the address that an HTTP client can call. The post HTTP Client SSRF Mitigation with InetAddressFilter in Spring Boot first appeared on Baeldung. ## \[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released DevFeed: [\[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released]() Original publisher: [Read original article]() Author: Patrick Donnelly Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [releases](), [Authentication](), [Linux](), [client](), [monitor]() Tags: [authentication](), [blog-post](), [cve](), [cves](), [en-article](), [en-blog-post](), [errors](), [linux](), [process](), [release](), [releases](), [rest](), [rgw](), [squid](), [tentacle](), [upgrade]() ### AI overview The Ceph project released Tentacle 20.2.4 and Squid 19.2.6 as hotfixes addressing four CVEs. The article urgently recommends upgrading and explains changes to CephX key types, daemon-key rotation, authentication controls, recovery procedures, and multisite RGW request signing. ### Source excerpt The Ceph project has released Tentacle 20.2.4 and Squid 19.2.6 hotfixes for four CVEs across several components. This is the sixth backport release in the Squid series. This is the fourth backport release in the Tentacle series. We strongly recommend that all Ceph operators upgrade to one of these releases as soon as possible. Release Date ¶ August 19, 2026 Critical Upgrade Steps ¶ The fix for CVE-2025-30156 introduces a new CephX key type, aes256k. This is the first time Ceph has introduced a new key type for CephX credentials. Therefore, a new procedure exists for upgrading and rotating Ceph daemon keys as part of this CVE. Before upgrading a Ceph cluster, the operator should familiarize themselves with the procedure to upgrade CephX keys. These steps are for package-based deployments of Ceph. In other sections, the document also includes new information about key rotation procedures, monitor authentication controls, and emergency recovery procedures. Deployments using cephadm will automate the process except for client keys. You may notice that Cephadm spends more time than normal on the upgrade after updating all daemon images. This is due to a new process rotating the OSD and MDS keys. Please be patient. There are plans to improve this in the future. Deployments using Rook will also automate rotation of some client keys with some exclusions. Look to the Rook project's announcement for more details. Client and kernel upgrades are recommended to support aes256k. Note that upstream Linux kernel client support began in kernel 7.0 and has been backported to CentOS Stream 9 and 10. Check with your distribution vendor for backported key support before rotating client keys used by the kernel. As part of upgrading a Ceph cluster, six new health warnings and errors will be generated. This is normal. As part of the process to upgrade/rotate entity keys, you will address the warnings and errors as you go. These are documented beginning here. The CephX documentation has bee ## Connect client traces to your logs DevFeed: [Connect client traces to your logs]() Original publisher: [Read original article]() Author: Katerina Skroumpelou; Steven Eubank Published: 2026-08-18T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [tracing](), [OpenTelemetry](), [client](), [Amazon API Gateway](), [browser](), [SIEM, Security, Observability]() Tags: [api](), [backend](), [browser](), [how-to](), [integration](), [opentelemetry](), [traces](), [tracing]() ### AI overview A walkthrough of connecting client-side traces to Supabase logs by propagating W3C Trace Context. It explains how to configure a tracer and client propagation so requests can be followed from the browser through Supabase's API Gateway and Edge Function logs, including with external log backends. ### Source excerpt supabase-js now propagates W3C Trace Context to Supabase, so a client trace and the matching Supabase log share one trace_id. ## Poisoned Postgres connection pools DevFeed: [Poisoned Postgres connection pools]() Original publisher: [Read original article]() Author: Josh Brown Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Database](), [postgresql clusters](), [client](), [API]() Tags: [api](), [database](), [engineering](), [postgres]() ### AI overview The article explains how stale session state can poison Postgres connection pools, causing reused connections to remain read-only and trigger errors. It focuses on connection pooling, PgBouncer transaction mode, and the resulting effects on client queries and API routes. ### Source excerpt An engineer's worst nightmare is waking up to a seemingly read-only database with no clear issue in sight. Let's dig into why this happens, and how AI can help solve it. ## Allocation Update - Q2 2026 DevFeed: [Allocation Update - Q2 2026]() Original publisher: [Read original article]() Author: Ethereum Foundation Ecosystem Support Program Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Resilience](), [zero-knowledge](), [client](), [Formal verification](), [Open Source](), [Tooling]() Tags: [2026](), [ecosystem-support-program](), [ethereum](), [formal-verification](), [network](), [open-source](), [resilience](), [tooling](), [update](), [zero-knowledge]() ### AI overview An update on Ethereum's Q2 2026 allocation efforts, covering support for zero-knowledge proofs, client diversity, formal verification, open-source tooling, and other ecosystem projects intended to strengthen the network. ### Source excerpt Q2 2026 carried forward our focus on advancing Ethereum's resilience and capabilities, supporting key work in zero-knowledge proofs, client diversity, formal verification, and open-source tooling. See the list below of the projects and ecosystem efforts supported this quarter as builders build and strengthen the network. Explore the full list... ## RFC 9470 explained: The OAuth step-up authentication challenge protocol DevFeed: [RFC 9470 explained: The OAuth step-up authentication challenge protocol]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [OAuth 2.0](), [Protocol (disambiguation)](), [API](), [Authentication](), [Authorization](), [OpenID connect (OIDC)](), [client]() Tags: [api](), [authentication](), [authorization](), [oauth](), [oauth-2-0](), [oidc](), [openid-connect](), [protocol]() ### AI overview This article explains RFC 9470, the OAuth 2.0 Step-Up Authentication Challenge Protocol. It describes how a resource server can tell a client that the current access token does not meet the required authentication level and how the client can obtain stronger authentication, including the roles of acr_values, max_age, and auth_time. ### Source excerpt How an API tells a client that the user needs to authenticate again, why acr_values is only a request while max_age is a requirement, and what the auth_time claim actually proves. [Next page]()