My personal recommendation is go full-sovereign and just upload your mp3s, rss feed and image files to a web server you control and run your own lightning node to receive the boosts.
Discussion
Good call! This is the ultimate sovereign way, how we used to do it nearly 20 years ago. I wonder if any open source tools exist for people to easily do this now? Hell I think I used WordPress and some plugins back then. Surely better tools exist now?
I personally just write my own RSS in VS Code, then uplaod it to my DreamHost server with FileZilla. I realize to anyone that might not have experience doing something like that it seems tough at first but it's not too taxing to take a template and just replace the values with your own tracks. I made a sample template here for people to go on, it contains a comment that explains each individual tag:
https://github.com/de-mu/demu-feed-template/blob/master/feed-with-comments.xml
I'm very interested in playing with the new tool Blossom that nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr is working on to potentially make the uploading/hosting process even easier and cheaper!
With each passing day on Nostr I'm going crazier and crazier wishing our products were already ready to get in front of people.
This is exactly the use case we're working on at my company.
Must go faster!
What are you building at your company?
Our full documentation will be arriving before long, but we have a brief here for now: https://vaporware.network/
In simple terms: a personal server VM. But the deeper details matter:
A Vaporeware "ship" is cryptographically-owned, peer-to-peer cloud VM built on a Solid State Interpreter written in a purely functional language. The ship's data, code, state and event log are all persisted as a **single** value - which means you can "unplug it" while it's running, move it to a different host, device, phone, etc. kick it back on and everything is precisely the same.
Every ship is identified by a keypair (just like nostr) and encrypted. not your keys, not your computer.
With all that said, the upshot _for nostr_ is: Once there is a "nostr relay" app installed in your ship, it will just run, "forever", with zero setup or maintenance. A one-click personal relay that your grandmother could setup. Additionally: uploading and serving many gigabytes of large files is trivial (and fast as hell) - some of our earliest demos were S3-style services. This means that the same ship that is providing your nostr relay will also serve as your personal content host. And because of orthogonal persistence (https://ngnghm.github.io/blog/2015/08/03/chapter-2-save-our-souls/), data loss just isn't a thing.
(if you're still reading by this point...) On top of this platform we're building a system of software distribution so that developers can build, fork, update, extend, modify and **sell** code peer to peer with end users (and other developers). At the moment, we represent software packages as NFTs because there are a lot of useful payment and distribution primitives there, but our ultimate design for The Agora is chain agnostic (chain optional, even).
You might build an enormous google-like app suite, or just a better sort function primitive - either way other users can seamlessly include this new code in their ship by buying it directly from you.
I'll stop there :) Always happy to answer questions!
This sounded interesting until I read about the shitcoining. Not everything needs a token. Software applications actually work just fine without them.
Agreed there and I recognize that bitcoiners will get scared off by that (me included).
Shitcoins will be an option to for shitcoiners, but not baked into the core system. Everything compelling about a vaporware ship will always be possible without ever touching ethereum.
Just as Bitcoin's blockchain is untainted by the fact that Shitcoins also use blockchains, your ethereum-free vaporware ship will be untainted by the shitcoinery of others.
This is the way voluntarism and exit work and it is a good thing.
A bit more on that: our software distribution _protocol_ isn't aware of the chain (because we're not crazy people). it's just a distribution and signature verification system. You could post the hash of your source on your personal website, rather than onchain - or you could build your own software storefront that uses whatever scheme you want that keeps the shitcoiners out. We hope that many paths and various darknets will spring up that operate on their own terms.
We expect that those who are interested in playing bizarre defi speculative token games will benefit from having "software distribution" as part of their arsenal, so we're providing hooks for them to have their own fun. But we're also keeping such antics firmly isolated from the FOSS kernel and purely optional wherever it fits in.
it's actually called VaporWare
Shitcoinery INC
a suit rationalizing it
where's the punchline
Our OS and the Plunder system we build on are all open source. Go inspect the code and show me where you find a shitcoin or even an ethereum RPC url.
(and feel free to inspect me, searching for a "suit". I think you'll have as much luck as your shitcoin hunt in our code)
I'm happy to have a productive conversation with you if you want.
