this post was submitted on 10 Jul 2023
221 points (100.0% liked)

Technology

37720 readers
384 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
coldredlight@beehaw.org
Los@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
221
Twitter traffic is 'tanking' as Meta's Threads hits 100 million users (www.cnbc.com)
submitted 1 year ago by trashhalo@beehaw.org to c/technology@beehaw.org
89 comments fedilink hide all child comments
 

Meta's new text-based social app Threads has quickly gained 100 million users since launching last week, which appears to be negatively impacting traffic on Twitter. According to web analytics, Twitter traffic declined 5-11% over the first two days Threads was available compared to the previous week. Threads was able to grow rapidly by allowing users to sign up with their existing Instagram accounts and bring over some of their followers. However, Threads has not yet launched in Europe due to regulatory issues. The fast growth of Threads may solidify its position as a real competitor to Twitter, which has over 238 million daily active users.

you are viewing a single comment's thread
view the rest of the comments
[–] pvr@beehaw.org 5 points 1 year ago

Your first point is an "initial limitation".

Your second point:" This is presumably due to most fediverse services not yet supporting reply restrictions."

Not sure why you are using select quotes without giving the full context to make a point that is actually not there.