Oddbean new post about | logout
▲ ▼
brugeman | 5 months ago (raw) | root | parent | reply | flag +2 
 How does Peertube solve the problem of dead instance/links?
▲ ▼
Râu Cao ⚡ | 5 months ago (raw) | root | parent | reply | flag 
 It doesn't, same as there is no solution to that on Nostr when it comes to (at least close to) YouTube-quality video hosting. But it is a real alternative that is better than only publishing to YouTube right now, which is what the original post and reply were about.
▲ ▼
brugeman | 5 months ago (raw) | root | parent | reply | flag 
 > If that server shuts down or censors you (easy via your npub), then the URL is dead, so the link in your event is, too. It has none of the guarantees of real nostr events that are published to relays in the current form of the spec.

I explained how nip96 and blossom are our poor-man's solution to the problem you stated in this branch. You dismissed it, and proposed we integrate with something that doesn't even try to be a solution. Not sure where you're heading here.
▲ ▼
Râu Cao ⚡ | 5 months ago (raw) | root | parent | reply | flag 
 I didn't dismiss it, I explained why it's insufficient to currently replace e.g. YouTube.

* Peertube tries to be a solution for replacing YouTube with a decentralized system. It is working well, but isn't 100% on the decentralized end of the centralized/decentralized spectrum yet. Its video player embeds can be used on any platform or protocol.
* NIP-96 tries to be a solution for replacing sites like Imgur, and both it and Blossom are preparing for being a solution (or you could say they're already half a solution) to the problem that e.g. IPFS is tackling.

These are different problems to solve, and if you want someone to "post their content natively to Nostr" then you need a proper implementation of a client+server that implements a real YouTube alternative based on e.g. Blossom.

Maybe I missed where you pointed me to that existing. If not, then I think the next best thing is to recommend publishing to a working YouTube alternative that is open-source, customizable, self-hostable, and not centralized to a single corporation.

Please don't get me wrong, I'm not at all against solutions based on what you're suggesting! I just believe it doesn't help actual creators, or their perception of Nostr for that matter, to tell them "no zaps from me", if they post HTTP links to their own content on Nostr, but aren't linking to a single, large mp4 file using the most widely supported (thus much larger filesize) video codec on a pure file hosting server that you approve of.
▲ ▼
rossbates | 5 months ago (raw) | root | parent | reply | flag +1 
 Your last point might be the most important. People who are creating content just want something that’s easy and it works today. They are rarely concerned about the implementation details that we enjoy debating. They just want to know, “does it work?”