this post was submitted on 19 Jun 2023
227 points (100.0% liked)
Technology
37804 readers
215 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
What license is it open sourced under? I think AGPL (or one of the GPLs) would be the only one that could sorta force that issue.
The community would have to enforce the rules of the license. It wouldn't stop them from attempting to commercialize but the code would all have to be 100% free and public. All of it. Free to review, change, copy, etc.
I still see three possible ways for Embrace, Extend, Extinguish.
The first is the Android way: while Android is FLOSS on paper, Google makes sure to cram as much important functionality as possible into their proprietary and closed Play Services blob. I have no intimate knowledge of ActivityPub, but I reckon it would be relatively easy to contribute a tailored modules wrapper under any required GPL licence, and then use that wrapper as a gateway to closed-source extensions.
The second is the Gmail way as described by Emi here: build a portal based on established standards that becomes hugely popular because of its ease of use and feature set, then start sneaking in cool non-standard features that only work inside your walled garden.
The third is the Microsoft Java way: build your closed-source clone from scratch and make it just incompatible enough for non-technical users to think that the original implementation is broken.
There's also nothing stopping Facebook or anybody else from just making their own clone of the software without copyright issues. If it talks the protocol the same way it will work.