And does it now mean if we're going to be enforcing file extension that the GET requests will be /. soon? Hoping to align this right. Thanks nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr

Reply to this note

Please Login to reply.

Discussion

Or, maybe also include using the returned URL in descriptor as a fallback? That way there's backwards compatibility? Since, a lot of current Blossom implementations appear to be utilizing it in that way.

no, the extension on the "GET /" endpoint will always be optional. mainly because its not important to the server, its mostly there just to allow the client to have a hint at file type so it can show an image / video / pdf viewer

Although I'm going to open a PR tomorrow to make the file extension required on the "url" field returned from the /upload /list and /mirror endpoints. since that field is intended to be used by the client and the client generally needs the file extension