alt Hacker News> tangled will struggle to have private repos that align with user expectations for RBAC, atproto ACL permission proposal is insufficient, Bluesky is not interested in alternative proposals, the centralization of atproto is most prominant in who has write permissions to the repos
This isn't entirely true because we're working on our own extensions to the protocol that will enable full-fledged RBAC at a knot/repo level. We're not beholden to PBC and AT Protocol; when needed, we're OK to roll custom bits.
> we're working on our own extensions to the protocol
what I hear is another path to app centralization, regardless of your intent, this is what comes out of custom extensions to a protocol
bluesky should have actually been open about the permissioned design process, posting your own proposal to a blog and not entertaining other proposals, or even joining the broader conversation that was happening, is not open in my book