Edmund Edgar (goat/acc) pfp
Edmund Edgar (goat/acc)
@edmundedgar.eth
What Bsky is doing here seems good to me, since have to follow laws: 1) Blocking is client-side only, Turkish users can use a different client and see the blocked posts 2) Blocked content is public, we can see what's blocked https://pdsls.dev/at://did:plc:cquoj7aozvmkud2gifeinkda/labels?uriPatterns=*
2 replies
2 recasts
8 reactions

Emre Ekinci pfp
Emre Ekinci
@emr.eth
Could one use the bsky social graph (where people signup) but have them submit posts via nostr (uncensorable) for a 🇹🇷 client?
1 reply
0 recast
1 reaction

Edmund Edgar (goat/acc) pfp
Edmund Edgar (goat/acc)
@edmundedgar.eth
You could link the two somehow but this is a case where nostr has the exact same problem as bsky: If the client you're using censors someone, you have to switch to a different client to see their posts. 1/2
2 replies
0 recast
0 reaction

Edmund Edgar (goat/acc) pfp
Edmund Edgar (goat/acc)
@edmundedgar.eth
The part where bsky has centralization and bsky doesn't is in the social graph, bsky allows key rotation in a way that involves a centralized repo. The nostr solution is not to have key rotation and try really hard not to lose your key 2/2
1 reply
0 recast
0 reaction

Emre Ekinci pfp
Emre Ekinci
@emr.eth
This is where I got the idea from. But then you can create a uncensored client on atproto with a pds?
1 reply
0 recast
0 reaction

Edmund Edgar (goat/acc) pfp
Edmund Edgar (goat/acc)
@edmundedgar.eth
I can't see that thread so I don't know what aspect they think would be better in nostr here. The PDS model is you can host content anywhere, and all clients can pull from it. Since the blocking here is just a client setting, the fix is just to use a different client, you don't need to do anything special with a PDS
1 reply
0 recast
1 reaction