Yeah, it’s the same way that nothing is stopping you from creating your own internet with all the same protocols that is completely separate from the world wide web or whatever you want to call the “real” internet.
It sure is suspicious how meta bothers to do the NDAed meetings though. If all they wanted was to build a product from scratch, they wouldn’t have had to ask.
Right yeah, understandable. That’s more about people running instances saying that they won’t federate with Meta, ie. they won’t connect to Meta’s ActivityPub service (and won’t allow it vice versa, naturally)
I mean, it’s a protocol. Nobody needs to “allow” you to use it any more than HTTP; Meta can set up a service and they’re good to go.
Whether others will want to federate with them is the question.
Yeah, it’s the same way that nothing is stopping you from creating your own internet with all the same protocols that is completely separate from the world wide web or whatever you want to call the “real” internet.
It sure is suspicious how meta bothers to do the NDAed meetings though. If all they wanted was to build a product from scratch, they wouldn’t have had to ask.
Yea, they’re afraid of potential backlash and wanted to float ideas in a safe space.
Yes, I see it the same way. probably I misinterpreted the “block” language.
Right yeah, understandable. That’s more about people running instances saying that they won’t federate with Meta, ie. they won’t connect to Meta’s ActivityPub service (and won’t allow it vice versa, naturally)