do we have a list of file types we can upload here? also max size? Cause if the media uploads for nostr are poorly designed there is some fun to be had

Reply to this note

Please Login to reply.

Discussion

The media upload presented to you by slick nostr clients is out of band using services like void.cat or nostr.build. it's like xmpp http upload, just not standardized. They're also just downloading the link in the message and displaying it, afaik there is no 'attachment' metadata field

it's all ad hoc

And that is gay. It's their design choice to not have relays store uploads. At least let us configure our own S3 server to use

Relays not storing uploads as part of some in-band spec isn't a huge problem imo.

All you need is

- protocol extension to designate a url as holding an attachment (NIP, not hard)

- clients to allow you to configure what you use as the uploader (nothing really that can be enforced, hard)

the second part is harder because fragmentation. Maybe not everyone decides to play nice and allow you to set the place you are uploading. HTTP is probably the lowest common denominator for uploading/downloading attachments.

I think relays optionally running an http upload endpoint would be really cool because you could distribute where you upload to across many different relays. Then add a NIP to discover which relays you know about offer this service. I think this would be ideal.

Yes, just like the Fediverse. By default, instances store and serve uploads but you have the option to add an S3 server or Media Proxy Provider

I think the fedi spec does attatchments pretty much right (except for the not so strict whether the key is always present when empty, whether it is a string, or an array, cause different implementations do it each of these ways because fuck you other server)

Nope. You could run MinioS3 and upload to there and paste the url to any nostr client to use your own upload service