NIP-94 introduces a File event type to nostr. File mime types are included as a m tag on the event, so creating file-type specific clients (3d models, pictures, videos, audio) is straightforward. As the spec settles clients that upload files can start to publish these events.

Reply to this note

Please Login to reply.

Discussion

Is this merged?

Got it. Thank you! I will check it. Did you check another nip proposed by nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj ? it looks very similar

So actually last week we decided to merge the proposals and just copy all the tags from NIP-81 (my proposal for modeling files and file sharing via torrents) into NIP-94

https://github.com/nostr-protocol/nips/pull/337#issuecomment-1504975505

Thats why they look the same :)

:) haha thats why. Zapped! It’s good work!

Thanks! I was glad to get the torrent stuff formalized at the protocol level - it’s going to enable a couple really cool features I’m currently building for Satellite

Cannot wait!

3D models!? omfgggg

Holy shittttt I fucking love it!! Game changer 🀯🀯🀯

Uncensorable thingiverse with zaps and torrent fallback for files. Blows my mind.

I know?!

Is that the going away party?!

πŸ’Œ

More culo that.

🫢🏻

And aids infected whattism to go with that, since that culo is highly phobic too.

πŸ‘»

Hey you.

Not hatey?

#haiti

🫢🏻

Omfg you’ve got me so hyped right now bro holy shiiiiiittttt

File are you?!

πŸ€”

Good to know that’s the case with more then. Knows does the rotten fruit?

πŸ’Œ

Is it possible to store data directly in it ?

From what I understand it does not provide anything related to file storage. It just allows file header publishing and file integrity confirmation.

Regarding file storage directly within the messages/events I'm a bit skeptical. This could lead to some huge data to download, as the nip-95 would allow keeping messages and events quite small.

I'd rather have anoter kind of event or message that would provide a pointer to the content, be it the content is on another P2P protocol ( hello torrents ). This way clients could configure and fine tune how to handle each different kind of file

Erratum : read nip-94, not 95

NIP 94 has optional magnet and infohash tags. void.cat supports this, all upload are seeded as torrents.

It's pretty cool, it could enable a search engine for torrents

I am very interested in this πŸ˜€

Fits your service like a glove, check out the NIP https://nips.be/94 I built a small client for creating and seeing this in https://github.com/verbiricha/filestr https://filestr.vercel.app/

I'm going to take a look at it and get down to work. πŸ˜€

Awesome, for these lists I want to show it as a gallery in habla.news Let me know if you create one, can use the naddr to embed in any post.

OK!! πŸ˜€

For galleries we could use NIP-51 lists with e tags pointing to file events. What do you think?

It seems to me a very good way to solve it and also to take advantage of the different NIP's and not reinvent the wheel.

Interesante. SerÑ genial. 🀟🏼