GM, my only comment is that for cursor-based pagination, it would be nice to include previous and next URL links (either in the body or in HTTP headers). Have a look at HATEOAS / HAL. This is better than forcing clients to figure out the URLs on their own.
As for Negentropy, I think Blossom could implement a simplified version of NIP-77. It would be nice if there were a global date we could sync with or perform range requests on. But even if there isn’t, I’d say the most useful sync "filter" would be by the author's pubkey. I.e., I would only use it to mirror or migrate my blobs to a different server.
Honestly, for my personal use cases, even manual syncing (e.g., if a client allowed me to add multiple Blossom servers and automatically use the mirror endpoint whenever I post or broadcast a note with Blossom media) would already be a huge step in the right direction.
Do you know of any Nostr clients that are BUD-03 compliant and handling the whole URL check / Kind 10063 retrieval process?
https://github.com/hzrd149/blossom/blob/master/buds/03.md#client-retrieval-implementation
noStrudel? Amethyst, maybe?
Anthony Accioly
npub1a6…w0tyc
2025-03-30 10:10:01
in reply to nevent1q…p6az
Author Public Key
npub1a6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajq7w0tycPublished at
2025-03-30 10:10:01Event JSON
{
"id": "e33f2bfb546d9a118bce8eeaf0d6641c0a4c3f2a4b4ea7a75d2195e53ff9bafa",
"pubkey": "ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64",
"created_at": 1743329401,
"kind": 1,
"tags": [
[
"e",
"d8ffde3b0cfd82e6c9b236c48a4f49aa3c539f817de8d50fc517fd1bf79cedd3",
"",
"root"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
],
[
"r",
"https://github.com/hzrd149/blossom/blob/master/buds/03.md#client-retrieval-implementation"
]
],
"content": "GM, my only comment is that for cursor-based pagination, it would be nice to include previous and next URL links (either in the body or in HTTP headers). Have a look at HATEOAS / HAL. This is better than forcing clients to figure out the URLs on their own.\n\nAs for Negentropy, I think Blossom could implement a simplified version of NIP-77. It would be nice if there were a global date we could sync with or perform range requests on. But even if there isn’t, I’d say the most useful sync \"filter\" would be by the author's pubkey. I.e., I would only use it to mirror or migrate my blobs to a different server.\n\nHonestly, for my personal use cases, even manual syncing (e.g., if a client allowed me to add multiple Blossom servers and automatically use the mirror endpoint whenever I post or broadcast a note with Blossom media) would already be a huge step in the right direction.\n\nDo you know of any Nostr clients that are BUD-03 compliant and handling the whole URL check / Kind 10063 retrieval process?\nhttps://github.com/hzrd149/blossom/blob/master/buds/03.md#client-retrieval-implementation\n\nnoStrudel? Amethyst, maybe?",
"sig": "49be2877e755aea53acea914d5533331c5941787ab6195f5c5b9ffc4cb02c21de160134a4afdea274ce1ff0260199fe35cc899bfc6c4c47ac3082a0451d4b90e"
}