The "GET
generally its also good to have the /upload endpoint on the same domain because clients wont be able to easily know about both domains. and when users select a the blossom server in a client they would be only setting one of the domains
The "GET
generally its also good to have the /upload endpoint on the same domain because clients wont be able to easily know about both domains. and when users select a the blossom server in a client they would be only setting one of the domains
Hmm that might not work for a lot of folks who use object storage providers... including our friends at nostr.build if they end up wanting to also support Blossom, as their media is on various subdomains too.
So, maybe the default could be
Or, am I completely misunderstanding this and the GET to /
Client can and probably will use the "url" field returned from the /upload endpoint when composing kind 1 notes. although the GET /
If my main server cdn.hzrd149.com went down or the image was removed from it. clients could lookup my preferred list of blossom servers (kind 10063 event) and start going down the list asking each one for the exact same blob (without needing to know how the server works)
1. 
2. 
Thats the point of requiring the "GET /
Ah gotcha! Ok, thanks for explaining that 👍