147

Embrace, Extend, Enforce (ƎƎƎ): A practical Strategy against potentially abusive Instances like Meta’s Threads (fungiverse.wordpress.com)

submitted 10 months ago by blue_berry@lemmy.ca to c/technology@lemmy.world

17 comments fedilink hide all child comments

cross-posted from: https://lemmy.ca/post/12225995

cross-posted from: https://lemmy.ca/post/12225991

TL;DR: The common view on Meta’s Threads is that it will be either all good or all bad, leading to oversimplified and at the end contra productive propositions like the Fedipact. But in reality, it’s behaviour will most likely change dynamically over time, and therefore, to prevent us getting in a position, in which Threads can actually perform EEE on us, we need to adapt a dynamic strategy as well.

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

[-] farcaller@fstab.sh 43 points 10 months ago

However, XAMPP didn’t just die because it opened itself up to Microsoft and got extinguished

So, we went from the somewhat imaginary “google killed xmpp” to fully fictional “Microsoft killed xampp” now? it's almost like the fedipact people literally have no clue what they are talking about.

[-] qjkxbmwvz@lemmy.sdf.org 17 points 10 months ago

Yeah all the EEE/"Threads will kill us" talk reminds me of how Slack killed IRC by first offering an IRC gateway, and then killing off support. And after that IRC literally died.

I saw a post here about how Threads' biggest enemy at this point is antitrust, and a federated approach is a clever way around that. I think that makes much more sense than the EEE narrative.

[-] umbrella@lemmy.ml 5 points 10 months ago* (last edited 10 months ago)

Zucc is using us to skirt regulations

Yeah, that aint any better. Defederate and let them die.

[-] Adanisi@lemmy.zip 9 points 10 months ago* (last edited 10 months ago)

Who was this article written by?

This excerpt seems like pure misunderstanding in communication, or a typo.

None of us are actually claiming ridiculous things like "Microsoft killed XAMPP". It's obvious that this is a communication error or typo (see: similarity in spelling of XAMPP and XMPP)

[-] blue_berry@lemmy.ca 1 points 10 months ago

Yeah sorry. That was a mistake but I changed it now :)

this post was submitted on 29 Dec 2023

147 points (90.6% liked)

Technology

59381 readers

1004 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS