// Adds dimensions UUID, Author and Topic into GA4
Sunday, March 15, 2026
27.6 C
Singapore

Threads: No unique identity on social media?

In a bold move to rival Twitter (now X), Meta launched Threads; however, the promising start has quickly fizzled out, with Threads witnessing a worrying decline in traffic and showing no apparent signs of a turnaround due to not having a unique identity on social media.

Bleak picture on social media

A recent report published on Tuesday paints a bleak picture for the once-hyped platform, predicting that Threads will close in 2023 with just 23.7 million users in the United States.

This figure stands at less than half of the 56.1 million anticipated for Twitter/X and a mere 17.5% of Instagram’s staggering 135.2 million user base.

Threads’ current trajectory places it second-to-last among major social media platforms, edging out only Tumblr, which boasts 20.4 million users.

In stark contrast, Facebook continues to reign supreme as the most popular social network, with a staggering 177.9 million users in the United States, followed closely by Instagram and TikTok, with 102.3 million users.

See also  Popular influencer with over 100 sponsorships, not a real person

Even as Threads’ user base is projected to grow to 33.9 million by 2025, accounting for 23.3% of Instagram’s total users, experts at Insider anticipate that the platform’s cellar-dwelling ranking will persist.

Jasmine Enberg, principal analyst at Insider, underscores the challenges facing Threads, stating, “The path to 1 billion Threads users is longer than Meta would like. The link to Instagram can only take Threads so far, and the clock is ticking for the network effect to take hold.”

Curiously, the report omits two other Twitter alternatives, Mastodon and Bluesky.

Despite having smaller user bases than Threads, these platforms offer a unique proposition to users weary of being subject to the whims of billionaire platform owners: decentralized protocols that empower individuals to take their online presence elsewhere.

Meta has hinted at Threads adopting Mastodon’s ActivityPub protocol in the future, but for now, Threads resembles a version of Twitter without the occasional controversial posts from high-profile figures.

See also  "Maradona's sweat still sticking to the ball" — Netizens react to Maradona's "Hand of God" ball auctioned for S$3.27M

No unique identity?

Enberg emphasizes Threads’ need to define its identity quickly, stating, “For Threads to carve a lasting niche in the social media landscape, it needs to determine its unique identity as it matures. It must also do so promptly, as Meta has a history of discontinuing new apps or integrating them into existing services.”

The clock is ticking for Threads, and its future in the competitive social media sphere hangs in the balance.

Read More News

Government Shutdown: Congress braces for showdown

The photo above is from Pexels

The post Threads: No unique identity on social media? appeared first on The Independent News.

- Advertisement -

Hot this week

Seating dispute at Jurong West food shop turns violent; man slaps worker

A dispute allegedly arose over seating arrangements. A male customer slapped a female employee at a food stall, who retaliated by throwing a chair and then hitting him with a basket full of spoons ...

Wife says husband dismisses her feelings and makes her feel like a stranger around his family

SINGAPORE: A wife took to social media to share that she feels utterly alone in her marriage because her husband constantly dismisses her concerns and makes her feel like a stranger around his fami...

Popular Categories

document.addEventListener("DOMContentLoaded", () => { const trigger = document.getElementById("ads-trigger"); if ('IntersectionObserver' in window && trigger) { const observer = new IntersectionObserver((entries, observer) => { entries.forEach(entry => { if (entry.isIntersecting) { lazyLoader(); // You should define lazyLoader() elsewhere or inline here observer.unobserve(entry.target); // Run once } }); }, { rootMargin: '800px', threshold: 0.1 }); observer.observe(trigger); } else { // Fallback setTimeout(lazyLoader, 3000); } });
// //