Hello, was reading the specs at https://github.com/hzrd149/blossom
I'm now implementing the protocol, in fact was already using it in similar fashion anyways since it is practical to serve files so thank you for defining this neatly.
Have a few questions if you see possible to answer.
1) why use the hexadecimal for npubs instead of the traditional npub1...? I ask because it is easy/fast for me to find the user account but like this seems I'd have to extra CPU to get the value
2) I understand we identify the sha256 file hash with the user npub so that he can request to delete the file and we can identify how many files a user is uploading among other similar operations. Is that correct?
3) how can we advertise the files in our server to other servers? Right it will use the user-appointed servers but I'm imagining the scenario of searching across the +400 nostr servers today for a specific file hash. I know we can ping them all individually (and we will) but bandwidth and CPU are expensive, if servers can advertise their files then it is easier to balance the load across different servers or automatically go to the ones that report having that file.
Thanks!
brito
npub1hf…p7yfm
2024-09-27 20:16:59
in reply to nevent1q…857p
Author Public Key
npub1hfg3tsmmp7g3u5cw6mzg0n9andehmgel6jug486eppsr0rqx4a3qlp7yfmPublished at
2024-09-27 20:16:59Event JSON
{
"id": "f9822dc9bc2cc35c9d095de7431e6361d57d2399abf3d9da8f7163076711611f",
"pubkey": "ba5115c37b0f911e530ed6c487ccbd9b737da33fd4b88a9f590860378c06af62",
"created_at": 1727468219,
"kind": 1,
"tags": [
[
"p",
"b7c6f6915cfa9a62fff6a1f02604de88c23c6c6c6d1b8f62c7cc10749f307e81",
"wss://nostr.cercatrova.me/",
"florian"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
"wss://nostr.wine/",
"hzrd149"
],
[
"e",
"1838dd2ee3f5148e06b56450eef657a839ea449d1032a6b7cc1c1300fb9fd964",
"wss://nostr.wine/",
"root",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
]
],
"content": "Hello, was reading the specs at https://github.com/hzrd149/blossom\n\nI'm now implementing the protocol, in fact was already using it in similar fashion anyways since it is practical to serve files so thank you for defining this neatly.\n\nHave a few questions if you see possible to answer.\n\n1) why use the hexadecimal for npubs instead of the traditional npub1...? I ask because it is easy/fast for me to find the user account but like this seems I'd have to extra CPU to get the value\n\n2) I understand we identify the sha256 file hash with the user npub so that he can request to delete the file and we can identify how many files a user is uploading among other similar operations. Is that correct?\n\n3) how can we advertise the files in our server to other servers? Right it will use the user-appointed servers but I'm imagining the scenario of searching across the +400 nostr servers today for a specific file hash. I know we can ping them all individually (and we will) but bandwidth and CPU are expensive, if servers can advertise their files then it is easier to balance the load across different servers or automatically go to the ones that report having that file.\n\nThanks!",
"sig": "af1e98480caa6b53e00c988ff7d3668784eea045d3624e4cdb32a4116bba43d77776bef77b1811eab76afa490a8aa7347b600aa534302ea984c38f87bd08315c"
}