nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr blossom doesn't really do file chunking correct? As it stands, files are loaded into RAM and served as a single file?
Discussion
yes, there isn't any chunking in blossom. which made it a lot simpler for small files and easier to write server implementations but it limits the size of the file that can be easily uploaded or transferred
Can I DM you something ive been thinking about the last week or so? I'm traveling home and need to catch a connecting flight so its gonna take me a sec to send it out but I'd like a reality check. Its 2 new BUDs that would make a "torrent gateway" and *might* help with the Size Constraints in Blossom. It builds on nip 35 as well for torrent indexing.
I can also just wait until I have a rudimentary server implementation fully built. But im kind of excited and could use some feedback.
send me all your ideas, but don't let me stop you from building. if you can find a good way to bridge torrents and blossom that could be interesting for a lot of nostr clients
I played around with the idea a bit but didn't see much use to implement it at the moment
https://github.com/hzrd149/blossom/blob/chunked-blobs/buds/10.md
files don't have to be fully loaded into RAM, they can be streamed from disk
there is also the http range header that is fully compatible with blossom