[sbt]

Disclaimer: I have not looked carefully at the permissioned data proposal, but I know atproto reasonably well.

Stepping back for a momement, it's clear that permissioned data is driven by real world use-cases (Bluesky needs DMs, Tangled needs private repos, etc). However, I think the synergies with the existing atproto needs to be pretty significant to warrant developing yet another encrypted space spec. We already have various double ratchet protocols, Matrix is having a huge boom. From the point of view of an app developer, does everything need to be handled by atproto, or could we accept that atproto is just for the public stuff?

[LelouBil]

I would prefer this to be more geared towards things like Private social profiles or shared with specific circles than DMs, which are already served by E2EE.

There's no issue in using ATProto to "link" an external service, like Tangled does with it's "knots" which host the git data.

All of the social stuff (issues, PRs, comments and so on) is on ATProto, and on ATProto you also have a "repository" object, linking to a "knot" object containing the address of the knot.

What's stopping an E2EE DM implementation to use ATProto to point to something like an "accepted matrix server" for all parties, and each having a "matrix identity" ATProto record ? (I don't know about Matrix so idk if this is exactly possible but you get the idea)