But the AT Protocol is open, isn’t it? Anyone can go ahead and create non proprietary software that lives on this protocol.
I understand your concerns regarding Bluesky specifically being proprietary, but as soon as someone creates an open source atproto server, you will be able to interact with Bluesky users without using proprietary software. It will require Bluesky to federate with instances using such software of course.
I agree that this would be a solution. Bluesky adding a bridge for ap would be 100.000 times easier though.
Why would anyone start anew? We have similar platforms already. One big downside is that someone buying into at protocol would need to start anew and bluesky is already so big that any instance needs to submit to their rule or wither.
Edit: any new instance would have to submit to their rule.
But the AT Protocol is open, isn’t it? Anyone can go ahead and create non proprietary software that lives on this protocol.
I understand your concerns regarding Bluesky specifically being proprietary, but as soon as someone creates an open source atproto server, you will be able to interact with Bluesky users without using proprietary software. It will require Bluesky to federate with instances using such software of course.
I agree that this would be a solution. Bluesky adding a bridge for ap would be 100.000 times easier though.
Why would anyone start anew? We have similar platforms already. One big downside is that someone buying into at protocol would need to start anew and bluesky is already so big that any instance needs to submit to their rule or wither.
Edit: any new instance would have to submit to their rule.