this post was submitted on 23 Jun 2023
623 points (100.0% liked)
Technology
37608 readers
218 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.
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)