Nostr Web Client

Trying out nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg on android. Like the music experience. I just wish there was a way to share music/podcast information between them, nostr:npub1t8cmt7hjnyz0a99x5ppw9kpdsrtglst26aj3aw5s4r0rna3l3l5qk89gm4 and nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 to make it truely decentralize. Nostr seems like a good idea cause they could have their own relays and just exchange the info if needed. Idk.

At least I can bridge Nostr and Mastodon with nostr:npub10qdp2fc9ta6vraczxrcs8prqnv69fru2k6s2dj48gqjcylulmtjsg9arpj I'll have to set up my own server, but I think it might be doable.

Reply to this note

Please Login to reply.

Discussion

Wavlake 1y ago

We publish everything to Podcast Index VIA RSS, which is pulled in by Fountain, etc. Is that what you mean?

PABLOF7z 1y ago

What about publishing nostr events?

odysseywestra 1y ago

No what I mean is the userdata for what songs/podcasts/playlists we add to our library along with our queue and played state. If that data is portable and could be stored on with Nostr, IPFS, or some decentralize database, that would be awesome. Though for that to happen, all the podcasting 2.0 app developers would have to agree on a storage standard to make it happen. We already have an identity base system with Nostr, so that can be taken advantage of as well. IPFS has been around forever so that can work too.

All-in-all I love what been happening already, it just seems that this is what needed to be address so all the user has to do is pick their favorite provider/podcast app and off they go.

Wavlake 1y ago

We have proposed the start of a lot of this here https://github.com/wavlake/nom-spec