Sounds like a great application for IPFS! To be fair, Blossom blobs are hash based, and hzrd149 (nprofile…wj75) has also been asking around about "Negentropy." On top of that, if clients follow BUD-03 as intended, they should be able to recover the media from any of the servers in a user list: https://github.com/hzrd149/blossom/blob/master/buds/03.md
However, your idea of leveraging IPFS sounds very promising. The client wouldn’t need to implement fallback logic or fetch the media elsewhere, users wouldn’t have to carefully manage redundancy by mirroring blobs and managing multiple blossom servers, and a simple "just download and seed my stuff" approach is certainly a great way to do things.
I’d definitely like to try what you’re building (or planning to build) once it’s out there. And if it can be made Blossom-compatible, that would be even better. I know that despite both systems using SHA-256 hashes by default, they aren’t exactly compatible OOH. IPFS uses CID versioning, supports multiple ways of encoding hashes and even multiple hash algorithms. But given that IPFS has some flexibility built-in and Blossom is an emerging standard, I think there are ways to accommodate this.
Anthony Accioly
npub1a6…w0tyc
2025-03-31 10:44:59
in reply to nevent1q…zhvz
Author Public Key
npub1a6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajq7w0tycSeen on
wss://theforest.nostr1.comPublished at
2025-03-31 10:44:59Event JSON
{
"id": "54202ccd190dd4c1755dd8a306cae8ea3cebd23d27abb7e4cf5695ccfec1c59d",
"pubkey": "ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64",
"created_at": 1743417899,
"kind": 1,
"tags": [
[
"e",
"6515da2900d1cbff94d3b8989922a58a298873840466bdc4bb6cc39bed3647a1",
"",
"root"
],
[
"e",
"00001c5acadc3c7d99890eaf01cf123dfb4cdf8d25aa09da2dc1ba4c3f8d9a56"
],
[
"e",
"acf4e8bac971c0adb0de30f8f7c7593c9b18a2066a2ea730ea825b160a37e6f3",
"",
"reply"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"45835c36f41d979bc8129830f2f5d92562f5343d6feddd6f30aa79480730f26e"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5",
"",
"mention"
],
[
"r",
"https://github.com/hzrd149/blossom/blob/master/buds/03.md"
]
],
"content": "Sounds like a great application for IPFS! To be fair, Blossom blobs are hash based, and nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpr3mhxue69uhhxct5v4kxc6t5v5hxs7njvscngwfwvdhk6tcpzfmhxue69uhkummnw3e82efwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsk7wj75 has also been asking around about \"Negentropy.\" On top of that, if clients follow BUD-03 as intended, they should be able to recover the media from any of the servers in a user list: https://github.com/hzrd149/blossom/blob/master/buds/03.md\n\nHowever, your idea of leveraging IPFS sounds very promising. The client wouldn’t need to implement fallback logic or fetch the media elsewhere, users wouldn’t have to carefully manage redundancy by mirroring blobs and managing multiple blossom servers, and a simple \"just download and seed my stuff\" approach is certainly a great way to do things.\n\nI’d definitely like to try what you’re building (or planning to build) once it’s out there. And if it can be made Blossom-compatible, that would be even better. I know that despite both systems using SHA-256 hashes by default, they aren’t exactly compatible OOH. IPFS uses CID versioning, supports multiple ways of encoding hashes and even multiple hash algorithms. But given that IPFS has some flexibility built-in and Blossom is an emerging standard, I think there are ways to accommodate this.",
"sig": "537997f02746a4053c1b81b449a69c2c99b48ad5829edb69f2f73482f7368817eb496a5f999a9fe06bb988d61a86edf15e337bf70c7d94bc951d8685f5427780"
}