Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 5
Generated: 21:32:30
Login to reply

Replies (5)

You intend to do chunking from several? Otherwise option to choose a blossom server from popular ones to upload to with short description to each one, what they support size/compression, mybe a recommendation to spin your own blossom, for the rest of us who know the drill fetch the 10063 with the blossoms we already chose to upload to in some client (wasn't that what bouquet did), including self-hosted etc. https://video.nostr.build/3c59264af8b07288387de0e48a2ec16ad11367a959794f68ab9f731855c10086.mp4
2025-11-15 13:39:08 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
Yeah I'll have a server selection like in bouquet. For now I have blossom servers hidden it in the settings... might need to bring it into the upload dialog. Uploads: - I want to support uploads in the GB range, that's why I have implemented a blossom server that uses https://github.com/hzrd149/blossom/pull/67 - My idea is to have an "upload server" and than use blossom mirror to move it to other servers. - Issues a) Mirroring is not supported by all servers. b) Size limitations and max storage capacity can prevent uploading, i.e. the user needs to know where to upload. - Transcoding and HLS will fix this but I'll tackle that later. Watching / Downloads: - Almost all blossom servers take multiple seconds to stream a video (nostr.download is quick). - Not all support range request, i.e. you can not skip in the video until it is completely downloaded. - My idea is a blossom-proxy (https://github.com/flox1an/almond) that caches videos and supports fast downloads. - It works without the proxy but UX is better with caching and it's another piece that needs to be configured. - Chunks from different servers could be done with HLS.
2025-11-15 14:32:15 from 1 relay(s) ↑ Parent Reply