CraysShosho
Shosho is a live-streaming app that treats Nostr as the public room record: the video still travels through streaming servers, but the live event, chat, clips, product listings, identity and audience trail can move across the wider network.
Open Shosho with the right question and it becomes much easier to understand. The important question is not whether video can be stored on Nostr relays. It usually cannot, and Shosho does not pretend otherwise. The real question is what happens when the live room, the host identity, the chat, the replay pointer, the clip metadata and the product shelf are no longer trapped inside one platform account.
That is Shosho's lane. The official help center says the app is available on Android, iOS and the web, and that a creator's live sessions and chats can also appear in other Nostr software such as Primal, Amethyst, Nostrudel, Wisp and Zap Stream. The Google Play listing frames the app around phone-camera streaming, mentions, stream chat, zaps, replays, multiple npub logins, Amber sign-in and Zap Stream support. The Nostr profile says the same idea in plain language: your phone sends live video to a streaming server, while Nostr lets friends and followers discover the room and talk back.
For a creator, that means Shosho is less a single destination than a bridge between two worlds. The camera and microphone are ordinary live-video plumbing. The public room record is a Nostr event. The audience does not need to live inside one Shosho database to find the session. A viewer on another compatible client can discover the live, join the chat, react or follow the host. That is the product thesis, and it is a serious one because live video is where social networks usually become most controlling: discovery, monetization, moderation, replay access and account identity all sit under the platform's thumb.
The trade-off is equally serious. A live stream is a high-bandwidth, public, time-sensitive thing. If the server fails, the stream drops. If the HLS URL is broken, the signed event points nowhere useful. If a relay misses the event, part of the audience may not see the room. If the host loses the key or signs from the wrong account, the social trail fragments. Shosho is interesting because it makes those boundaries visible instead of hiding them behind the word "decentralized."
The room is not the video file
Nostr live streaming is built around a split. The video and audio travel to a streaming server. The room announcement travels to relays as a signed event. Shosho's own documentation explains the flow clearly: when a creator goes live, the server makes the video available at a playback URL, typically an HLS `.m3u8` address, and a Nostr live event advertises that URL together with the host profile, title, thumbnail and status.
The standard behind that is NIP-53. It defines kind 30311 as an addressable live streaming event with tags such as `d`, `title`, `summary`, `image`, `streaming`, `recording`, `starts`, `ends`, `status`, participant `p` tags, relay hints and pinned chat references. This is the small but powerful thing Shosho adds to the live-video stack: a signed, relay-discoverable record that says who is live, what the room is, where to watch it and how clients should attach chat.
The distinction matters. If you hear "Nostr live video" and imagine relays carrying the actual media bytes, you will misunderstand the security and reliability model. The relays carry discoverability and conversation. The streaming server carries the expensive video path. Shosho can therefore interoperate with the Nostr world without forcing every relay operator to become a video CDN. That is practical. It also means the server remains a real trust and availability dependency.
Shosho's developer docs add a useful warning: if you stream to a Nostr-aware streaming server, do not publish a duplicate kind 30311 manually, because the server publishes it for you. They also say the host `p` tag matters because Shosho uses it to associate the stream with the host profile. This is exactly the kind of detail that makes the app worth covering. The user-facing button is simple, but the product lives or dies by small protocol choices.
Mobile first, but not mobile only
Shosho's natural first use is phone streaming. Install the app, grant camera and microphone permissions, open the broadcast screen, press Start Stream, accept the terms when prompted and go live. The documentation says the app creates a guest profile automatically, so a person can start watching and chatting before building out a polished Nostr identity. Later, that profile can be personalized or replaced with an existing Nostr profile.
The mobile workflow is not a toy version of the product. The creator docs describe the live screen as a camera preview with a stream button, chat panel and other controls. Once live, video broadcasts to the selected streaming server, the Show is published as a Nostr live event, and chat messages from Shosho or the wider Nostr network appear in the panel. The same docs spend time on upload quality: High for strong 5G or Wi-Fi, Medium for most users, Low for weak cellular connections. That is a good sign. Real live streaming fails because of bandwidth long before it fails because of ideology.
Shosho also supports the more traditional streaming desk. If you use OBS or another RTMP-compatible encoder, you can create a Live Show on Shosho.live, copy an RTMP ingest URL and stream key, set OBS to Custom, then start streaming. Shosho's server handles the live event publication to Nostr. That makes Shosho useful for a creator who wants the familiar OBS workflow but wants Nostr discovery and chat rather than another closed destination.
The third path is Show Chat. If you already have a stream running on a self-hosted SRS, Owncast or Open Media Engine server, or a hosted service such as Cloudflare Stream, Livepeer or API.video, Shosho can take the HLS playback URL and handle the Nostr side. In that mode, Shosho is not trying to own the video path. It is giving an existing stream a Nostr room, chat and shareable identity layer.
The server question
Shosho is refreshingly direct about servers. Its help center says a phone or laptop alone cannot serve thousands of viewers; the streaming server receives video and audio and makes the stream watchable. Shosho works with two broad kinds. Nostr-aware streaming servers understand the Nostr live-event flow and can publish kind 30311 events on the creator's behalf. Generic RTMP servers do not know Nostr, but Shosho can publish the room event if it has the right playback details.
Shosho Server is the default path. The docs describe it as a Nostr-aware streaming server operated by Shosho. It publishes the live event, records the stream for replay and updates the event when a stream drops or ends. Replays from Shosho Server are kept for 90 days, while clips are stored separately. That is convenient, but it is also a dependency. If you care about long-term archive value, download the replay or make clips before the retention window closes.
Zap Stream is the second named path. Shosho's docs call Zap Stream a Nostr-aware streaming service and say the Zap Stream website shows Nostr lives, including streams sent to Shosho Server. Shosho can use Zap Stream Server through its API URL. That is important because it keeps the Shosho room from being a walled garden. A creator can use another Nostr streaming server and still remain in the same kind 30311 world.
Bring-your-own RTMP is the adult version of the story. Shosho needs an ingest URL, a stream key and an HLS playback URL. The first two are how the creator sends video to the server; the last one is what viewers actually play. If you run your own server, those values are operational secrets and public pointers at the same time. Protect the stream key. Make sure the HLS URL survives under load. Test the event from another Nostr client before announcing to an audience.
Chat, zaps, replays and clips
The moment a live room exists on Nostr, chat becomes more interesting than a sidebar. NIP-53 uses kind 1311 for live chat messages tied to an activity coordinate. Shosho's developer docs repeat the important rule: a chat message must include an `a` tag pointing to the live activity coordinate, and an `e` tag can mark a direct parent when replying. Reactions use kind 7, the familiar NIP-25 reaction event. The App Store history also notes threaded chat and room presence, which make busy rooms feel less like a loose comment pile.
Zaps matter because they make live attention payable while the room is still alive. Google Play lists zaps among the things a streamer can see while live, and the public Shosho profile describes receiving zaps from viewers. The technical zap flow is not Shosho-specific; it sits in the wider NIP-57 Lightning zap world. The product consequence is specific, though: a creator can speak, answer chat, receive value and keep the social proof tied to the same public Nostr identity.
Replays and clips turn a live moment into a library. Shosho Server records live streams for replay, with the 90-day limit noted above. Clips are more portable. The creator docs say clips are published to the Nostr network, appear on the Shosho profile and clips feed, and can interoperate with short-video clients such as Divine. The developer docs map that to NIP-71 video events: normal and short video can be legacy event-id records or addressable records, with kinds 34235 and 34236 preferred when metadata may need updates.
This is where Shosho stops being only a live app. It becomes a media graph. A live show can become a replay. A replay can produce clips. Clips can travel to other Nostr video surfaces. Chat can continue to point back to the live activity. Product links can stay discoverable after the stream. That is the open-network promise in a concrete form: one live session can leave behind more than a dead link.
Commerce came into the stream
The latest major Shosho release changed the shape of the app. Version 0.16.0, published on GitHub on May 28, 2026, added Shosho Shopping Cart, Shosho Seller Hub and the Help Center. The release notes describe the cart as a way to add products and check out without leaving the stream. Seller Hub is described as a backend for creating shops, listing products, managing stock locations and shipping, inventory, promotions, orders and fulfillment. That is not a small feature. It moves Shosho from "go live on Nostr" toward "sell while live on Nostr."
The docs split products into two modes. A Classified product sends the buyer to the seller's site or direct arrangement, with Shosho not handling checkout, shipping or payment. A Shopping Cart product keeps checkout on Shosho, collects email and shipping details, handles the order, and can provide order tracking and refunds through the Shosho system. Seller payout docs say shopping-cart sales pay out to a linked bank account, after funds are held until fulfillment and after the platform commission defined in the seller agreement.
Under the hood, Shosho's developer docs connect products to NIP-99 classified listings, kind 30402. A user's shop page can live at a Shosho profile URL, but the docs are honest about an implementation boundary: NIP-99 events are per-product and do not carry Shosho's internal shop metadata. In other words, the product listing can be a Nostr event, while the shopping-cart business system still has operated infrastructure around it.
That is not a criticism. It is the accurate map. Live commerce needs inventory, shipping methods, order emails, payouts, refunds, tax responsibility, seller agreements and dispute handling. Nostr can carry identity and product events. It cannot, by itself, make a parcel arrive or reverse a card charge. Shosho's value is in putting Nostr-native discovery and media around a commerce flow while admitting where a normal business backend still exists.
The operator trail
Shosho has a clearer public trail than many small Nostr apps. The app stores list Bravo Charlie as the developer or seller, with Google Play naming BRAVO CHARLIE HOLDINGS PTY LTD and publishing support contact details. The terms name Bravo Charlie Holdings Pty Ltd trading as Bravo Charlie, based in Manly, Australia. The public Nostr profile says the project is made by Rod, and Rod Bishop's own public Nostr profile points to Shosho, his GitHub account and his Nostr blog.
The public GitHub repository is not a full source tree. It is a releases repository under r0d8lsh0p/shosho-releases, with APK release assets, issues and release notes. Checked on June 7, 2026, GitHub showed it was created on May 15, 2025, had its latest release v0.16.0 published on May 28, 2026, and had 22 stars, 2 forks and 5 open issues. GitHub did not show license metadata for the repository. That matters. A release trail is useful, but it is not the same as an auditable open-source codebase.
The store privacy signals also deserve careful reading. Apple says the developer indicates no data collected, while Google Play says the app may collect and share photos and videos, audio and app activity, that data is encrypted in transit, and that data cannot be deleted. Shosho's own privacy policy says the app may collect Nostr information entered into the app and usage information including video and audio recorded and live-streamed to the Nostr network. It also says live streams and messages are distributed to Nostr and may be accessed from the network by third-party services.
The honest conclusion is not "danger" or "safe." It is this: Shosho is an operated live-video product using an open social protocol. You should treat it as both. It has Nostr identity and interop. It also has app-store distribution, camera and microphone permissions, Shosho-operated servers, optional third-party streaming servers, commerce infrastructure, retention windows and legal terms.
What to check before going live
If you are testing Shosho as a creator, start with a small private-feeling public test. Use a low-risk Nostr key or a signer setup you understand. Set a clear title, summary, thumbnail and hashtags for the Show. Go live for a minute, then open the stream from Shosho.live and from another compatible Nostr client. Confirm that the host profile, chat and replay behave the way you expected. Do not wait until an actual audience is watching to learn whether your relay or server choice works.
If you are using OBS, treat the stream key like a password. If someone else gets it, they may be able to publish video into your stream path. If you are bringing your own RTMP server, make sure the HLS playback URL is stable, public where it needs to be public, and not exposing admin endpoints. If you use Shosho Server, understand that replays are convenient but not permanent. Download or clip what you need.
If you are joining as a viewer, remember that a public live chat is not a private message. A kind 1311 chat event is part of a public activity thread. Your reactions, zaps and comments can become part of the visible room history. That is the point, but it should be understood before you type casually into a live stream with your main identity.
If you are selling, separate the two commerce modes in your head. A Classified product is a pointer to the seller's own purchase path, and Shosho says it cannot intervene in that purchase. A Shopping Cart product is handled by Shosho, with a different refund and support path. As a buyer, look for which button you are pressing. As a seller, understand the bank payout, commission, tax and fulfillment responsibilities before presenting a product live.
The fair verdict is that Shosho is one of the more concrete Nostr media apps because it does not stop at a demo. It has native apps, a web surface, a live-event model, mobile and OBS paths, server options, chat, replays, clips, NIP-99 products, a seller backend and a visible operator trail. The caution is that every part of that stack has a boundary. Nostr makes the room more portable. It does not remove the need for servers, moderation, bandwidth, payment handling, key hygiene or adult judgment.
Sources worth opening
This article keeps claims close to Shosho's own docs, app-store listings, release notes and the Nostr standards the product depends on. Start here if you want to verify the current state yourself.
- Shosho official web app
- Shosho Help Center
- Install the Shosho app
- Create your Shosho profile
- Go live in 2 minutes
- Going live from the Shosho app
- Going live from OBS or another encoder
- What is a Show?
- Live Show vs Show Chat
- What is a streaming server?
- Shosho Server
- Zap Stream Server
- Bring your own RTMP server
- How streaming to Nostr works
- Live event structure: kind 30311
- Chat: kind 1311 and 7
- Clips: kind 34235 and 34236
- Products: NIP-99
- NIP-98 HTTP authentication in Shosho
- Selling products on Shosho
- Becoming a seller
- Selling during a stream
- Shosho payouts
- Buying products on Shosho
- How to buy a Shopping Cart product
- If something goes wrong with a purchase
- Shosho replays
- Shosho creator clips
- Shosho Privacy Policy
- Shosho Terms of Service
- r0d8lsh0p/shosho-releases GitHub repository
- Shosho v0.16.0 release notes
- Shosho on Google Play
- Shosho on the Apple App Store
- Shosho on Zapstore
- Shosho public Nostr profile
- Rod public Nostr profile
- Shosho on NostrApps
- NIP-53 Live Streaming and Spaces
- NIP-71 Video Events
- NIP-99 Classified Listings
- NIP-98 HTTP Auth
- NIP-25 Reactions
- NIP-57 Lightning Zaps
