Torrent protocol is battle tested. And who said it had to be web ready ? Why should this be a constraint ?
There would be an obvious question of the data persistence - e.g : how long should I seed - but nothing that seems to be a huge impediment to me
Having some example of a kind of workflow like : I chose a file to share in my client. The client creates a magnet link to be shared through nip-94, seeds the file, and users that want to access the file retrieve it thanks to the magnet url and an embedded torrent client.
Am I missing something obvious here ?
Regarding 1. Why another protocol ? P2P file sharing exist since a long time and are battle tested.
Many nips are not supported in many clients. I don't see this as an argument.
As per the people not wanting nip-94 why not let the clients provide choice to the user to filter out those events ? Nip-94 per se doesn't cost much as it is only file headers which is quite light
I can understand the take regarding nip-95 ( even if I don't have a particular opinion ), but I don't get it about banning nip-94
Isn't nip-94 only about file headers ?
There should be a NIP to ban anyone from the network that support Hawaiian pizza
You know you can ask for note deletion right? 😅
Unfortunately nope. Best thing (s)he can do afaik is to warn people about it and start fresh
Raclette, definitely obvious raclette on the way
Fuckin' hell. So this what we call multiverse ?

Bonjour, article bien sympa sur les DNS menteurs.
https://www.bortzmeyer.org/fdn-dot-doh.html
#nostrfr #FDN
I see Bortzmeyer, I upvote 💜
Bonjour bonjour ! Et bon appétit bien sûr !
Salut les #nostronautes !
J'espère que vous êtes en forme ! #nostrfr
Ici ça se réveille au son de cloche sans ménagement :

How would you qualify it then ?

