bigmoves/goose

chadtmiller.com/goose

A Gleam WebSocket consumer for AT Protocol Jetstream events.

isaaccorbrey.com/gleam_atproto

A Gleam module for interacting with the AT Protocol.

Browsertech Digest

An email digest about modern browser technology and the things people build with it. We’re talking WebAssembly, WebRTC, WebGL, WebGPU, WebSockets, WebCodecs, WebTransport, Web-everything. Written by Paul Butler of Jamsocket. We also host Browsertech events in NYC and SF. Talk browsertech in real time on #browsertech in the Jamsocket Discord.

Filling the remaining gap between WebSocket, WebRTC and WebTranspor

Existing web platform facilities for network communication include WebSocket and WebRTC. Each mandates a specific protocol, ensures TLS, and respects the Same Origin Policy. The proposed WebTransport is similar in these respects.

A field day for Gleam’s language server | Gleam programming language

News post: Gleam v1.18.0 released!

Into the feed of Currents, an open Pinterest alternative built on AT Protocol - Matteo Marjanovic

In this article I describe how I built the first version of Currents' feed, an open Pinterest alternative on AT Protocol, and how its personalization slider works.

Bluesky Firehose

Real-time Jetstream analytics for sentiment, hashtags, and network health.

About — AT Proto Collection Tracker

A bottom-up tool for discovering activity across the AT Protocol network by watching live record types on the Jetstream firehose.

ATOM: AT Protocol Over MoQ Transport

This document specifies how the Authenticated Transfer (AT) Protocol can leverage Media over QUIC Transport (MOQT) for efficient data synchronization across decentralized social networks. The AT Protocol's firehose event stream and repository synchronization mechanisms map naturally to MOQT's publish/subscribe model, enabling scalable relay infrastructure, priority-based delivery, and improved resilience for large-scale social data distribution. This specification addresses the challenges of the current WebSocket- based transport and demonstrates how MOQT's relay architecture, group-based caching, and multiplexed streams provide significant benefits for AT Protocol deployments at scale.

burrito.space/bzzrt

Cloudflare worker to watch RSS feeds and post updates to Discord webhooks

RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win | TechCrunch

Editor's note: With all of the debate lately between RSSCloud versus PubSubHubbub, we wanted to hear from a developer who could actually tell us which one might be better and why. The following guest post is written by Josh Fraser, the co-founder of EventVue, who is an active contributor to PubSubHubbub in his free time. He has contributed several client libraries for PubSubHubbub including a WordPress plugin. Guess which side of the debate he falls on. In the past few months, a lot of attention has been given to the rise of the real-time web. The problem is that the web wasn't designed with real-time in mind. There is a huge need for the tech community to get behind new protocols that will power this fundamental shift in how web applications work. Today I want to take a look at two of the leading protocols that enable real-time notifications on the web. While there are older protocols that enable real-time notifications like XEP-0060, PubSubHubbub (PuSH) and rssCloud are two new protocols which show a lot of promise of gaining adoption. Both PuSH and rssCloud address a fundamental flaw in the way web applications work today. Currently, getting updates on the web requires constant polling. Subscribers are forced to act like nagging children asking, "Are we there yet?" Subscribers must constantly ping the publisher to ask if there are new updates even if the answer is "no" 99% of the time. This is terribly inefficient, wastes resources, and makes it incredibly hard to find new content in as soon as it appears. Both protocols flip the current model on its head so that updates are event driven rather than request driven. By that I mean that both protocols eliminate the need for polling by essentially telling subscribers, "Don't ask us if there's anything new. We'll tell you." But if you find yourself confused about how they are different, you're not alone.