jeremy on Nostr: In centralized systems (twitter, hosted email), you can be more protected from ...
In centralized systems (twitter, hosted email), you can be more protected from anonymous third-parties triggering a fetch to get that data. The provider has the info, but you're trusting them with it anyway.
There's not an easy solution in decentralized systems like Nostr. You could whitelist trusted image serving domains (e.g. nostr.build). Or have trusted image proxies--perhaps relays could even offer this.
Published at
2023-01-10 13:37:53Event JSON
{
"id": "14deb0d5769a270e0954c4185fb8d9ace9aa7581d9f595f2e806b67ee7763c0a",
"pubkey": "b8f0f79c1688d8bcf16f333a2c5617a2c3935469cbbd4ece398856b1a3f7eee0",
"created_at": 1673357873,
"kind": 1,
"tags": [
[
"e",
"73388ffd6d5f7ef4d473057e8358ac525f31bb69223b19b9f6b8953e3ac87764",
"wss://relay.damus.io",
"root"
],
[
"e",
"85c2fc4fe505418c04fe28cbf3f6688eee2ba6f1bcd824d688bc1c6a60c5a295",
"wss://nostr.oxtr.dev",
"reply"
]
],
"content": "In centralized systems (twitter, hosted email), you can be more protected from anonymous third-parties triggering a fetch to get that data. The provider has the info, but you're trusting them with it anyway.\n\nThere's not an easy solution in decentralized systems like Nostr. You could whitelist trusted image serving domains (e.g. nostr.build). Or have trusted image proxies--perhaps relays could even offer this.",
"sig": "abbc932404a0832840f1cbeece179784dbb458fa02fac524a4a5b2a5f0773470240f739c3ba642d012a4dd37025d414b14c30903b2bde9c4628a4bb43377147d"
}
