this post was submitted on 19 Dec 2023
1134 points (91.5% liked)

Technology

60052 readers
3608 users here now

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


Our Rules


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

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 209 points 1 year ago* (last edited 1 year ago) (163 children)

Dumb. Federation is how we escape from every cloud-based service being a dictatorship of the person who owns the platform. That includes federating with privately own orgs to provide them an exit.

By all means make good tools to allow individual users to block Threads (or other private instances ruled by amoral coporations), but doing it at instance level is just dumb.

edit: also, number of instances doesn't matter. Number of daily active users matters. Most users are on mastodon.social, mastodon.cloud, lemmy.world, hachyderm.io, lemmy.world, etc. And all of those are federating. The only large instance that is not federating with threads is mas.to

[–] [email protected] 30 points 1 year ago (1 children)

If you federate with something too massive though it has undue weight on the entire system. It is likely to be Embrace, Extend, Extinguish again, and it's reasonable to want to avoid that.

For people who don't remember, the pattern would be something like:

  1. Federate and use the existing ecosystem to help you grow and to grow mutually (Embrace)
  2. Add new features that only work locally, drawing users away from other instances to your own (Extend)
  3. Defederate - the remainder is left with a fraction of the users since many moved away, so the users on the local instance don't care. (Extinguish)

It depends whether 2 actually succeeds at pulling users in. Arguably most people already on the Fediverse are unlikely to jump ship to Facebook, but you have to consider what happens in a few years if it's grown, but Facebook is a huge name which makes people less likely to join other instances.

[–] [email protected] 6 points 1 year ago

Personally, it's the implausibility of 2 that makes all of this seem like no big deal to me. In fact, I think federating openly with Threads might signal to Threads users that they can use alternatives and not lose access to whomever they follow on Threads, thus growing the user-base of other federated instances.

I think people who are going to use Threads for Meta-specific features are likely going to use Threads anyway, and if any of those features are genuinely good (i.e. not simply Instagram and Facebook tie-ins) they will be replicated by the various open Fediverse projects which already differ from one another in terms of features.

The moderation issue is entirely different and there are some instances that have an understanding with their users about protecting them from seeing any objectionable content or behavior as defined by whatever culture they have. Defederating from such a large group of people makes sense, perhaps even preemptively, no different from when they defederate existing large instances now.

load more comments (161 replies)