Jump to content
  • Sign Up
×
×
  • Create New...

Recommended Posts

  • Diamond Member

This is the hidden content, please

What Meta should change about Threads, one year in

It’s been a year since Meta pushed out Threads in an attempt to take on the platform now known as X. At the time, Mark Zuckerberg said that he hoped it would turn into “a public conversations app with 1 billion+ people on it.”

Meta’s timing was good. Threads launched at a particularly chaotic moment for

This is the hidden content, please
, when many people were seeking out alternatives. Threads saw 30 million sign-ups in its first day and the app has since grown to
This is the hidden content, please
monthly users, according to Elon Musk.)

But the earliest iteration of Threads still felt a little bit broken. There was no web version, and a lot of . The company promised interoperability with ActivityPub, the open-source standard that powers Mastodon and other apps in the fediverse, but integration ******** .

One year later, it’s still not really clear what Threads is actually for. Its leader that “the goal isn’t to replace

This is the hidden content, please
” but to create a “public square” for
This is the hidden content, please
users and a “less ****** place for conversations.”But the service itself still has a number of issues that prevent it from realizing that vision. If Meta really wants to make that happen, here’s what it should change.

If you follow me on Threads, then you probably already know this is my top complaint. But Meta desperately needs to fix the algorithm that powers Threads’ default “For You” feed. The algorithmic feed, which is the default view in both the app and website, is painfully slow. It often surfaces days-old posts, even during major, newsworthy moments when many people are posting about the same topic.

It’s so bad it’s become a running meme to post something along the lines of “I can’t wait to read about this on my ‘For You’ feed tomorrow,” every time there’s a major news event or trending story.

The algorithmic feed is also downright bizarre. For a platform that was built off of

This is the hidden content, please
, an app that has extremely fine-tuned recommendations and more than a decade of data about the topics I’m interested in, Threads appears to use none of it. Instead, it has a strange preference for intense personal stories from accounts I’m entirely unconnected to.

In the last year, I’ve seen countless multi-part Threads posts from complete strangers detailing childhood ******, eating disorders, chronic illnesses, domestic *********, **** loss and other unimaginable horrors. These are not posts I’m seeking out by any means, yet Meta’s algorithm shoves them to the top of my feed.

I’ve aggressively used Threads’ swipe to try to rid my feed of excessive trauma dumping, and it’s helped to some extent. But it hasn’t improved the number of strange posts I see from completely random individuals. At this moment the top two posts in my feed are from an event planner offering to share wedding tips and a woman describing a phone call from her health insurance company. (Both posts are 12 hours old.) These types of posts have led to blogger Max Read dubbing Threads the “” because they make it feel as if everyone is “suffering some kind of minor brain damage.”

Look, I get why Meta has been cautious when it comes to content moderation on Threads. The company doesn’t exactly have a great track record on issues like extremism, health misinformation or genocide-inciting hate speech. It’s not surprising they would want to avoid similar headlines about Threads.

But if Meta wants Threads to be a “public square,” it can’t searches for topics like COVID-19 and vaccines just because they are “potentially sensitive.” (

This is the hidden content, please
head Adam Mosseri claimed this measure was “temporary” last October.) If Meta wants Threads to be a “public square,” it shouldn’t political content from users’ recommendations; and Threads’ leaders shouldn’t assume that users to see news.

A year in, it’s painfully clear that a platform like Threads is hamstrung without a proper direct messaging feature. For some reason, Threads’ leaders, especially Mosseri, have been adamantly opposed to creating a separate inbox for the app.

Instead, users hoping to privately connect with someone on Threads are forced to switch over to

This is the hidden content, please
and hope the person they are trying to reach accepts new message requests. There is an in-app way a Threads post to an
This is the hidden content, please
friend but this depends on you already being connected on
This is the hidden content, please
.

Exactly why Threads can’t have its own messaging feature isn’t exactly clear. Mosseri has suggested that it doesn’t make sense to build a new inbox for the app, but that ignores the fact that many people use

This is the hidden content, please
and Threads very differently. Which brings me to…

Meta that the reason why it was able to get Threads out the door so quickly was largely thanks to

This is the hidden content, please
. Threads was created using a lot of
This is the hidden content, please
’s code and infrastructure, which also helped the company get tens of millions of people to sign up for the app on

But continuing to require an

This is the hidden content, please
account to use Threads makes little sense a year on. For one, it shuts out a not-insignificant number of people who may be interested in Threads but don’t want to be on
This is the hidden content, please
,

There’s also the fact that the apps, though they share some design elements, are completely different kinds of services. And many people, myself included, use

This is the hidden content, please
and Threads very differently.

A “public square” platform like Threads works best for public-facing accounts where conversations can have maximum visibility. But most people I know use their

This is the hidden content, please
accounts for personal updates, like family photos. And while you can have different visibility settings for each app, you shouldn’t be forced to link the two accounts. This also means that if you want to use Threads anonymously, you would need to create an entirely new
This is the hidden content, please
account to serve as a login for the corresponding Threads account.

It seems that Meta is at least considering this. Mosseri said in with Platformer that the company is “working on things like Threads-only accounts” and wants the app to become “more independent.”

These aren’t the only factors that will determine whether Threads will be, as Zuckerberg has speculated, Meta’s next 1 billion-user app. Meta will, eventually, need to make money from the service, which is currently advertising-free. But before Meta’s multibillion-dollar ad machine can be pointed at Threads, the company will need to better explain who its newest app is actually for.




This is the hidden content, please

news, gear,
This is the hidden content, please
, meta, threads
#Meta #change #Threads #year

This is the hidden content, please

This is the hidden content, please

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Vote for the server

    To vote for this server you must login.

    Jim Carrey Flirting GIF

  • Recently Browsing   0 members

    • No registered users viewing this page.

Important Information

Privacy Notice: We utilize cookies to optimize your browsing experience and analyze website traffic. By consenting, you acknowledge and agree to our Cookie Policy, ensuring your privacy preferences are respected.