🐈⬛
Nov 22, 2024
Amethyst 🌸 support incoming in 3,2,1 ... 🔥
Fyi cdn.nostrcheck.me and cdn.satellite.earth will do great in your options, plus if you run haven. As because I am too lazy to hop to the strudel and nostromo just for the blossom support. Btw if primal stops fucking up the hash, blossom.primal.net will do too. The whole point is to find the file everywhere and to get delivered no matter which one of the 🌸 works at the time.
Fyi cdn.nostrcheck.me and cdn.satellite.earth will do great in your options, plus if you run haven. As because I am too lazy to hop to the strudel and nostromo just for the blossom support. Btw if primal stops fucking up the hash, blossom.primal.net will do too. The whole point is to find the file everywhere and to get delivered no matter which one of the 🌸 works at the time.
npub1ye5pt
•
Nov 22, 2024
Replying to @USER
Client can and probably will use the "url" field returned from the /upload endpoint when composing kind 1 notes. although the GET /<sha256> serves a different purpose
Take this note for example
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 /<sha256>" endpoint to be in the exact same location on every server. so its super easy for clients to quickly fallback and check other servers
Take this note for example
npub1ye5pt
•
Nov 3, 2024
See translation
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 /<sha256>" endpoint to be in the exact same location on every server. so its super easy for clients to quickly fallback and check other servers
See translation
See translation
0
0
0
0
0
No replies