there is a reddit and 4chan like social media protocol on ipfs, its a bit more wild west. it uses pubsubs.
but its nothing like nostr, nostr is more profile based, and a lot more closer to regular social media. just better in general.
and ipfs problematic when you share something alone from your own node, it takes a long while for others to discover it. but sometimes it also works fast, just like that.
i think one problem with nostr right now is all media is just http links to a cdn.
they are not distributed, and link have nothing to do with the content, makes it impossible to verify. so i think sharing a hash instead of some random centralized id makes more sense. and we already have ipfs hash and uri. so if we shared ipfs uri instead of http url i think it would just work.
like relay lists, we can also have ipfs api and gateway lists. clients can ask all of the gateways for the content until finding it at one. ipfs gateways allow HEAD requests, so you can know if the content exists and its size before fetching it.
you can easily backup/pin your own content on another gateway you pay for as well if you want to.
main thing is its hash based, and distributed.
right now if i post a media on primal, they will host it via their cdn, and all of the other nostr clients will fetch it from a url to that cdn. cdn can censor, remove the content, and in the future even cdn itself can shutdown. there is no way to access that content other than that cdn. but and ipfs uri is hash based, so anyone can host if for you. if the content is lost, you can verify it again once you find it, etc. primal can just host an ipfs gateway instead of a regular cdn.
i know not many clients support ipfs, or have a list of ipfs gateways to use. but what you can do is share an a gateway https url, and anyone can still parse, it and say that "its an ipfs url".
ipfs url formats are known, it can be in bafy subdomain type or bafy and Qm type with /ipfs/ pathname prefixes. you can extract the hash from there and try it on multiple gateways. and clients that doesn't support ipfs would still work, because its basically a https url to an ipfs gateway.
i plan on hosting one in the future for nostr, with my own client.
nomadshiba
npub1gk…sppqk
2025-03-31 06:15:00
in reply to nevent1q…yds8
Author Public Key
npub1gkp4cdh5rktehjqjnqc09awey4302dpadlka6mes4fu5spes7fhqfsppqkPublished at
2025-03-31 06:15:00Event JSON
{
"id": "acf4e8bac971c0adb0de30f8f7c7593c9b18a2066a2ea730ea825b160a37e6f3",
"pubkey": "45835c36f41d979bc8129830f2f5d92562f5343d6feddd6f30aa79480730f26e",
"created_at": 1743401700,
"kind": 1,
"tags": [
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"ws://192.168.18.7:7777"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64",
"https://theforest.nostr1.com/"
],
[
"e",
"00001c5acadc3c7d99890eaf01cf123dfb4cdf8d25aa09da2dc1ba4c3f8d9a56",
"ws://192.168.18.7:7777",
"reply",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"e",
"6515da2900d1cbff94d3b8989922a58a298873840466bdc4bb6cc39bed3647a1",
"https://theforest.nostr1.com/",
"root",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
]
],
"content": "there is a reddit and 4chan like social media protocol on ipfs, its a bit more wild west. it uses pubsubs. \n\nbut its nothing like nostr, nostr is more profile based, and a lot more closer to regular social media. just better in general.\n\nand ipfs problematic when you share something alone from your own node, it takes a long while for others to discover it. but sometimes it also works fast, just like that.\n\ni think one problem with nostr right now is all media is just http links to a cdn.\n\nthey are not distributed, and link have nothing to do with the content, makes it impossible to verify. so i think sharing a hash instead of some random centralized id makes more sense. and we already have ipfs hash and uri. so if we shared ipfs uri instead of http url i think it would just work.\n\nlike relay lists, we can also have ipfs api and gateway lists. clients can ask all of the gateways for the content until finding it at one. ipfs gateways allow HEAD requests, so you can know if the content exists and its size before fetching it.\n\nyou can easily backup/pin your own content on another gateway you pay for as well if you want to.\n\nmain thing is its hash based, and distributed.\n\nright now if i post a media on primal, they will host it via their cdn, and all of the other nostr clients will fetch it from a url to that cdn. cdn can censor, remove the content, and in the future even cdn itself can shutdown. there is no way to access that content other than that cdn. but and ipfs uri is hash based, so anyone can host if for you. if the content is lost, you can verify it again once you find it, etc. primal can just host an ipfs gateway instead of a regular cdn. \n\ni know not many clients support ipfs, or have a list of ipfs gateways to use. but what you can do is share an a gateway https url, and anyone can still parse, it and say that \"its an ipfs url\". \nipfs url formats are known, it can be in bafy subdomain type or bafy and Qm type with /ipfs/ pathname prefixes. you can extract the hash from there and try it on multiple gateways. and clients that doesn't support ipfs would still work, because its basically a https url to an ipfs gateway.\n\ni plan on hosting one in the future for nostr, with my own client. ",
"sig": "f24134d5241ecffab3b8ec5f7a23200809187218e1766b1140d9f97ff894b2b9d8f9187b33e7ea62cceb371d80ea64aa9e19fea9238c807967fb82538ce4b9d6"
}