Nostr Web Client

I know the feeling… I put a couple of bits out on Wavlake and the instant gratification of sats was cool but I then felt I was giving over control of the work to another platform, all be it with a better payments scheme.

I now aim to release as RSS and physical only, I do a daily music show (playing other people’s music but also a lot of things I’ve engineered etc) and I self host using Castopod, that works on the ActivityPub protocol. This also enables music releases. I put something up a couple of months ago to test the tech and it appears to work well. Visibility is an issue, the only social media I use is the Fediverse and Nostr. I’m at the stage where if I can’t self host it, I’m not really interested (Nostr is different but I need to up my skills level to take on Blossom servers).

I don’t have any great answers, I’m just a weirdo sound guy tinkering in a shed but at least I’m not dancing to some other bastard’s tune. A better system is possible but it’s on us to figure it out.

SondreB 1w ago 💬 1

The content needs to integrate with Nostr somehow and rely on Nostr-native mechanisms for zapping. That will at least set content creators up for a good start, then what is left is getting exposure. Creators can pay for exposure and the more content we got on Nostr, the more people will come. We got a lot of content, but it's still not enough.

Reply to this note

Please Login to reply.

Discussion

Heuristic 1w ago

Hopefully you like #techno then since the whole album is basically that and #breakbeats lol.

inpc 1w ago 💬 1

Would a Blossom server be the best way to achieve that? Admittedly I don't really understand what they are yet... On my to do list to study. ActivityPub has numerous options at this point but I'd love to get something Nostr native running and ideally something that interops well with the Fediverse, I know folks here have issues with it but it's been my online home since 2019 and it was a thriving indie music scene, something we're some way behind here.

set:// 𓁣 🏴 probably 1w ago 💬 2

you have a blossom server already, mate! add https://relay.inpc.cat to the top of your clients blossom server list! :aliendance:

set:// 𓁣 🏴 probably 1w ago

not sure how that link renders in your client, but for blossom it has to be https:// not wss://

inpc 1w ago 💬 1

Ah ok, I really need to read up on Blossom servers.

set:// 𓁣 🏴 probably 1w ago

There's more to it, but the main difference from, say fediverse upload, is that the file hash becomes the file name. So a client can query the server indicated in the note for the file, but if it is not there, it can look for the same file on any other blossom server it knows of. Typically, the access control is different from the things you are used to. I.e. your haven relay on relay.inpc.cat will not accept files from anyone else than you, and that's why you have to sign an event for the blossom to accept the file.

SondreB 1w ago

Blossom Servers are very basic binary file storage endpoints. The protocol allows you to mirror your files across multiple servers.

Then when you create any event on Nostr, depending on which client you use, the client will include URL to all your mirrored copies of your files. So, let's say someone comes across your 2-year-old Nostr event, and they first Blossom server is long dead, it might still work if the second or third Blossom server is still running.

Great for uploading and storing podcasts, music, etc. They can also transcode uploaded videos to smaller sizes, or photographs.