# HTTP HTTP (Hypertext Transfer Protocol) is a stateless application-level protocol for distributed hypertext information systems. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ktor 3.6.0 Is Now Available! DevFeed: [Ktor 3.6.0 Is Now Available!]() Original publisher: [Read original article]() Author: Simon Vergauwen Published: 2026-09-18T10:45:56Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [Ktor](), [Kotlin](), [Netty](), [Authentication](), [HTTP](), [openid](), [multiplatform](), [clients](), [Routing (disambiguation)]() Tags: [authentication](), [clients](), [http](), [http-3](), [kotlin](), [kotlin-multiplatform](), [ktor](), [news](), [openid](), [quic](), [release](), [releases](), [routing](), [server]() ### AI overview Ktor 3.6.0 introduces experimental typed authentication with OpenID Connect support and HTTP/3 over QUIC for the Netty engine. The release also improves routing, request handling, and Kotlin Multiplatform client defaults. ### Source excerpt Ktor 3.6.0 is here! This release is full of new experimental features, including typed authentication capabilities with specialized support for OpenID Connect and HTTP/3 support for the Netty engine. There are also a few quality-of-life improvements for routing and request handling, more convenient defaults for Kotlin Multiplatform clients, and more. Check out What's new in [...] ## В "Архиве Интернета" из-за наплыва ботов могут блокировать и обычных пользователей DevFeed: [В "Архиве Интернета" из-за наплыва ботов могут блокировать и обычных пользователей]() Original publisher: [Read original article]() Author: Travis\_Macrif Published: 2026-09-17T13:18:01Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [Artificial Intelligence](), [HTTP](), [Google]() Tags: [ai](), [chatgpt](), [google](), [http](), [ip](), [tag-53b4ba2afbf0](), [tag-7e87c89650ab](), [tag-8fcb6037885f](), [tag-92fc4f083c94](), [tag-9d8cf70dc46c](), [tag-bd7eab81747d](), [tag-d96e238f1419](), [wayback-machine]() ### AI overview The Internet Archive deployed protections against automated and malicious bots targeting the Wayback Machine, but the measures have also blocked some legitimate users. The organization is trying to reduce false positives while combating large-scale data collection for AI model training. ### Source excerpt Некоммерческая организация "Архив Интернета" развернула средства защиты онлайн-библиотеки Wayback Machine от автоматизированных и вредоносных ботов, что стало приводить к блокировке и обычных пользователей, пытающихся получить доступ к ресурсу. Читать далее ## JavaScript bundling and HTTP performance trade-offs DevFeed: [JavaScript bundling and HTTP performance trade-offs]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-11-23T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [JavaScript](), [HTTP](), [Caching](), [browserify](), [Webpack]() Tags: [browserify](), [cache](), [engineering](), [http](), [infrastructure](), [js](), [news](), [webpack]() ### AI overview The article examines trade-offs between bundling JavaScript files, serving them separately, and using semantically related bundles. It explains how these approaches balance HTTP request overhead, browser fetch limits, cacheability, and unused downloaded code. ### Source excerpt By Craig Silverstein Bundling JavaScript files The traditional advice for web developers is to bundle the JavaScript files ... 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. ## Patching This Site's MCP Endpoint and Limiting What It Can Do DevFeed: [Patching This Site's MCP Endpoint and Limiting What It Can Do]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [Model Context Protocol](), [MCP Server](), [API](), [HTTP](), [JSON]() Tags: [aeo](), [agent-ready-website](), [agentic-ai](), [agents](), [api](), [api-security](), [clients](), [json-rpc](), [logs](), [mcp](), [mcp-server](), [model-context-protocol](), [prompt-injection](), [protocol](), [rate-limiting](), [retry](), [server](), [streamable-http](), [webmcp]() ### AI overview This article explains how to patch a website's public, unauthenticated MCP endpoint. It covers updating to the current protocol revision while retaining compatibility with older clients, and applying limits including read-only tools, per-IP rate limiting, request-size caps, Origin checks, POST-only access, non-reflected strings, and privacy-preserving logs. ### Source excerpt An MCP server on your website is a public, unauthenticated API. Bringing one to the current protocol revision while keeping older clients working, and the seven limits that bound it: read-only tools, a per-IP rate limit that always sends Retry-After, hard caps on body and argument size, an https-only Origin check, POST only, no reflected strings, and logs that store a salted hash instead of an address. ## 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. ## curl 8.22.0 DevFeed: [curl 8.22.0]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-09-02T05:52:46Z Content type: release Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Security](), [HTTP](), [openssl](), [API](), [TLS (Transport Layer Security)](), [Command-line interface]() Tags: [bugfixes](), [command-line](), [curl](), [curl-and-libcurl](), [cve](), [cves](), [http](), [openssl](), [release](), [security](), [tls]() ### AI overview The curl 8.22.0 release includes six changes, 302 bug fixes, and nine curl/libcurl security fixes plus one wcurl fix. It adds Apple GSS Framework support, API guards, experimental HTTP Message Signatures support, and Apple fast UDP, while blocking NTLM fallback in SPNEGO and dropping TLS-SRP support. ### Source excerpt Welcome to this new release. Get it as always from https://curl.se. If you rather want a security-patched older release branch, stay tuned for the follow-up Rock-solid curl announcement within a few days. Release presentation Numbers the 276th release6 changes70 days (total: 10,887)302 bugfixes (total: 14,489)525 commits (total: 39,608)0 new public libcurl function (total: 100)4 new ... Continue reading curl 8.22.0 -> ## Cypress 16: faster tests, starting with HTTP/2 support DevFeed: [Cypress 16: faster tests, starting with HTTP/2 support]() Original publisher: [Read original article]() Published: 2026-09-01T17:28:34Z Content type: release Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [HTTP](), [Chromium](), [Node.js](), [Streaming](), [Vite]() Tags: [chromium](), [ci](), [cypress](), [http](), [node-js](), [streaming](), [tests](), [vite]() ### AI overview Cypress 16 improves end-to-end test performance with HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie and storage commands, and automatic memory management. The release also updates Node.js, Electron, and Chromium versions and removes Cypress.env() as part of its security work. ### Source excerpt Cypress 16 goes after slow test suites from every angle: HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie commands, and automatic memory management. Most of it arrives without editing a single test. Here's what changed, why, and how to upgrade. ## Classify Domain and System Errors to Set HTTP Status, Logging, and Paging DevFeed: [Classify Domain and System Errors to Set HTTP Status, Logging, and Paging]() Original publisher: [Read original article]() Author: The T-Shaped Dev Published: 2026-08-29T04:19:38Z Content type: tutorial Language: en Sources: [The T-Shaped Dev]() Topics: [Code](), [HTTP](), [API]() Tags: [api](), [code](), [errors](), [graphql](), [http](), [logs](), [middleware](), [on-call]() ### AI overview This tutorial distinguishes expected domain errors, such as invalid input or forbidden actions, from unexpected system errors, such as database failures, upstream timeouts, and memory exhaustion. It proposes encoding the distinction in error types so middleware can determine the HTTP status, user message, log level, and paging behavior. ### Source excerpt One distinction that sets your HTTP status, your log level, and who gets paged. (6 min) ## 【kube-apiserver】Watch 路径（服务端）：长连接、410 Gone 与 timeout DevFeed: [【kube-apiserver】Watch 路径（服务端）：长连接、410 Gone 与 timeout]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [HTTP](), [kubectl]() Tags: [410-gone](), [apiserver](), [bookmark](), [cacher](), [distributed](), [etcd](), [etcd3](), [informer](), [kubernetes](), [resourceversion](), [rest](), [timeout](), [v1-30-3](), [watch]() ### AI overview This article explains the Kubernetes v1.30.3 apiserver Watch path, from the REST handler through cacher and etcd3 watchers. It distinguishes 410 Gone caused by cacher ring-buffer eviction from errors propagated from etcd compaction, and covers resourceVersion semantics, timeouts, bookmarks, connection lifecycle, and the boundary with client-go Informer. ### Source excerpt 钉 Kubernetes v1.30.3 服务端 Watch 路径：从 REST handler 到 cacher/etcd3 watcher 的建立过程、resourceVersion=0 与具体 RV 的语义差异、410 Gone 与 etcd ErrCompacted 的映射、bookmark 推送与连接生命周期，以及与 client-go Informer 的边界。 ## Security Week 2635: вредоносное ПО в автомобильных Android-устройствах DevFeed: [Security Week 2635: вредоносное ПО в автомобильных Android-устройствах]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-08-25T08:00:25Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Security](), [Android](), [APK](), [HTTP](), [WebView]() Tags: [2026](), [android](), [apk](), [badbox](), [http](), [security](), [tag-9fe8963de219](), [webview]() ### AI overview Kaspersky researchers discovered Android malware installed on DoFun automotive head units. The JarService dropper downloads a clicker for advertising banners and a reverse-proxy module, linking the campaign to attacks on Android TV set-top boxes and the BADBOX platform. ### Source excerpt Исследователи "Лаборатории Касперского" обнаружили новый Android-зловред, уникальной особенностью которого является установка на головное устройство автомобиля. Вредоносное ПО использовало особенности головных устройств производителя DoFun, позволявшие устанавливать произвольные APK-файлы. Целью распространения вредоносного ПО являлось мошенничество с рекламными баннерами и использование автомобильной магнитолы в качестве прокси-сервера. Исследование кода выявило связи с другими атаками, нацеленными, например, на телеприставки под управлением Android. Расследование началось в июне 2026 года, когда специалисты "Лаборатории Касперского" обнаружили новый дроппер JarService. Зловред устанавливался как обычное пользовательское приложение и никак не маскировался под легитимное ПО. Точнее, у него полностью отсутствовал интерфейс, что указывало на возможность установки без ведома пользователя. Дроппер расшифровывает данные и запускает следующий этап атаки -- вредоносный загрузчик. Он, в свою очередь, отправляет информацию на командный сервер злоумышленников, скачивает оттуда и запускает финальную полезную нагрузку -- кликер на рекламные баннеры и реверс-прокси. Читать далее ## Choosing an HTTP Status for AI Agent Authorization Through Transparent Proxies DevFeed: [Choosing an HTTP Status for AI Agent Authorization Through Transparent Proxies]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [API](), [AI Agent](), [HTTP](), [Authentication]() Tags: [agents](), [ai-agent](), [api](), [authentication](), [http](), [rest]() ### AI overview This article explains how a transparent proxy for AI agents should respond when a user has not connected a third-party API. It examines why 401 and 403 conflict with existing authentication and provider-response meanings, and discusses the proposed response shape and the x402 standard. ### Source excerpt Your agent calls a third-party API for a user who never connected it. What to send back, why 401 and 403 are both already taken, and what the x402 standard means for the answer. ## SCIM Deprovisioning Is a Promise Your App Probably Breaks DevFeed: [SCIM Deprovisioning Is a Promise Your App Probably Breaks]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T01:29:36Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Security](), [API](), [HTTP](), [JSON](), [Internet Engineering Task Force (IETF)](), [Protocol (disambiguation)]() Tags: [api](), [http](), [identity](), [idp](), [ietf](), [json](), [net-conf](), [protocol](), [schema](), [security](), [standards](), [state](), [token]() ### AI overview This article explains that SCIM deprovisioning updates identity state but does not automatically invalidate an application's sessions, refresh tokens, or API keys. It describes how identity providers commonly use soft deactivation and why applications must explicitly handle the resulting offboarding state. ### Source excerpt SCIM tells you a user is gone, but sessions, refresh tokens, and API keys often outlive deprovisioning. Here's why offboarding needs more than a user row. ## Webinar Recap: Giving AI agents a native way to pay with x402 DevFeed: [Webinar Recap: Giving AI agents a native way to pay with x402]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-08-05T18:55:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Artificial Intelligence](), [Transactions](), [HTTP](), [API]() Tags: [ai](), [ai-agents](), [api](), [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [developers](), [http](), [nfts](), [payments](), [podcasts](), [recap](), [solana](), [solana-ecosystem](), [stablecoins](), [transactions](), [web3]() ### AI overview The article recaps a webinar about x402, a protocol that uses HTTP 402 and stablecoins to let AI agents discover, pay for, and access web resources without human-managed accounts or API keys. It describes use cases including micropayments, budget-aware purchasing, and autonomous earning and spending. ### Source excerpt X402 has processed roughly 200M transactions and $50B in volume, giving AI agents a stablecoin-native way to pay for web resources. ## Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp) DevFeed: [Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp)]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-07-31T23:13:22Z Content type: article Language: en Sources: [Simon Willison]() Topics: [Model Context Protocol](), [Large Language Model](), [anthropic](), [HTTP](), [Command-line interface](), [JSON](), [Python](), [web applications]() Tags: [2026](), [agent](), [ai](), [ai-2-235](), [anthropic](), [anthropic-336](), [cli](), [codex](), [context](), [curl](), [datasette](), [datasette-1-542](), [generative-ai](), [generative-ai-1-981](), [http](), [json](), [llm](), [llm-631](), [llms](), [llms-1-947](), [mcp](), [mermaid](), [mermaid-5](), [model-context-protocol](), [model-context-protocol-35](), [projects](), [projects-553](), [shell](), [stateless](), [terminal]() ### AI overview This commentary examines the 2026-07-28 stateless Model Context Protocol specification. It argues that stateless MCP simplifies client and server implementation, improves auditability and control compared with shell-based agent access, and better supports scalable web applications by removing session state and session-affinity requirements. The article also introduces the mcp-explorer CLI tool and mentions datasette-mcp. ### Source excerpt Tuesday was Stateless MCP day - the rollout of MCP 2.0, or the 2026-07-28 Model Context Protocol specification to use the more formal but less memorable name. This is the most significant change to the MCP spec since it first launched, and has also served to reignite my personal interest in the protocol. For background: MCP is the Model Context Protocol, which describes a standard way to expose new tools to LLM-powered agent frameworks. It was introduced by Anthropic back in November 2024, had a huge spike of interest through much of 2025, and then became somewhat eclipsed by Skills (another Anthropic invention) when it became apparent that an agent harness with access to a terminal and curl could do most of what MCP did in a more flexible way. I wrote about that in my review of 2025. I'm coming back around to MCP now. Giving an agent a shell environment with the ability to access the internet is fraught with risk, and requires a strong model that is capable of effectively driving such an environment. MCP tools are easier to audit and control, and simple enough that smaller models that run on a laptop can still drive them reasonably well. The new stateless MCP specification also greatly decreases the complexity of implementing both clients and servers for the protocol. I built three of those this week! What's easier with stateless MCP The best demonstration of the difference between stateful and stateless MCP is in this May 21st blog post that introduced the RC for the new specification. It included a clear before-and-after example. The older stateful MCP (I'm going to call it "legacy MCP") required two HTTP requests - the first to initialize a session and obtain a Mcp-Session-Id, and the second to actually call the tool: POST /mcp HTTP/1.1 Content-Type: application/json { "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2025-11-25", "capabilities": { }, "clientInfo": { "name": "my-app", "version": "1.0" } } } POST /mcp HTTP/1.1 Mcp ## What's new in the MCP 2026-07-28 specification DevFeed: [What's new in the MCP 2026-07-28 specification]() Original publisher: [Read original article]() Author: Aditya Oberai Published: 2026-07-30T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Model Context Protocol](), [MCP Server](), [HTTP](), [Routing (disambiguation)](), [Caching](), [Authorization](), [Remote Procedure Call (RPC)]() Tags: [caching](), [http](), [mcp](), [mcp-server](), [model-context-protocol](), [news](), [routing](), [rpc]() ### AI overview The article explains changes in the MCP 2026-07-28 specification, focusing on the move from stateful sessions to a stateless request/response core. It covers implications for routing, load balancing, caching, authorization, and server migration. ### Source excerpt The MCP 2026-07-28 spec drops sessions, adds header based routing, cacheable lists, and MRTR. Here is what changed and what you need to migrate your servers. ## HTTP QUERY: the method that was missing between GET and POST DevFeed: [HTTP QUERY: the method that was missing between GET and POST]() Original publisher: [Read original article]() Author: Matteo Baccan Published: 2026-07-29T12:26:29Z Content type: article Language: en Sources: [Backend Job: skill, salary and insights - Codemotion Magazine]() Topics: [HTTP](), [Back end](), [Web](), [Security](), [Caching]() Tags: [backend](), [caching](), [firewall](), [http](), [http-query](), [ietf](), [load-balancing](), [post](), [security](), [siem](), [web]() ### AI overview This article examines the proposed HTTP QUERY method, which is intended to combine the safety and idempotency of GET with the ability to carry an extended request body like POST. It discusses the limitations and security risks of putting complex or sensitive queries in URLs, and considers the method's effects on caching, infrastructure compatibility, and future backend implementation. ### Source excerpt For nearly thirty years, the Web has lived with a semantic paradox that anyone developing for the backend knows well: how do you execute a complex, voluminous query, or one containing sensitive data, if the only "safe" method available does not allow a request body? Think about when we need to send a structured search... Read more The post HTTP QUERY: the method that was missing between GET and POST appeared first on Codemotion Magazine. ## HTTP Message Signatures with curl DevFeed: [HTTP Message Signatures with curl]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-07-27T06:55:03Z Content type: release Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [HTTP](), [Authentication]() Tags: [curl](), [curl-and-libcurl](), [digital-signatures](), [ed25519](), [experimental](), [git](), [hmac](), [http](), [production](), [release]() ### AI overview curl experimentally supports HTTP Message Signatures based on RFC 9421, allowing users to sign selected HTTP request components with ed25519 or hmac-sha256 through new command-line and libcurl options. The feature must be explicitly enabled, is discouraged for production use, and is planned for curl 8.22.0. ### Source excerpt The recently published RFC 9421 describes how to do HTTP Message Signatures, and starting just now, curl experimentally supports them. Message Signatures The specification describes this as a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. It is a way to verify that selected parts ... Continue reading HTTP Message Signatures with curl -> ## RFC 9880 and the IoT Validation Problem DevFeed: [RFC 9880 and the IoT Validation Problem]() Original publisher: [Read original article]() Author: Stefano Fago Published: 2026-07-26T00:00:00Z Content type: article Language: en Sources: [Nicolas Fränkel]() Topics: [Internet of things](), [SDF](), [data](), [JSON](), [Code](), [CoAP](), [MQTT](), [HTTP](), [TLS (Transport Layer Security)]() Tags: [architecture](), [code](), [data](), [development](), [iot](), [json](), [protocol](), [sdf](), [standards](), [validation]() ### AI overview This article examines RFC 9880 and its Semantic Definition Format (SDF) as an ecosystem-neutral, JSON-based way to describe IoT devices. It argues that SDF validation is best understood as a compilation problem and discusses how different IoT ecosystems represent the same physical concepts incompatibly. ### Source excerpt The IoT/IIoT world has a data model problem and the concept of Digital Twin has made this issue more important. Plenty of people have tried to fix it. RFC 9880 and its Semantic Definition Format (SDF) are a serious attempt: a JSON-based, ecosystem-neutral way to describe what a device is and what it does. I have had some experiences with this specification, and I've understood that the format shows its full value once you treat it as source code, something you compile. ## Calendar API: Local Calendars, Cloud Sync, and Conflict Handling DevFeed: [Calendar API: Local Calendars, Cloud Sync, and Conflict Handling]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-25T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [API](), [cross-platform](), [Concurrency](), [Cloud](), [Google Calendar](), [Android](), [iOS](), [macOS](), [Microsoft](), [JavaScript](), [HTTP](), [OAuth]() Tags: [android](), [api](), [apis](), [apple](), [backend](), [cloud](), [concurrency](), [cross-platform](), [google](), [http](), [ios](), [javascript](), [macos](), [oauth](), [offline](), [storage](), [sync](), [synchronization](), [work]() ### AI overview The article introduces a cross-platform calendar API that unifies local calendars and cloud providers through a capability-based model. It covers events, tasks, recurrence, time zones, offline mutations, optimistic concurrency, provider synchronization, and conflict handling. ### Source excerpt The new calendar API handles local calendars, cloud providers, recurrence, conflicts, and offline changes through one capability-based model. ## What is a remote MCP server? DevFeed: [What is a remote MCP server?]() Original publisher: [Read original article]() Author: Jacob Schmitt Published: 2026-07-24T16:00:00Z Content type: tutorial Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [Model Context Protocol (MCP)](), [MCP Server](), [AI Agent](), [HTTP](), [Command-line interface]() Tags: [ai-agent](), [circleci-mcp-server](), [hosted-mcp-server](), [how-to](), [http](), [local-vs-remote-mcp](), [mcp](), [mcp-oauth](), [mcp-server](), [model-context-protocol](), [remote-mcp-server](), [remote-vs-local-mcp-server](), [what-is-a-remote-mcp-server]() ### AI overview This explainer defines remote or hosted MCP servers, which let AI agents access external tools over HTTP from cloud-based or background environments. It compares remote and local MCP servers and describes connecting an AI agent to CircleCI through a hosted MCP server. ### Source excerpt A remote MCP server is a hosted MCP server your AI agent reaches over HTTP instead of running locally. Here's how remote and local MCP servers differ, and how to connect an AI agent to CircleCI using the new remote MCP. ## Drag, drop, done: a visual composer for Redpanda Connect DevFeed: [Drag, drop, done: a visual composer for Redpanda Connect]() Original publisher: [Read original article]() Author: Prakhar Garg Published: 2026-07-23T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Redpanda-Connect](), [Canvas](), [stream-processing](), [Caching](), [Routing (disambiguation)](), [HTTP](), [n8n](), [workflow automation]() Tags: [api](), [automation](), [building](), [cache](), [caching](), [events](), [front-end](), [http](), [n8n](), [pipeline](), [redpanda-connect](), [routing](), [stream-processing](), [workflow]() ### AI overview Redpanda introduces a visual Pipeline Builder for Redpanda Connect, using a drag-and-drop canvas to compose pipelines from inputs, processors, and outputs. The builder generates YAML while making routing, enrichment, caching, error handling, and retries easier to understand and configure. The article contrasts it with n8n, emphasizing Redpanda Connect's suitability for high-volume event streaming with ordering, backpressure, and exactly-once semantics. ### Source excerpt A first look at the new visual Pipeline Builder for Redpanda Connect (preview), plus a roundup of recent CDC and connector updates. ## Собрать прошлое: как архивировать весь трафик сборки SONiC DevFeed: [Собрать прошлое: как архивировать весь трафик сборки SONiC]() Original publisher: [Read original article]() Author: denballakh (Яндекс, Yandex Cloud & Yandex Infrastructure) Published: 2026-07-20T07:03:18Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Docker](), [Debian](), [HTTP](), [docker registry](), [GitHub](), [PyPI](), [Python]() Tags: [build](), [debian](), [docker](), [docker-registry](), [github](), [http](), [infrastructure](), [mitm](), [proxy](), [pypi](), [reproducibility](), [sonic]() ### AI overview This article explains how Yandex Infrastructure developed a caching MITM proxy for SONiC and YaSONiC builds. The proxy captures HTTP/HTTPS traffic and serves previously saved responses to improve build reproducibility when external dependencies change or disappear. ### Source excerpt Интернет -- это зависимость без зафиксированной версии. Сегодня он возвращает одно, завтра -- другое, а послезавтра -- ничего. Поэтому мы решили сохранить для сборки тот интернет, который она однажды увидела. Для этого пришлось перехватывать HTTPS, выпускать собственные сертификаты, переподписывать индексы Debian и выяснять, почему Docker отправляет "случайные" заголовки. В этой статье я расскажу, как разрабатывал кеширующую MITM-проксю, которая перехватывает весь HTTP/HTTPS-трафик и отдаёт ранее сохранённые ответы. Разберём также неочевидные технические проблемы, с которыми пришлось столкнуться. Читать далее [Next page]()