Moving to: m/AskMbin!

19 readers

1 users here now

### We are moving! **Join us in our new journey as we take a new direction towards the future for this community at mbin, find our new community here and read this post to know more about why we are moving. Thank you and we hope to see you there!**

founded 1 year ago

With Meta exploring the fediverse, would it be possible to create a copy-left federation license to block for-profit entities from federating with a server? (kbin.social)

submitted 1 year ago by zalack@kbin.social to c/AskKbin@kbin.social

14 comments fedilink hide all child comments

I.E. a way to legally enforce that servers which federate with you are not allowed to serve ads alongside content from your server, and must be run by not-for-profit entities?

I'm curious about some sort of strategy that blocks Meta from extracting money from the content creators in the current fediverse by using legal licensing of some sort, similar to how the GPL software license requires any derivative software to be open source.

you are viewing a single comment's thread
view the rest of the comments

[–] cyberian_khatru@kbin.social 4 points 1 year ago (1 children)

they need us, not the other way around.

Yeah, until they get a foot on the door. A single foot of theirs is stronger than the whole fediverse. Google used the depend on the android open source project. Then AOSP depended on google. Then they started phasing out base apps like email, browser, gallery, sms/phone, calendar, file manager, music player, etc., in favor of proprietary google apps and made everything require google play services. Other vendors stopped using the AOSP apps as well, and made their own versions in response, up to and including entire app stores like samsung apps. Today most users only know the proprietary android experience, even the UI is proprietary (android ONE, pixel UI, MIUI, etc). Even open source enthusiasts have a hard time installing AOSP or a custom ROM because of hardware level locked bootloaders. Others have mentioned the embrace-extend-extinguish tactic and this is what it is.

[–] Blakerboy777@kbin.social 2 points 1 year ago (1 children)

@cyberian_khatru

@zalack @FreeBooteR69 google never "depended" on Android in any real sense. It was developed by a for profit entity that was bought by Google while it was still in its infancy and has always been wholly owned by Google since - the source code is open, but it wasn't a community project that Google EEE'd, it was a privately owned project that they've made all the investment in and done all the work on, except the apps themselves which they assert little to no control over. The same company literally EEE'd a chat protocol with Google Talk so this was just a really oddball example to pick.

[–] cyberian_khatru@kbin.social 3 points 1 year ago

I supposed I would make some mistake talking about xmpp since I never used it. Oh well, thanks for the clarification.