This page is only for the streamer’s Nostr key.
Settings
Loading credits...
My Stream. My Domain. My Power.
Stream Days are added to your balance after payment is confirmed.
Stream Days run from 00:00 to 24:00 UTC. Activating streaming unlocks the current day only.
A Stream Day is only used when you activate streaming day for that day — it never decreases automatically.
Managed on simulcast.me.
Go there
Choose which Zap Stream-style backend to use for metadata + live note.
—Ignore this box when using simulcast.
Mirror your live stream to Twitch, YouTube, Facebook Gaming, Kick, Trovo, or a custom RTMP target
Forwarding is handled on Zap Stream’s servers and depends on their current backend status.
managed on simulcast.me.
Go there.
When using Simulcast you must use this feature.
/live/ and wait for your stream to appear.Add your live stream information.
Publish a "I'm live" Nostr note.
Paste this into your announcement if you want a Nostr preview card.
Manually email verified subscribers after your player is live. LFL never sends this automatically when OBS connects or reconnects.
Zap Stream backends. See your dot balance, RTMP URLs, keys, tiers, and raw endpoint JSON.
Ignore this box when using simulcast
Instructions:
Go to Tab1. Under the section "Stream Backend" select a backend using the radio button.
Then come back here and accept the terms. Do this for each backend. If you don't accept the terms
the backend will block you from streaming.
You only have to do this once.
Terms: zap.stream/tos
Terms are managed on simulcast.me.
Drop these in OBS as browser sources.
Combined chat view + send box. Type to viewers or monitor your chat from your phone while streaming.
Choose where LFL stores uploaded media. Local is safe for small files. Backblaze B2 is recommended for large 4K videos and keeps big uploads off your LFL server.
Your permanent bucket-restricted media key cannot change bucket CORS. If the test reports missing
writeBuckets, create a temporary Backblaze app key with access to All buckets
and Read and Write, paste it here, and run the test again. LFL uses it only for this request,
does not save it, and you should delete the temporary key in Backblaze afterward.
Add this address in Amethyst as a media/Blossom server. Amethyst will upload images and videos to this LFL instance and insert the protected LFL viewer URL into your note. Only the configured instance owner can upload.
No extra cron job is required. In Amethyst, leave mirror uploads to all Blossom servers disabled for this LFL server.
This instance sends its own email. Credentials and subscriber addresses stay
in the protected /live/data/ area and are never sent to LFL Core.
Configure SPF, DKIM, and DMARC with your email provider for reliable delivery.
Owners see masked addresses only in the LFL interface. Viewers see their own full address. Campaign reports count messages accepted by SMTP, failed, or skipped; LFL does not track opens or clicks.
—
—
kind:0Name, avatar, bio, website, and NIP-05 come from the newest signed profile in this LFL database. Saving writes locally first; Cron5 synchronizes the same signed profile to every configured relay group.
Existing profile fields that LFL does not edit—including the Nostr Lightning address—are preserved in the replacement event.
Keep signed copies of your personal LFL Nostr archive on mutual, verified LFL friends. Backups are stored in an isolated database and never appear in the host's feeds. Both instances must opt in and remain activated.
LFL uses a dedicated server transport key, not your Nostr private key. Every batch and storage receipt is signed.
Every valid owner-authored event and every valid event carrying the owner's p tag is eligible. Unrelated cached Watchlist events, media files,
SMTP data, configuration, login sessions, and secrets are excluded. Restore controls and NWC payments will be
added later without changing the stored event format or receipt ledger.
You may use the same relay in several groups, but the groups do different jobs.
The installer copies one starter list into all five; you can specialize the lists here afterward.
Enter one wss:// relay per line.
Important: wss://relay.letsfo.com is required and is restored
automatically when these settings are saved. A specialized group does not normally inherit
changes made to another group.
LFL checks actual relay behavior. Advertised payment information is shown only as a hint; successful reads and genuine LFL publication results are authoritative.
Write access is learned from real notes, videos, profiles, and deletion requests handled by LFL’s durable outbox. Until one has been sent to a relay, write access remains “Not tested.” No fake notes are published.
relays
General compatibility and fallback list. It is not a master list that automatically controls every LFL feature.
Shared or older Nostr features may use this list when they have no dedicated relay group.
The OBS chat viewer can fall back to it when commentRelays is unavailable, and
older livestream configurations can reach it after their dedicated fallbacks are empty.
commentRelays
Reads and publishes livestream chat activity in the sidebar and OBS chat widget.
These relays carry livestream comments, reactions, zap receipts, and chat profile lookups. Cron5 also sends the owner's locally saved Nostr profile here. The sidebar publishes comments and reactions here. A smaller trusted or paid list can reduce spam, but chat or zaps available only on other relays will not appear.
notesRelays
Publishes your notes and supplies the background database sync for My Notes and Notes Feed.
Cron5 publishes locally queued notes and their Nostr deletion requests here. Cron3 imports streamer activity; Cron4 rotates through this list to import followed-account activity and engagement into SQLite. My Notes and Notes Feed then load from the local database. If a note exists only on an unconfigured relay, LFL does not know it exists and does not automatically search that relay for the missing note.
liveStreamRelays
Supplies Cron2 with livestream events for the cached Nostr Live Network, stream status, and the owner's Past Streams history.
Cron2 rotates through these relays for recent kind:30311 events,
a bounded owner-history backfill, related profiles, and relevant deletion
requests, then stores the results in SQLite. This list controls what LFL
discovers; it does not control where a streaming provider publishes the original stream event.
videoRelays
Publishes video notes and synchronizes My Videos favourites and recording-list events.
My Videos initially loads its cards from local SQLite, uploads, and recordings, then performs
selected relay lookups in the background. Cron5 publishes locally queued video notes, video
deletion requests, and kind:30005 favourites or recording lists here. The Nostr Video Network obtains cards from verified LFL
instance APIs rather than scanning this list directly in the browser.
s1.letsfo.com is always forced.
LFL separates owner-authored and owner-tagged events from cached network events in the report without moving or copying the SQLite database.
To be listed on the LFL Networks, your domain must publish
/.well-known/lfl.txt once to prove the domain and streamer pubkey.
Country is synced separately and can be changed later without editing the file.
Installs are fast on purpose (recent events only). Use this to sync your older nostr history into your local DB.
This copies your existing events from your local database to other relays. It does not “edit” your notes.
Idle.
If Auto-Activate is enabled in Tab 1, this cron automatically activates the current Stream Day shortly after midnight UTC each day. If Auto-Activate is disabled, the streamer must activate each new Stream Day manually.
—
This cron synchronizes recent kind:30311 livestream events from the configured livestream relays. It keeps the Nostr Live Network, current LIVE or ENDED stream status, previous-stream information, and streamer profile data up to date. If it stops, the Live Network and live page may show outdated information.
—
This cron imports recent Nostr activity authored by or involving the streamer, including notes, replies, quotes, reposts, reactions, zaps, Guest Notes, profile updates, contact lists, and long-form articles. It keeps /live/notepad/my-notes/ current and fast. If it stops, My Notes and related streamer activity may become outdated.
—
This cron alternates between synchronizing recent activity involving the streamer and recent activity from accounts the streamer follows. Its bounded people phases also refresh the Watchlist, discover and confirm the Audience, and cache the verified Nostrich Network. It keeps /live/notepad/notes-feed/, the Nostr Notes Network, and related activity views current. It also purges expired Notes Feed cache rows and performs scheduled SQLite maintenance. If it stops, Notes Feed, the Notes Network, and people pages may become outdated, expired cache rows will not be purged, and database maintenance will not run.
—
This cron publishes locally queued notes, profiles, deletions, and favourites first, then advances any active setup mirror job. If it stops, events remain safe in the local database and outbox but will not synchronize to every configured relay until the worker resumes.
—
/live/ page and wait for the stream to appear.
Refresh the page if necessary./live/ page and wait for the stream to appear.
Once it’s live, return to the Admin Panel.
Support: Forum
The Upgrade Assistant replaces program files while preserving
/live/data/, your instance configuration, uploads, keys, and
assigned card/profile images. Ordinary releases do not copy or modify the
SQLite database.
Loading preflight…