> what should happen?

A core principle of ATProto is that the cost of switching is low, thereby facilitating real competition on social media. So the answer is two parts

1. App views decide permission parameters for their modality and frame the user experience

2. Users use these permission parameters to dial in their personal or community experience

I believe there is more middle ground than you leave space for. See systems like ReBAC/Zanzibar, Anonymous Credentials, and UCANN. Google Workspace is a good model that many many people understand and are happy with (IAM wise).

With a design like this, you can build an enforceable world-read, mutual-following-write version of Bluesky, something users ask for every time Bluesky announces any new feature.

▲

fidotron an hour ago | parent [-]

> 1. App views decide permission parameters for their modality and frame the user experience

Yeah, so this is the problem. A system flexible enough for that will be some combination of centralized, hilariously over complicated, massively inefficient, and full of odd unexpected behaviors.

	▲	verdverm 41 minutes ago \| parent [-]
		Perhaps if you are after public square social media. If you are after small social media, the usage patterns and tradeoffs look different. Modded Minecraft (smp) servers are interesting prior art for me.