A free, open-source, community project that helps self-hosted live
streamers get found the moment they go live – For livelier live streams.
—users bridged
—live right now
—chat auto-delete
Your browser confirmed these stats are true by reading Livelier's relays.
Here's exactly what's going on ↓
What Livelier.live is doing
Livelier makes self-hosted live streams available to a wider audience.
Your live stream is listed in a public directory that Livelier watches,
such as Owncast Directory.
When you go live, Livelier bridges your live stream to Nostr — a global
open network of apps and websites full of people who love independent live video.
When one of those people opens your stream's chat, Livelier joins your chat
and bridges the messages both ways — it joins under the name "Livelier".
If you saw "Livelier" appear in your chat, someone out there just tuned in
to watch your live stream, and Livelier bridged the chat so they could join.
See for yourself
What does Livelier know about your live stream?
Livelier republishes already-public directory information to its own Nostr
relays so that more people can find it. It only captures things you have published elsewhere.
Put your server URL in below and this page will fetch whatever Livelier holds,
live, off the relay.
Or
Discovery
Where your live stream shows up.
The moment you're live on a directory that Livelier watches, it bridges your live stream to any website or app that subscribes to the bridge,
carrying your title, your artwork, and a player URL pointing at
your own server.
Nothing is re-hosted and nothing is uploaded. Viewers connect to your
server to watch.
Your live stream gets more reach. Any website or app that subscribes to the bridge can discover your live stream, for example:
Zap.StreamShoshoPrimalAmethystNostrudel…and any app that supports Nostr NIP-53
Live on the bridge right now
And more...
Chat
Live chat messages are bridged both ways then deleted after.
When a viewer on Nostr opens your stream's chat, Livelier joins your
chat room under its own name to bridge your chat messages to them.
Chat is bridged both ways and is deleted after. Viewers' chat messages are
held only on the bridge, not published to any wider network, expire after three hours, and
are then hard-deleted by the relay.
Right now there are — chat messages on the
bridge. None should be older than
three hours.
Promises
Attempting a trustworthy design for streamers and viewers.
The Livelier bridge is designed to meet the needs of streamers and viewers in a
trustworthy way. Each commitment is enforced in the open source code, rather than
by policy.
Content should pass through unchanged.
Nothing is edited, filtered, or gated. Everything you publish about
your stream is passed along for viewers' apps to act on.
Overhead should be very light.
Livelier's load on your server is one playlist check a minute. A chat
connection opens only while someone is watching.
Bridged chat should not persist.
Chat lives on one dedicated relay, is marked do-not-share,
and is deleted on a timer. It should not be archived, syndicated, or searchable
afterwards.
The bridge should have its own identity.
Livelier joins your chat under its own name. Nothing it publishes
forces any brand on you or on your viewers.
Bridged accounts should be marked as mirrors.
Everything published is labelled as a bridge, and links back to your
server as the source to build your audience, not Livelier.
How it works
Live streams and chat are bridged to Nostr relays.
Nostr is a global social network protocol where “Notes and Other Stuff are
Transmitted by Relays”. One kind of Other Stuff is the live event —
NIP-53,
a way to announce live streams and open live chat rooms.
Livelier is a Nostr client that operates as a bridge. It finds live streams
on other public directories and publishes them to its own Nostr relays.
The Livelier bridge operates two relays, each with one job and a narrow
policy: one for live streams, and one for live chat.
Any Nostr client can query Livelier by subscribing to its relays, and receive
the live streams and live chat events that are on the bridge.
The code is open source. The bridge and both relays are open source code,
and each relay declares its own behaviour in its
NIP-11
document.
discovery
…
…
…
Only the bridge can write to it. The write whitelist contains one key.
Anyone can read it. This is where clients read your stream's event.
Your browser confirmed these policies by reading each relay's own NIP-11 document.
Verify it yourself
Every claim on this page can be verified.
You can query Livelier relays to verify each statement made on this page using
nak, the
Nostr command-line tool — brew install nak.
Prefer not to install anything? The same commands run in
Grimoire which is like Nak but runs in a
browser tab.
You can also read the Livelier bridge source code. Everything above is produced by the
code at github.com/r0d8lsh0p/livelier
— the discovery loop, what each event carries, and the relay policies these commands report.
Get involved
What do you think?
“I like it.” If you are already on the bridge there is nothing you need to do. Keep on as you have been, and Livelier should continue to find and bridge your live stream.
“I want to opt out.” You can opt out no questions asked. Please open an issue on GitHub naming your server. Your server will be opted out and no longer appear on the bridge.
“I want to contribute.” Livelier is new, but hopefully it can become a community project with more directories added as adapters (PeerTube, or anything else), and contributions are welcome.
We have built Livelier for self-hosted streamers because we think self-hosting is important, and because you shouldn't have to put up with reach that is second best.
We hope Livelier is an example of what open source technologies like Nostr can do for users of the open internet. We hope it's helpful to you, and inspires you to build or get involved in the open web.
