Why does the path need a “.ext”? The sha256 should be enough, right? Why confuse things with whether it’s a jpg, pdf, gif, etc as part of the path?

Reply to this note

Please Login to reply.

Discussion

Servers should serve the blob with and without the .ext

The .ext is just optional because its useful for clients and users to get an idea what type the blob is without downloading it first. a lot of web apps look for `.png` or `.jpg` on URLs before they show them as images

Is there some kind of metadata about the blob in blossom? If not, is it even possible as an extension on the protocol?

It is very useful for clients to understand the data before downloading the actual data. One good example would be image resolution so apps can prepare the layout properly before image is loaded. This helps with performance and cleaner ux.

Servers can offer additional metadata on media or any other file type but none of the metadata is synced or stored on other servers.

You could store some metadata in k:1063 events or NIP-94 tags though

It would be awesome if Blossom would provide that info in the response header. That way apps could make an http request for just the header without downloading the whole thing.