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
I am just thinking you do not like tangled because you don't use the social features of github and so don't see the point here. I can understand that, but then tangled is just not for you ?
And yeah ATProto is not the next thing, but IMO having a portable identity and services that can act as "one big single app" are requirements for a modern social protocol to do applications like Twitter,Instagram, and github's social features for example, ATProto is just the one that does it better imo for now.
But again since you are always bringing on private repos, I think tangled is just not for you since the ATProto model is for open data and so fits open source projects really nicely I think.
you are incorrect and this is why it's advised not to project the answer but ask a question instead
for clarity, I do in fact use github's social features
I also believe that the idea around the atmosphere that the point of atproto is to have open data is completely misaligned with how most of society wants their data handled, this is based on my talking to people IRL, outside of the echo chambers of social media, what's actually happening is more and more people signing off because of toxicity
open source and small devs do not pay the bills, github is financially sustainable because they have enterprise clients, same for gitlab and bitbucket
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.
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