Technology

58173 readers

3047 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

136

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

submitted 8 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

[–] blue_berry@lemmy.ca 1 points 8 months ago* (last edited 8 months ago)

That's a good point. I could imagine Meta will try kind of a "franchising" of the Fediverse. With many little Threads-instances popping up that are not maintained by Meta itself but give it a fee for their software.

I think we should all be incredibly critical of any community and systems maintenance challenges in software released by meta, and be diligent about testing migrate-away scenarios. In fact, I would say that if they do release self hostable software, we make sure to port all the good features to FOSS software as quickly as possible.

Sounds like a good point although I'm not really in the opensource community to know how the dynamics are. Is it a threat scenario that is common and doesn't this already fall under EEE?