Threads logo with transparent ghost and 24-hour countdown timer

Threads Just Launched Posts That Vanish After 24 Hours

Meta’s trying something new with Threads. The company just rolled out “ghost posts” that disappear after one day.

These aren’t your typical temporary posts, though. Sure, they vanish after 24 hours like Instagram Stories. But the way people interact with them is completely different. And that could make them way more useful than similar features that flopped on other platforms.

How Ghost Posts Actually Work

Ghost posts appear in your main Threads feed like normal posts. Nothing looks different at first glance. But once 24 hours pass, they’re gone forever.

Here’s where it gets interesting. You can still like and reply to ghost posts. However, only the original poster sees those interactions. Everyone else? They can’t view the likes or replies at all.

Ghost posts disappear after 24 hours like Instagram Stories

Plus, replies don’t work like regular Threads comments. Instead, they route directly to your inbox as private messages. So a ghost post creates a one-to-many conversation that becomes many private one-on-one chats.

That means your replies are limited by Threads’ default messaging settings. Most users can only receive DMs from people they follow. So if you want to reply to a ghost post from someone who doesn’t follow you back, you might be out of luck unless they’ve changed their privacy settings.

Why Meta Thinks You’ll Use This

Meta’s pitch is simple. Ghost posts let you share “unfiltered thoughts and fresh takes without the pressure of permanence or polish.”

Translation? They want you to post more casual, off-the-cuff content. The kind of stuff you might normally skip because it doesn’t feel polished enough for your permanent feed.

That makes sense when you look at Instagram. Stories completely dominate grid posts there. People share way more when they know the content won’t live on their profile forever. So Meta’s betting the same psychology will work on Threads.

Ghost posts appear in main Threads feed then vanish after 24 hours

But here’s the thing. Ephemeral features have a rough history on text platforms.

Remember When Twitter Tried This?

Twitter launched Fleets in 2020. The feature worked almost exactly like Instagram Stories, but for text and tweets.

It bombed spectacularly. Former CEO Jack Dorsey reportedly “grew to despise” Fleets. Twitter killed the feature less than a year after launch. Users just didn’t care about temporary tweets the way they cared about temporary photos and videos.

So why would ghost posts succeed where Fleets failed? Maybe they won’t. Or maybe the private reply system makes them different enough to find an audience.

Replies route directly to inbox as private messages creating one-on-one chats

The privacy angle could actually work. Some people might feel more comfortable sharing casual thoughts if they know replies won’t turn into public dogpiles. And the 24-hour limit removes the anxiety of permanent posting without forcing content into a separate feed like Stories do.

The Real Question Nobody’s Asking

Will ghost posts get buried by Threads’ algorithm, or will Meta boost them to encourage adoption?

That’s the make-or-break factor here. If ghost posts get the same algorithmic treatment as regular posts, they’ll probably flop. Users won’t see enough of them to build the habit. But if Meta artificially promotes ghost posts in your feed, regular posters might get annoyed by the favoritism.

Meta hasn’t said anything about algorithmic treatment yet. But watch your Threads feed over the next few weeks. If you suddenly see tons of ghost posts from accounts you barely interact with, you’ll know Meta’s putting its thumb on the scale.

Ghost posts could fill a genuine gap in Threads. Or they could become another forgotten feature that nobody uses. Either way, they’re rolling out now. So you’ll find out soon whether your friends actually want to share their unfiltered thoughts with you.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *