Oddbean

I brought this up with hzrd, but this thread might be a good place to get feedback from others and @PABLOF7z, as i'm not aware of a channel to discuss blossom dev, i just see it being discussed every so often: Run Blossom in a webcontainer, as its own server. Webcontainers are able to run nodejs and any npm package in the browser which means integrating one with blossom and a simple server would enable: Hardware agnostic set up, just visit the i.p/url, install it as a progressive app, done. You can start serving your own files, itseld or those of others from the browser. Each client becomes a serving node in the network, while the browser is open. In the monetized environment envisioned by the devs, this means simply opening an instance and being the nearest to need in terms of serving speed, could earn someone zaps ! With this design, Blossom becomes the nostr coordinating daemon, in a sense. I'm not sure i'm explaining it well so i will also describe the user journey: Alice opens their nostr app. They notice a post with a new video from a creator they enjoy. They want to boost(repost) this video but they also think it will be very popular and want to participate in its spread, so they also click the option in their client to help it blossom. This changes context to their local webrowser, which loads up a local copy of the webcontainer hosting the file (blossom). (Since these containers and all associated npm packages install very quickly this happens in seconds.) The context can also switch to an instance they already have running and adds the files hash and address to its serving list. Alice goes back to her nostr client and continues bloom scrolling, with the added potential of earning sats simply for keeping a browser/server open.