fiatjaf on Nostr: Why can't we just open one subscription to two or three relays of each followed ...
Why can't we just open one subscription to two or three relays of each followed person in order to build the default feed?
If that was possible that would make implementing "outbox" even easier than implementing a client that just uses a static set of relays. Caching notes from is easy, it's easy to continue fetching from where your cache ends. Relay selection is easy, no need to build complex filters aggregating multiple requests and do fancy relay selection based on whom you're following matches whom. Everything is just one loop.
Nostr is easy again, developers are happy. Even the dumbest web developer can do censorship-resistant Nostr clients for everything.
Published at
2025-04-04 21:11:34Event JSON
{
"id": "00001ad3a276414ce70204c4a98a5f1a666488c69b5e3002e803c70b84fe9479",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1743801094,
"kind": 1,
"tags": [
[
"nonce",
"9223372036854795635",
"16"
]
],
"content": "Why can't we just open one subscription to two or three relays of each followed person in order to build the default feed?\n\n\nIf that was possible that would make implementing \"outbox\" even easier than implementing a client that just uses a static set of relays. Caching notes from is easy, it's easy to continue fetching from where your cache ends. Relay selection is easy, no need to build complex filters aggregating multiple requests and do fancy relay selection based on whom you're following matches whom. Everything is just one loop.\n\n\nNostr is easy again, developers are happy. Even the dumbest web developer can do censorship-resistant Nostr clients for everything.",
"sig": "d541cc45bfc1631487b67ca878b95aedfd331faec82a3f9971c46de2db01c65a2bf3912f62497643de4dfbc59cf2e5ac355162e27aa05042e0c8f97e8d673585"
}
