Oddbean new post about | logout
 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. 
 We have proposed the start of a lot of this here https://github.com/wavlake/nom-spec