Nostr Web Client

I’ve been musing over the best strategy for uploading media to #nostr. Most people can already host a relay but I doubt they’ll want to host their own media, not to mention doing it for others.

Services like nostr.build allow you to upload and will serve your media but I get nervous about it going away one day and losing access to all my uploaded media.

This is where a protocol like #ipfs might be useful. Without doing much in the sense of a media server, you can run the ipfs daemon and pin files you intend to share and use the url of a public ipfs gateway to serve your files.

I’m going to experiment with hosting future media content on ipfs and see how it goes.

Reply to this note

Please Login to reply.

Discussion

The(H)Emperor 2y ago

The uno-nazis must hate your idea, having individual sovereignity is against their objectives of total command and control over earth, life and mankind.

The(H)Emperor 2y ago

I follow you.

Kristaps K. 2y ago

I’m thinking can BitTorrent be useful here?

takinbrrrr 2y ago

Naturally. The issue with Bittorrent (and why I didn’t suggest using it) is that it requires more tooling for it to work. Although both (Bittorrent and IPFS) use DHTs for locating content, IPFS (in my experience) is faster in locating content. You would need a tracker to be able to do so with Bittorrent. There’s also the need to have a HTTP interface for accessing media files. This comes bundled with the IPFS daemon. In general, IPFS is probably better for storing and serving many small files and Bittorrent for larger files.