richard on Nostr: there are currently so many factors that make this whole process near impossible to ...
there are currently so many factors that make this whole process near impossible to achieve:
- it's not only about trust in relays, but also trust in end users as they could re-broadcast what they see.
- clients have default big pre-defined relays
users are told they "own" their data which is kind of true only under very specific conditions
among other major onboarding issues, nostr is advertised with crazy statements: "you own your data" but as many others also mentioned before, data ownership is not real, it has never been.
and you can't ever have true control over where your data is going. for this to be real, each user would have their own household relay, all clients would use outbox model and, even then, it would only work for protected events while also hoping your posts don't end up broadcasted to relays that don't care about nip-70.
this makes me think there could be data crawlers all over nostr that will find your data and possibly just sell it.
PoW and paid relays are solutions yet to be, for the former, deployed on more clients, and for the latter, accepted by people (no one wants to pay)
- there's basically no information on the biggest relays rn and who owns them as far as i know
what relays to use in order to have the broadest view possible or to help with discoverability? nostr.wine looks okay... but what else is there?
if your client doesn't use the outbox model, setting main big relays is the only way for you to discover new content.
at this point i have accepted that anything posted on nostr is automatically freely accessible to everyone on earth by default. and we should expect all the companies in the world to track everyone's data. the censorship-resistant aspect is real though.
Published at
2025-04-15 00:23:25Event JSON
{
"id": "e4514ff51ab94b095220fdbfde1eda67adafc9c9075b79799c4975757e0c459f",
"pubkey": "f946f6aa7a0afe2c243fdc3ff7f6c7402f349d84bb3dd2e95ac6e39ba0b20c1a",
"created_at": 1744676605,
"kind": 1,
"tags": [
[
"e",
"bf58399e31f680b920730ea22c55c0cde45f2bf1936a5938944697b9c51aaa38",
"",
"root"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"r",
"nostr.wine"
]
],
"content": "there are currently so many factors that make this whole process near impossible to achieve:\n\n- it's not only about trust in relays, but also trust in end users as they could re-broadcast what they see.\n\n- clients have default big pre-defined relays\n\nusers are told they \"own\" their data which is kind of true only under very specific conditions\n\namong other major onboarding issues, nostr is advertised with crazy statements: \"you own your data\" but as many others also mentioned before, data ownership is not real, it has never been.\nand you can't ever have true control over where your data is going. for this to be real, each user would have their own household relay, all clients would use outbox model and, even then, it would only work for protected events while also hoping your posts don't end up broadcasted to relays that don't care about nip-70.\n\nthis makes me think there could be data crawlers all over nostr that will find your data and possibly just sell it. \n\nPoW and paid relays are solutions yet to be, for the former, deployed on more clients, and for the latter, accepted by people (no one wants to pay)\n\n- there's basically no information on the biggest relays rn and who owns them as far as i know\n\nwhat relays to use in order to have the broadest view possible or to help with discoverability? nostr.wine looks okay... but what else is there?\nif your client doesn't use the outbox model, setting main big relays is the only way for you to discover new content.\n\nat this point i have accepted that anything posted on nostr is automatically freely accessible to everyone on earth by default. and we should expect all the companies in the world to track everyone's data. the censorship-resistant aspect is real though.",
"sig": "8cc1cf4ee7d93a14df2375e2c3e2e09f89f59807e363d990b5e26e9ef73472cd378d26143535bf4f0e832e033bb2ce3fa66d00441e48e5bff8ea6584d740a617"
}