selkies-project/selkies

Selkies

Open-Source Low-Latency Accelerated Linux WebRTC HTML5 Remote Desktop Streaming Platform for Self-Hosting, Containers, Kubernetes, or Cloud/HPC

Turbulent networking with WebRTC

Game networking is hard. I want to do Quake3-like networking, which runs on UDP, but on browser which does not support UDP. Bummer. Fortunately, there are some clever folks experimenting with using…

WebRTC: Making a peer-to-peer game using JavaScript

I recently had the chance to work on a prototype for a video chat service. It was an excellent opportunity to become more closely…

simple streaming setup

for the uninitiated (like me)

Selfhosted Infrastructure Any%

A Co-op Cloud speedrun attempt livestream! Brought to you by by libre software.

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.

Datastar: Modern web dev, simplified

You love building web apps with Python, and HTMX got you excited about the hypermedia approach -- let the server drive the HTML, skip the JavaScript build step, keep things simple. But then you hit that last 10%: You need Alpine.js for interactivity, your state gets out of sync, and suddenly you're juggling two unrelated libraries that weren't designed to work together. What if there was a single 11-kilobyte framework that gave you everything HTMX and Alpine do, and more, with real-time updates, multiplayer collaboration out of the box, and performance so fast you're actually bottlenecked by the monitor's refresh rate? That's Datastar. On this episode, I sit down with its creator Delaney Gillilan, core maintainer Ben Croker, and Datastar convert Chris May to explore how this backend-driven, server-sent-events-first framework is changing the way full-stack developers think about the modern web.

sneakerweb

A parallel web updated through physical media.

disnet/semble-it

A fast, local-first client for Semble.

leaningtech/webvm

Virtual Machine for the Web

Join the Selkies OSS Discord Server!

Check out the Selkies OSS community on Discord - hang out with 450 other members and enjoy free voice and text chat.

supersonic-app/supersonic

A lightweight and full-featured cross-platform desktop client for self-hosted music servers

PlanetScale - the world’s fastest and most scalable cloud hosting for Vitess, Neki, and Postgres

PlanetScale offers the world’s fastest and most scalable cloud hosting for Vitess, Neki, and Postgres.

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.