# websocket Published articles for websocket. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Gemini Live audio DevFeed: [Gemini Live audio]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-15T22:47:07Z Content type: tutorial Language: en Sources: [Simon Willison's Weblog]() Topics: [speech-to-speech](), [WebSocket](), [Google AI](), [browser](), [Playback](), [implementation](), [API]() Tags: [api](), [audio](), [browser](), [gemini](), [gemini-196](), [generative-ai](), [generative-ai-1-982](), [google](), [google-416](), [llm-release](), [llm-release-231](), [llms](), [llms-1-948](), [model](), [models](), [openai](), [playback](), [release](), [speech-to-speech](), [speech-to-text](), [speech-to-text-21](), [tools](), [tools-78](), [ui](), [voice](), [websocket](), [websockets](), [websockets-21]() ### AI overview The article describes a browser-based web UI for trying Google's Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking speech-to-speech models. The implementation supports model and voice selection, an optional system prompt, voice conversations, and interruption while the model is speaking. It uses no libraries, connecting to a WebSocket endpoint and using the Web Audio API for capture and playback. ### Source excerpt Tool: Gemini Live audio Google released Gemini 3.8 Live and 3.8 Live Extended Thinking today - two new speech-to-speech models that are a similar shape to OpenAI's GPT-Live family. I pointed GPT-6 Astra Extra High at the documentation and had it build me this web UI for trying out the new models. You can select a model and voice preset, enter an optional system prompt and then start a voice conversation through your browser, including the ability to interrupt the model while it is talking. The implementation uses no libraries. It connects to the wss://generativelanguage.googleapis.com/ws/google.ai.generativelanguage.v1alpha.GenerativeService.BidiGenerateContent?key=... WebSocket endpoint and uses a Web Audio API AudioContext for both capture and playback. Here's the Gemini Live tutorial for getting started with that WebSockets API. Tags: google, tools, websockets, generative-ai, llms, gemini, llm-release, speech-to-text ## Gemini 3.8 Live models now available on AI Gateway DevFeed: [Gemini 3.8 Live models now available on AI Gateway]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-09-15T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [real-time](), [Artificial Intelligence](), [API](), [Google](), [WebSocket](), [SDKs]() Tags: [ai](), [api](), [cost](), [failover](), [gemini](), [google](), [real-time](), [realtime](), [sdk](), [websocket]() ### AI overview Vercel announces that Google's Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking models are available on AI Gateway. The models support real-time spoken interactions, audio and visual grounding, multilingual switching, background tool calls, and parallel reasoning through the AI SDK's realtime API. ### Source excerpt Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking from Google are now available on AI Gateway. Both models support real-time spoken interactions for voice assistants, conversational experiences, and applications that respond through audio. google/gemini-3.8-live supports real-time audio, visual grounding, automatic switching across 97 languages, and background tool calls while the conversation continues. google/gemini-3.8-live-extended-thinking adds multi-step reasoning that runs in parallel with speech, allowing it to acknowledge requests and narrate progress without interrupting the conversation. Use either model through the AI SDK's realtime API. Install the Gateway provider and a WebSocket client: Mint a short-lived token, open the WebSocket, and use the model adapter to serialize and parse realtime events: See the realtime quickstart for more details on realtime events and WebSocket connections. Try Gemini 3.8 Live or Gemini 3.8 Live Extended Thinking in the model playground. AI Gateway provides a unified API for calling models, tracking usage and cost, and configuring retries, failover, and performance optimizations for higher-than-provider uptime. Read more ## How to Connect Your Twilio Agent to External APIs in Python DevFeed: [How to Connect Your Twilio Agent to External APIs in Python]() Original publisher: [Read original article]() Author: Amanda Lange, Dylan Frankcom Published: 2026-09-12T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Python](), [API](), [FastAPI](), [AI Agent](), [voice ai](), [REST API](), [WebSocket](), [OpenAI]() Tags: [ai-agents](), [apis](), [developer-insights](), [fastapi](), [ngrok](), [openai](), [python](), [tutorial](), [visual-studio-code](), [voice-ai](), [websocket]() ### AI overview This tutorial explains how to connect a Twilio voice agent to an external REST API using Python and FastAPI. It demonstrates using LLM tool calling to fetch live data and take actions on a caller's behalf. ### Source excerpt Learn how to connect a Twilio voice agent to an external API using Python, so it can fetch real-time data and take action on a caller's behalf. ## Building EasyReply: How We Used Laravel to Unify Customer Support DevFeed: [Building EasyReply: How We Used Laravel to Unify Customer Support]() Original publisher: [Read original article]() Author: Emma Blake Published: 2026-09-11T16:06:51Z Content type: article Language: en Sources: [Laravel]() Topics: [Laravel](), [Support](), [Artificial Intelligence](), [React](), [WebSocket](), [PHP](), [Single-page application (SPA)](), [email](), [Front end](), [Instagram]() Tags: [ai](), [api](), [development](), [email](), [frontend](), [instagram](), [laravel](), [queue](), [react](), [sponsor](), [support](), [ui](), [websocket]() ### AI overview This article explains how EasyReply uses Laravel to combine email, Slack, Instagram, and WhatsApp conversations in an AI-powered shared inbox. It describes Laravel Reverb for real-time updates, Inertia and React for the frontend, and queues for background processing. ### Source excerpt EasyReply pulls email, Slack, Instagram, and WhatsApp into one AI shared inbox, built on Laravel with Reverb, Inertia, React, and queues. The post Building EasyReply: How We Used Laravel to Unify Customer Support appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## Build Voice AI Experiences with Twilio and GPT-Live-1 in the OpenAI API DevFeed: [Build Voice AI Experiences with Twilio and GPT-Live-1 in the OpenAI API]() Original publisher: [Read original article]() Author: Lenore Files Published: 2026-09-10T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [voice ai](), [real-time](), [API](), [SDKs](), [OpenAI](), [Node.js](), [Python]() Tags: [ai](), [api](), [developer-insights](), [openai](), [real-time](), [tutorials](), [voice](), [voice-ai](), [websocket]() ### AI overview This tutorial article explains how to build real-time voice AI applications by connecting Twilio Agent Connect with OpenAI's GPT-Live-1 through the OpenAI API. It provides tutorials, sample applications, SDK support, and documentation for voice assistants and outbound voice agents using Node.js and Python. ### Source excerpt Build real-time voice AI Agents with Twilio and GPT-Live-1 in the OpenAI API with these tutorials, sample apps, and more. ## 🔌 Stripe's Proxy Was Opening Hundreds Of Thousands Of Connections DevFeed: [🔌 Stripe's Proxy Was Opening Hundreds Of Thousands Of Connections]() Original publisher: [Read original article]() Author: Byte-Sized Design Published: 2026-09-08T15:36:04Z Content type: article Language: en Sources: [Byte-Sized Design]() Topics: [stripe](), [Go Language](), [Latency](), [servers](), [WebSocket]() Tags: [go](), [latency](), [proxy](), [servers](), [stripe](), [websocket]() ### AI overview The article explains why Stripe replaced Envoy with its own Go proxy, mesh-proxy. It attributes the change to connection scaling problems and reports lower CPU usage and latency, fewer connections, and additional burst capacity from Ruby load balancing. ### Source excerpt A Go proxy, one connection per host, and 3,000 days of latency saved every day ## Integrate Deepgram Flux with Twilio's Conversation Relay DevFeed: [Integrate Deepgram Flux with Twilio's Conversation Relay]() Original publisher: [Read original article]() Author: Dhruv Patel Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [flux](), [asr](), [Tutorial](), [Latency](), [Node.js](), [WebSocket](), [Streaming]() Tags: [developer-insights](), [flux](), [latency](), [node](), [speech](), [streaming](), [transcription](), [tutorial](), [websocket]() ### AI overview This tutorial shows how to integrate Deepgram Flux with Twilio's Conversation Relay in Node.js. Flux combines speech transcription and turn detection, with configurable end-of-turn confidence, and is described as reducing response latency and false interruptions. ### Source excerpt Integrate Deepgram Flux with Twilio ConversationRelay in Node.js for faster turn detectio, and tunable end-of-turn control. ## Compose & kotlinx.html DevFeed: [Compose & kotlinx.html]() Original publisher: [Read original article]() Published: 2026-08-26T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Compose](), [HTML](), [WebSocket](), [Document Object Model (DOM)](), [ui](), [client]() Tags: [backend](), [compose](), [html](), [sse](), [ui](), [web](), [websocket]() ### AI overview The article presents an approach for keeping server-rendered HTML admin pages fresh without abandoning static HTML. It uses Molecule on the JVM to observe state, kotlinx.html to render HTML fragments, Ktor to stream updates over WebSockets, and client-side JavaScript with Idiomorph to patch the DOM. It also discusses using server-sent events for unidirectional updates and the scalability tradeoffs of long-lived connections. ### Source excerpt Let's render a simple page with Ktor server and kotlinx.html: get("/users.html") { call.respondHtml { myLayout(title = "Users") { userList( users = db.users.value, ) } } } A reusable myLayout provides scaffolding, userList encapsulates the specific page content, and db.users is a StateFlow> from the persistence layer. I've been doing this over and over to create admin dashboard pages for a project. It works great right up until you leave it open for a minute or two, and its content becomes stale. Client-side frameworks exist within the ecosystem to "solve" this, such as Compose for HTML or Compose UI for Web. If your house has a leaky pipe you can also "solve" that by moving to a new house. I simply will not bring myself to abandoning HTML let alone delivery of static HTML in the response. Efforts are underway to adapt Compose for HTML for so-called isomorphic rendering. This would involve performing the initial composition on the server to produce the static HTML for the HTTP response. Then, client side as JS, mounting the same rendering code to reproduce the DOM tree and incrementally update it for future state changes. Tomorrow's Compose today Instead of waiting, I brought my own Compose on the JVM from home in the form of Molecule. Instead of managing a UI tree over time, Molecule manages a single piece of state over time. We can use that to render an HTML fragment on the server as a string, and then stream that to the client. webSocket("/users.ws") { launchMolecule(Immediate) { val users by db.users.collectAsState() createHTML().userList( users = users, ) }.collect(::send) } That's it. Ktor gives us the webSocket, Molecule runs the StateFlow which is piped into it, and kotlinx.html renders the HTML fragment of our existing content function. In the initial HTML payload you need to wire this up somehow. Something like: script { unsafe { +""" |const content = document.getElementById("content"); |const socket = new WebSocket("ws://" + location.ho ## 🍔🧠 Why Linear Feels So Fast (Technical Breakdown) DevFeed: [🍔🧠 Why Linear Feels So Fast (Technical Breakdown)]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-07-20T15:30:40Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [Caching](), [Local-First](), [client](), [WebSocket](), [Software Engineering](), [Vite](), [npm]() Tags: [cache](), [caching](), [javascript](), [linear](), [local-first](), [npm](), [technical](), [vite](), [websocket]() ### AI overview A technical breakdown of how Linear aims to feel fast by minimizing network latency. It describes local-first state updates, asynchronous synchronization over WebSocket, code splitting, parallel module loading, service-worker precaching, and separately cached dependency chunks. ### Source excerpt PLUS: Virtual memory explained 👨💻, Spark retires vector DBs 💾, Backprop explained simply 🧮 ## Starlette vs FastAPI: what FastAPI actually adds DevFeed: [Starlette vs FastAPI: what FastAPI actually adds]() Original publisher: [Read original article]() Author: Farhan Hasin Chowdhury Published: 2026-07-20T07:00:00Z Content type: comparison Language: en Sources: [Honeybadger]() Topics: [FastAPI](), [Pydantic](), [ASGI](), [OpenAPI Specification](), [Dependency injection](), [Python](), [WebSocket](), [Cross-origin resource sharing (CORS)]() Tags: [cors](), [data-validation](), [dependency-injection](), [fastapi](), [frameworks](), [openapi](), [python](), [python-articles](), [starlette](), [websocket]() ### AI overview This comparison explains how FastAPI builds on Starlette and Pydantic. Starlette provides the ASGI-based HTTP layer, while Pydantic handles typed data validation; FastAPI adds type-driven parameter parsing, dependency injection, and automatic OpenAPI documentation. It also discusses when using raw Starlette may be preferable. ### Source excerpt FastAPI is built on Starlette, but most developers never look at what's underneath. Learn what FastAPI actually adds on top of Starlette and Pydantic, what comes straight from Starlette, and when dropping down to raw Starlette makes more sense than pulling in the full stack. ## How Discord Fans Out One Message to a Million Users DevFeed: [How Discord Fans Out One Message to a Million Users]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-07-07T13:22:26Z Content type: article Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [Discord](), [Publish-subscribe pattern](), [real-time](), [WebSocket](), [Back end](), [Processes](), [Authorization]() Tags: [backend](), [case-study](), [channel](), [discord](), [engineering](), [permission](), [real-time](), [scale](), [server](), [websocket]() ### AI overview This case study explains how Discord fans out a single message to many online users. It describes a real-time backend built around pub/sub, guild routing processes, permission checks, session processes, and WebSocket delivery. ### Source excerpt A case study in fanout, bottlenecks, and the engineering decisions behind Discord's scale. ## Choose your fighter: benchmarking 5 WebSocket servers for Node.js DevFeed: [Choose your fighter: benchmarking 5 WebSocket servers for Node.js]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-06-24T00:00:00Z Content type: comparison Language: en Sources: [Evil Martians]() Topics: [WebSocket](), [Node.js](), [benchmarking](), [Socket.IO](), [real-time](), [Latency]() Tags: [benchmark](), [benchmarking](), [frontend-real-time](), [latency](), [network](), [node](), [node-js](), [open-source](), [performance](), [performance-scale](), [real-time](), [websocket]() ### AI overview Evil Martians compare five WebSocket server options for Node.js: Socket.io, Socket.io with Connection State Recovery, uWebSockets.js, AnyCable OSS, and AnyCable Pro. The benchmark finds similar raw latency at 10,000 subscribers, while resilience under network drops, reconnect storms, and broadcast load separates the systems. AnyCable delivered all messages during simulated drops and led broadcast throughput; the other systems showed different recovery, connection-capacity, or message-loss trade-offs. ### Source excerpt Evil Martians benchmarked five WebSocket servers for Node.js: Socket.io, uWebSockets.js, and AnyCable (OSS and Pro). How we caught our own load generator lying, and how to make WebSocket benchmark numbers honest. ## WebSockets, gRPC, And GraphQL In The Core DevFeed: [WebSockets, gRPC, And GraphQL In The Core]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-07T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [WebSocket](), [GraphQL](), [gRPC](), [real-time](), [API](), [Code generation]() Tags: [api](), [graphql](), [pipeline](), [real-time](), [tutorial](), [websocket]() ### AI overview A hands-on tutorial covering WebSockets, typed GraphQL clients, and typed gRPC clients in the core framework. It explains how to build a real-time chat, generate typed clients from GraphQL schemas and proto files, and use WebSocket subscriptions. ### Source excerpt A hands-on walk through the three connectivity features that landed together this week, building a live chat over the new core WebSocket API and typed clients from a GraphQL schema and a proto file. ## Sandboxed AI bots: give capabilities, not credentials DevFeed: [Sandboxed AI bots: give capabilities, not credentials]() Original publisher: [Read original article]() Author: Alex Petric Published: 2026-04-23T00:00:00Z Content type: tutorial Language: en Sources: [Windmill Blog]() Topics: [Security](), [Discord](), [Discord bot](), [stripe](), [implementation](), [WebSocket](), [HashiCorp Vault]() Tags: [agent](), [ai](), [ai-bots](), [ai-discord-websocket-triggers](), [api-keys](), [credentials](), [discord](), [secret-storage](), [secrets](), [security](), [ssh](), [stripe](), [websocket](), [websocket-triggers]() ### AI overview This tutorial shows how to build a Discord bot that answers billing questions through Stripe while keeping API keys hidden from an AI agent. Windmill tools retrieve credentials at runtime from encrypted resource storage, and the agent receives only tool capabilities. The sandbox also provides process, filesystem, CPU, memory, and optional network isolation. ### Source excerpt How do I build an AI Discord bot that accesses Stripe without leaking API keys? Use Windmill sandboxed tools to give the AI capabilities, not credentials. ## CLI 2.4.0: iOS 26 and more devices on Maestro Cloud DevFeed: [CLI 2.4.0: iOS 26 and more devices on Maestro Cloud]() Original publisher: [Read original article]() Author: Proksh Luthra Published: 2026-04-03T06:43:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Command-line interface](), [iOS](), [Android](), [Cloud](), [iphone](), [WebSocket]() Tags: [android](), [api](), [apple](), [cli](), [ios-26](), [linux](), [macos](), [tests](), [update](), [websocket]() ### AI overview Maestro CLI 2.4.0 adds iOS 26 support locally and on Maestro Cloud, expands the available Apple device catalog, and introduces commands that return device values for CLI flags. It also updates device OS formatting, adds web test improvements, and includes fixes and performance improvements. ### Source excerpt You can now test across a much wider range of Apple devices and on iOS 26. ## A look back at 2025 demo development at ClickHouse DevFeed: [A look back at 2025 demo development at ClickHouse]() Original publisher: [Read original article]() Author: Lionel Palacin Published: 2025-12-30T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Demo](), [Development](), [real-time](), [benchmarking](), [dashboards](), [WebSocket](), [data](), [Go Language]() Tags: [2025](), [analytics](), [apis](), [applications](), [benchmarking](), [benchmarks](), [clickhouse](), [data](), [demo](), [development](), [engineering](), [examples](), [go](), [real-time](), [speed](), [ui](), [websocket]() ### AI overview The article reviews notable ClickHouse demos developed in 2025, emphasizing how hands-on applications make database performance tangible. It describes StockHouse, a real-time market analytics application that streams stock and crypto data through WebSocket APIs, ingests it into ClickHouse, and updates a dashboard within milliseconds. ### Source excerpt Have a look at some of the most notable demos we built this year, and how they help people feel the speed of ClickHouse through real, hands-on examples. ## A refreshing take: using serverside rendering to reduce fragile DOM state DevFeed: [A refreshing take: using serverside rendering to reduce fragile DOM state]() Original publisher: [Read original article]() Author: Simon Fish Published: 2025-10-17T08:33:59Z Content type: article Language: en Sources: [FreeAgent]() Topics: [Hotwire](), [Front end](), [Rails](), [Stimulus](), [WebSocket](), [Document Object Model (DOM)](), [tbox]() Tags: [browser](), [development](), [frontend](), [hotwire](), [html-elements](), [js](), [rails](), [ruby-on-rails](), [stimulus](), [streams](), [websocket]() ### AI overview This article examines FreeAgent's use of server-side rendering with Hotwire, Turbo, Stimulus, and Rails to reduce fragile DOM state. It explains how Turbo Streams and Action Cable can update browser pages asynchronously, contrasting these behaviors with the original DOM-manipulation actions. ### Source excerpt Hotwire is central to how we drive the frontend at FreeAgent, and Action Cable allows us to send Turbo Streams as users browse the site, adding a layer of richness to the user experience. ## Announcing Apollo iOS 2.0 DevFeed: [Announcing Apollo iOS 2.0]() Original publisher: [Read original article]() Author: Anthony Miller Published: 2025-10-07T07:00:46Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Swift](), [GraphQL](), [iOS](), [Concurrency](), [WebSocket]() Tags: [announcement](), [apple](), [concurrency](), [graphql](), [release](), [structured-concurrency](), [swift](), [websocket]() ### AI overview Apollo iOS 2.0 is a release of Apollo's Swift client rebuilt around Swift's modern concurrency model. It introduces concurrency-aware APIs, streamlined layers, and updated platform and distribution requirements, including the retirement of CocoaPods support. GraphQL subscriptions currently support HTTP only; WebSocket support is planned for a future minor release. ### Source excerpt Apollo iOS 2.0 is here, and it's the biggest reimagining of our Swift client yet. Built from the ground up for Swift's modern concurrency model, this release delivers snappier performance, stronger type guarantees, and a cleaner developer experience for teams shipping GraphQL-powered apps across Apple platforms. Improved APIs Swift's structured concurrency and the / syntax weren't just sugar, they introduced an entirely new mental model for reasoning about work, isolation, and cancellation. ## What's New in Apache Pulsar 4.1 DevFeed: [What's New in Apache Pulsar 4.1]() Original publisher: [Read original article]() Author: David Kjerrumgaard Published: 2025-09-09T00:00:00Z Content type: release Language: en Sources: [Apache Pulsar Blog]() Topics: [Apache Pulsar](), [SDKs](), [Security](), [Grafana Cloud Metrics](), [Resilience](), [WebSocket]() Tags: [announce](), [apache](), [api](), [authentication](), [bug-fixes](), [cli](), [configuration](), [encryption](), [java](), [launch](), [monitoring](), [new-features](), [observability](), [performance](), [release](), [resilience](), [schema](), [sdk](), [security](), [websocket]() ### AI overview Apache Pulsar 4.1 is a feature release with 19 approved Pulsar Improvement Proposals, bug fixes, security updates, and performance improvements. Highlights include stronger WebSocket token security, enhanced encryption handling, client configuration and resilience improvements, third-party schema registry support, Java 17 as the minimum for the Java client SDK, improved storage management, monitoring, and topic policies. ### Source excerpt The Apache Pulsar community is thrilled to announce the launch of Apache Pulsar 4.1, a significant feature release! ## SignalR Scalability: Scaling Real-Time SignalR Applications on Heroku DevFeed: [SignalR Scalability: Scaling Real-Time SignalR Applications on Heroku]() Original publisher: [Read original article]() Author: Andrew Fawcett Published: 2025-05-21T16:26:16Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [SignalR](), [Scalability](), [Heroku](), [Redis](), [.NET](), [WebSocket]() Tags: [developer-tools](), [engineering](), [guide](), [heroku](), [net](), [performance-optimization](), [redis](), [scalability](), [signalr](), [sticky-sessions](), [websocket]() ### AI overview A Heroku tutorial explains how to scale a real-time .NET SignalR application across multiple servers or dynos. It covers using a Redis backplane and sticky sessions to maintain stable WebSocket connections. ### Source excerpt SignalR makes it easy to add real-time functionality to .NET web applications--things like live chat, instant notifications, or interactive dashboards. But what happens when your app starts to grow? A single server can only take you so far. At some point, you'll need to take advantage of SignalR scaling features to scale out your app. [...] The post SignalR Scalability: Scaling Real-Time SignalR Applications on Heroku appeared first on Heroku. ## FastRTC: The Real-Time Communication Library for Python DevFeed: [FastRTC: The Real-Time Communication Library for Python]() Original publisher: [Read original article]() Author: Freddy Boulton; Abubakar Abid Published: 2025-02-25T00:00:00Z Content type: tutorial Language: en Sources: [Hugging Face - Blog]() Topics: [FastAPI](), [Python](), [real-time](), [AI Development](), [WebRTC](), [WebSocket](), [gradio](), [Large Language Model]() Tags: [apis](), [artificial-intelligence](), [audio](), [gradio](), [llm](), [python](), [real-time](), [speech](), [text-to-speech](), [video](), [voice](), [webrtc](), [websocket]() ### AI overview FastRTC is introduced as a Python library for building real-time audio and video AI applications. The article demonstrates core features including voice detection and turn taking, a WebRTC-enabled Gradio interface, phone access, WebRTC and WebSocket support, FastAPI integration, and speech-to-text and text-to-speech utilities. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## psql from the browser DevFeed: [psql from the browser]() Original publisher: [Read original article]() Author: Eduard Dyckman Published: 2024-12-11T18:48:43Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [Databases](), [Command-line interface](), [SQL](), [WebSocket](), [browser](), [C](), [JavaScript](), [Serverless](), [Back end](), [Template](), [Workers]() Tags: [browser](), [c](), [cloudflare](), [cloudflare-workers](), [command-line](), [database](), [databases](), [javascript](), [postgres](), [server](), [serverless](), [sql](), [websocket](), [workers]() ### AI overview Neon describes psql.sh, a browser-based implementation of the Postgres command-line client. It uses a WebSocket proxy and serverless driver to connect browser and JavaScript environments to isolated, instantly created database branches based on templates. ### Source excerpt If you've ever worked with Postgres, you've probably launched psql at least once. It's the default database client packaged with the Postgres server. This is a command-line application, written in C, and it's packed with many features such as autocompletion, command history, and... ## How a Live Multiplayer Snakes Demo Tested Temporal Workflow Resilience DevFeed: [How a Live Multiplayer Snakes Demo Tested Temporal Workflow Resilience]() Original publisher: [Read original article]() Author: Rob Holland Published: 2024-12-05T08:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Resilience](), [distributed-systems](), [real-time](), [Svelte](), [WebSocket](), [Cloud]() Tags: [chaos](), [cloud](), [distributed-systems](), [how-to](), [live](), [multiplayer](), [real-time](), [resilience](), [svelte](), [websocket]() ### AI overview This blog post explains how Temporal powered a live multiplayer Snakes game with independent workflows for the game, rounds, and snakes. The demo introduced Worker restarts to test recovery from induced outages while the game continued running. ### Source excerpt We used a live, multiplayer snake game powered by Temporal workflows to showcase the power of Durable Execution. Learn all about it in this blog post. ## Supabase Edge Functions: Introducing Background Tasks, Ephemeral Storage, and WebSockets DevFeed: [Supabase Edge Functions: Introducing Background Tasks, Ephemeral Storage, and WebSockets]() Original publisher: [Read original article]() Author: Lakshan Perera; Nyannyacha Published: 2024-12-03T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [WebSocket](), [Back end](), [Filesystems](), [Streaming](), [Zip](), [OpenAI](), [SDKs]() Tags: [announce](), [api](), [features](), [openai](), [storage](), [streaming](), [websocket](), [zip]() ### AI overview Supabase announces Background Tasks, Ephemeral File Storage, and WebSockets for Edge Functions. The article explains how these features support long-running workloads, temporary-file processing, zip extraction, streaming uploads, and authenticated relays to the OpenAI Realtime API. ### Source excerpt Edge functions can be used for workloads outside the request-response lifecycle [Next page]()