Stuart Bowman on Nostr: I recently updated some stuff to be compatible with the blossom spec - there are now ...
I recently updated some stuff to be compatible with the blossom spec - there are now two endpoints, cdn.satellite.earth and blob.satellite.earth. Unless there is some kind of bug, I believe the cdn endpoint still works and should still contain the file extension as it did before. The only thing that has been changed is that the cdn endpoint 301 redirects to the blob endpoint (which does not contain extension). So if you use the blob endpoint directly it will cause a problem in some clients, but if you continue to use the cdn endpoint as before it should still work
Published at
2024-04-01 23:14:43Event JSON
{
"id": "72fcae871d960832020986b0ff1db83be1e93e3db582878bee19a45d0639b5d0",
"pubkey": "ff27d01cb1e56fb58580306c7ba76bb037bf211c5b573c56e4e70ca858755af0",
"created_at": 1712006083,
"kind": 1,
"tags": [
[
"e",
"777059dd7463863745d575b4099cf47392730d5bf858f1962225804064693b83"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "I recently updated some stuff to be compatible with the blossom spec - there are now two endpoints, cdn.satellite.earth and blob.satellite.earth. Unless there is some kind of bug, I believe the cdn endpoint still works and should still contain the file extension as it did before. The only thing that has been changed is that the cdn endpoint 301 redirects to the blob endpoint (which does not contain extension). So if you use the blob endpoint directly it will cause a problem in some clients, but if you continue to use the cdn endpoint as before it should still work",
"sig": "58f3e2e41a7136c3495903aa93cfc579d0247cb724c97b602000d96ae06583c40a52b0cec0dbb54ea13ba6504205b648ceac28e7723fa8c59b2f1a65edffbe92"
}
