I agreed with most of this until the end, the question is how often are you going to make a query to something that you haven't cached before. I call this the cold lookup.
And the answer to that is the vast majority of the time for two reasons;
1. There are more URLs on the Web and more endpoints than you can cache, and if you want to replace ICANN DNS, and not just contact list in a social app, then you should expect that most URLs are seen for the first time or it was evicted from your limited cache.
2. You want to support stateless clients, so caching at relays is much more reliable than expecting every client to start with it's own equivalent of host.txt of the entire web
Again, we already know what works for the general purpose, and it is not local host.txt.
But I am not saying you shouldn't use local caches if you can, you should, and Pkarr encourages that, but it is just one layer of caching, and without the falling back to the DHT, the UX really doesn't work, you can't take a step backwards from the status quo, especially when you are already asking users to do the hard thing of managing their own keys, you can't add to that URLs that have a 10% chance of working and "depends".
Nuh
npub1jv…s7yqz
2025-05-01 16:21:00
in reply to nevent1q…9tkq
Author Public Key
npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqzPublished at
2025-05-01 16:21:00Event JSON
{
"id": "95c05b03ea700c3348f47e7599890bcf9630203fe4edcc538b6ce4858f677bfb",
"pubkey": "930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9",
"created_at": 1746116460,
"kind": 1,
"tags": [
[
"p",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9",
"wss://ditto.pub/relay"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"wss://ditto.pub/relay"
],
[
"p",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
],
[
"p",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"wss://nos.lol"
],
[
"e",
"e75919dab725cede9cc345a88db21655c909986710f569bbdbe118c542eadef1",
"",
"reply",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
],
[
"e",
"e769553791abb162c0b686a03387c208e1927bea9053ae517bdd8e5eb6f8b2de",
"wss://nos.lol",
"root",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
]
],
"content": "I agreed with most of this until the end, the question is how often are you going to make a query to something that you haven't cached before. I call this the cold lookup.\n\nAnd the answer to that is the vast majority of the time for two reasons;\n1. There are more URLs on the Web and more endpoints than you can cache, and if you want to replace ICANN DNS, and not just contact list in a social app, then you should expect that most URLs are seen for the first time or it was evicted from your limited cache.\n2. You want to support stateless clients, so caching at relays is much more reliable than expecting every client to start with it's own equivalent of host.txt of the entire web \n\nAgain, we already know what works for the general purpose, and it is not local host.txt.\n\nBut I am not saying you shouldn't use local caches if you can, you should, and Pkarr encourages that, but it is just one layer of caching, and without the falling back to the DHT, the UX really doesn't work, you can't take a step backwards from the status quo, especially when you are already asking users to do the hard thing of managing their own keys, you can't add to that URLs that have a 10% chance of working and \"depends\".",
"sig": "551925f5b86c0005ae8504f09a18d57227ccb4236a5e06c5b437a670507917b59ec9f78e71edbbe7365ed2acadd967c0b21c5346d67aeae42b6cae7d3d071bd9"
}