334
submitted 7 months ago by deadsuperhero@lemmy.ml to c/fediverse@lemmy.ml

Server indexes of places for newcomers to join can be instrumental for Fediverse adoption. However, sudden rule changes can leave some admins feeling pressure to change policies in order to remain listed.

you are viewing a single comment's thread
view the rest of the comments
[-] qjkxbmwvz@startrek.website 5 points 7 months ago

I agree.

I think a good example is how Slack started off by having good IRC integration, then slowly added features which were incompatible with IRC, and finally terminated IRC integration.

So clearly, Slack killed IRC, right? (...of course they didn't!)

I see the potential situation with Threads as similar.

[-] niartenyaw@midwest.social 3 points 7 months ago

the problem occurs when most of the content comes from Meta (they will likely have the vast majority of Fediverse users). especially if major communities exist on their instance. when meta decides to no longer support fedi integration, those in the fedi are forced to decide between staying with their communities by ditching the fedi and moving to threads or having many of their communities ripped away.

meta will do this at some point as a play to draw users to them, but we can decide if we want to be affected when that comes to pass.

this post was submitted on 30 Mar 2024
334 points (96.1% liked)

Fediverse

17698 readers
2 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS