Will threads mainstream the fediverse? (threads.net)

submitted 1 year ago by stux@reddthat.com to c/fediverse@lemmy.world

27 comments fedilink hide all child comments

Within the first hour of threads going live, about a dozen of those im following on ig have joined (and began posting). When it's fully federated, could this be the entry level platform the fediverse needs to push it into average use? I have a slight feeling it’ll be a BeReal type scenario where people use it for a few months and then move on, but id be stoked to be able to have my friends and family see my posts on mastodon/lemmy.

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

[-] Mountaineer@lemmy.world 50 points 1 year ago

Threads will mainstream threads.
Any good content here will be available to the Threads users, who will be oblivious to where it is coming from.
Eventually, Meta will take steps to break compatability, and lots of the most prolific contributors from here will move to Threads exclusively (for a host of valid reasons).
When it is no longer in Meta interest to federate, they will stop.

The fediverse will continue, but it will be weakened by it's temporary reliance on Threads (who could afford to host large images/videos/etc, have lower latency, etc etc).

[-] tyfi@wirebase.org 10 points 1 year ago

Why would users from here migrate to Threads?

[-] Mountaineer@lemmy.world 19 points 1 year ago

Maybe the client is faster/prettier/can show videos/uses less data/integrates with their phone better.
Maybe it's got features that clients here lack such as the ability to host larger images or video.
Maybe the user is sick of responding to conversations over there and it not being federated, so they are ignored.
Maybe using the Threads app is just faster (because it's local instead of batch federating).

If I was in charge of product design for Threads, I would be literally crawling the issue listings for Lemmy/Kbin and the associated clients looking for complaints and implementing solutions for those problems.
Then I would make a list of every limitation within the system and make sure Threads exceeds that baseline.

And then when I had made the software better in every measurable way (because I am paying a large team of developers to target those pain points), I'd start adding features that ActivityPub doesn't, especially if ActivityPub instances would find those features hard to implement.

I'd make damn sure that every time ActivityPub changes from a source outside Meta, I'd drag my heels on implementing that feature, so that instance hosts are forced to choose between implementing the new version, or maintaining compatability with Threads.

Why would a user here move there?
Because their spouse/coworker/friend tried to send something for the 50th time and the message just never came through.