#nip-96 is currently supported by 6 file upload servers, which is more than #nip-97 (probably one demo server), but less than any nip using relays directly (#nip-95, or kind 334/335)

nostrcheck.me

nostrage.com

sove.rent

nostr.build

files.sovbit.host

void.cat

#kind-334 / #kind-335 are exclusive kinds for #nostrfileviewer, which supports any size of #files #uploaded directly to #relays. it supports #uploading #images without additional #compression / quality loss as well as uploading any other file type, like #archives, executables, #videos etc..

http://bafybeifv7ocpq7pkbwtw5bygwzinfregj2gsvfxge2likxbiftcbik6ag4.ipfs.cf-ipfs.com/#/hostr/p/c489c2bb22c693fc4bfaf444cc34fb247c2132995683ab659222725270d81635/d/fileloader.html#/quiet/filter:jpg/inlineall/noinlinelimit

Reply to this note

Please Login to reply.

Discussion

maybe #http #fileupload with changing #tor #onion addresses would be best for keeping #files and ignoring toxic #dmca #takedown requests

these onion #servers could #announce their existence in nostr #events. their addresses could even change regularly, so that one could not know whether the file they requested comes from same or different server now or tomorrow, as same server could change their onion address.

so i'm #proposing some kind of #announce event for file #servers

any nip or #kind they are using, they should announce they are #file servers and you can #find files there. these server addresses could be #clearweb #domains, #ip addresses, #ipfs addresses or #onion addresses