Greg on Nostr: An idea to make Nostr relays more realistically scale to the size of Twitter: - ...
An idea to make Nostr relays more realistically scale to the size of Twitter:
- Define a minimum period for a post to gain traction. This is the minimum amount of time that a post would typically take to be seen, go viral, etc.
- If this time passes and the post sees little interaction, then…
- Define a minimum interaction threshold for a post to remain on the network. In other words, how many people have to click/like/comment per hour/day for this post to stay on the network?
This should be technically possible as well. I’m not sure if this is the case with Nostr relays, but at least in the case of IPFS: posts are “content-addressable” and not “location-addressable”.
When I want to find a post I don’t say “go to this DNS address to find the post”. Instead I say “this is the hash of the post I’d like to see”, and ask the network if anyone has this post. This to my understanding is the way that BitTorrent works.
If the post is hosted across multiple relays, each relay can announce to the network the amount of traffic they saw to the post. In this way, the entire network should have a global understanding of how much interaction a post is seeing.
This would offer an alternative to just “delete a post after 30 days”. Because here we can actually delete posts maybe earlier than this deadline to save space for posts that never gained traction, and also save posts for users who still show a high demand for this content.
Published at
2024-08-27 03:55:39Event JSON
{
"id": "cc21b87e02a3f24d518e2718d8e7ada3e78c15aa9f28b133742bf992e32e2d5e",
"pubkey": "b16063c3d74ecdbe49cbe2fea2557296b82f5463375d095e2ddcebb272eab998",
"created_at": 1724730939,
"kind": 1,
"tags": [],
"content": "An idea to make Nostr relays more realistically scale to the size of Twitter:\n\n- Define a minimum period for a post to gain traction. This is the minimum amount of time that a post would typically take to be seen, go viral, etc. \n- If this time passes and the post sees little interaction, then…\n- Define a minimum interaction threshold for a post to remain on the network. In other words, how many people have to click/like/comment per hour/day for this post to stay on the network?\n\nThis should be technically possible as well. I’m not sure if this is the case with Nostr relays, but at least in the case of IPFS: posts are “content-addressable” and not “location-addressable”. \n\nWhen I want to find a post I don’t say “go to this DNS address to find the post”. Instead I say “this is the hash of the post I’d like to see”, and ask the network if anyone has this post. This to my understanding is the way that BitTorrent works.\n\nIf the post is hosted across multiple relays, each relay can announce to the network the amount of traffic they saw to the post. In this way, the entire network should have a global understanding of how much interaction a post is seeing. \n\nThis would offer an alternative to just “delete a post after 30 days”. Because here we can actually delete posts maybe earlier than this deadline to save space for posts that never gained traction, and also save posts for users who still show a high demand for this content.",
"sig": "93a67dcad7d177a933ca0f09e18b96ea83be1ce64b377a8a3cee97f381fa5fd7f6ca52f918dd6d6670f379d601bff887d459ab9344f2baa02b3b841cf75c4334"
}