Open standards
The four drafts #
- irl-commons
- Shared facts
- Words, quick checks, a list of apps and services, guides and standards, written in plain language. Anyone can reuse them with credit. The glossary, links and guides on this site come from here.
- Published, v0 · github.com/irl-commons
- stream-status
- What's wrong, and are you still live?
- Each part reports its problems in the same short shape: what is wrong, where, how much it matters to viewers, and whether the stream still reaches the receiver. A part that can't see something says "unknown", never "fine".
- Published draft, v0 · No app uses it yet · github.com/irl-commons/stream-status
- stream-session
- Which show, who's in it, who decides?
- The devices in one show agree on which device is in charge. So a stream can move from your PC to your phone to your backpack, and a friend or a guest can join. Each person chooses what the others see. Anyone allowed can hide the picture at once.
- Published draft, v0 · No app uses it yet · github.com/irl-commons/stream-session
- stream-components
- Who's around, who trusts whom, what goes where?
- How your phone, backpack, OBS and other apps would find each other, pair once with a QR code, and show where each picture and sound goes. It is meant to work on one Wi-Fi or hotspot, and across the internet through an optional server.
- Designed, not published yet
Comments wanted #
These are drafts, so now is the easiest time to change them. Comments from makers and integrators help most.
Do you make a streaming app, an encoder box, a relay or receiver, a hub, a scene switcher, a remote app or a help page? Then one question matters most: what would stop you from using one of these?
- Something your product needs to say that a draft can't say.
- A rule that doesn't fit how your product works.
- Too much work for what you would get back.
Short answers help. One line on why you wouldn't use it is as useful as a long review. Doubts about the whole idea are welcome too.
Where to write
- On GitHub: each repository has a "Feedback from makers and integrators" discussion: irl-commons, stream-status, stream-session.
- By email: hello@irlcommons.org, if you'd rather not post in public.
- On Discord: the project's Discord server.
Try one first
- Use the irl-commons data in your app or site.
- Send your first stream-status snapshot.
- Join a stream-session show.
Built on earlier work #
The drafts borrow on purpose, and their specs name where each idea comes from.
- NOALBS
- The open-source scene switcher many IRL streamers run. It reads the stats of the common receivers, and it is the closest thing to a shared status format in IRL streaming today. stream-status and stream-session are meant to sit next to it.
- IRLToolkit
- Its ingest sharing for cloud OBS, where both sides agree and access runs out by itself by default, shaped how stream-session lets guests in.
- OBS Studio
- Its broadcast performance metrics, carried inside the video, are the model for stream-status's in-band form.
- Broadcast and monitoring
- AMWA NMOS, Prometheus Alertmanager, the IETF alarm model, Kubernetes conditions, Nagios, OpenTelemetry and CloudEvents.
- Coordination and sharing
- Raft, Chubby, etcd and NATS leases, fencing tokens, DNS-SD, OAuth scopes, Biscuit and macaroons, LiveKit, Matrix and W3C Trace Context.