110
This is FUD, slow down take a deep breath and just give it time.
Giving them time is exactly my problem. That's exactly embrace extend extinguish works.
They start by embracing it. "We created our own fediverse instance isn't this a cool thing, come on over to our server you can see other servers and leave anytime."
Then they extend it. "We added a colorful widget, only available on threads!"
Then when they feel they've got enough of the core users, they extinguish it. "If you want to see threads content you need a Facebook account, sorry just to meant be features to stay federated."
Look at what Google did to RCS for a real world example.
If you're truly worried about federating with Meta, you should probably also avoid all the other products they have their fingers in.
This includes all their web properties:
- Onavo
- Oculus VR
- Beat Games
- Kustomer
- Lofelt
But this also includes many web technologies that are ubiquitous around the web. Meta has either created or contributes code and resources to:
- React.js
- MySql
- Memcached
- HHVM
- Cassandra
- Scribe
- Hadoop
- Hive
- Apache Thrift
- Varnish
I suspect you'll have a hard time finding any website on earth that doesn't use at least one of these technologies.
load more comments
(8 replies)
Probably an unpopular opinion but I'd rather defederation be left to the users. I don't want to see content from Meta, but I want the ability to make that decision myself.
load more comments
(1 replies)
this post was submitted on 06 Jul 2023
110 points (100.0% liked)
/kbin meta
2 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 2 years ago