(Threads now has a fixed 15 minutes delay before they federate a post)

Are they already trying to enshittify the Fediverse experience with this delay?

Sounds like simply shitty programming if they need a 15 minutes delay in order to give users the possibility to edit their posts .. editing posts is possible in lots of fediverse software without such hacks lol
- Sounds like EEE to me, but it seems a little too early in the cycle for that.
- But it's cooperative, as long there is 1 instance that doesn't respect delete requests, they can't provide the ability to delete a mistakenly posted picture that actually works.
  
  15 minutes is excessive though. 3 minutes should be enough.
Agree it's a bit sus. They could just send out the updated version if it gets edited within their 15 minute window.

I can’t say I’ve ever seen one.

Maybe the majority of fediverse instances should just defederate from Threads. Then they can take all the time they want to broadcast their shitty posts.

https://fedipact.veganism.social/

Lemmy.world is one of the few still federated

I can see why they'd do that tbh. Being able to delete something posted in error is something that may not be guaranteed in the Fediverse. Once it's out there, you're relying on others to delete that cute picture of your cat with your shrivelled up little winkie clearly visible in the reflection of your TV.

Let’s not kid ourselves about threads properly deleting posts though. Their database probably just goes DELETED: True;
- So do most of mine. Makes maintaining data integrity a lot simpler and it's how my database replication tools work.
  
  GDPR was the only time I bothered to delete the data, and even then it was me setting the content of the records to "Information removed due to GDPR".
  
  Being able to undelete data is a powerful customer service tool, and when Grandma's Facebook account gets hacked (because her password is one of her grandkid's names), and all the photos get nuked (and being grandma, Facebook is their photo backup solution), they're probably going to want that all that restoring again.
  
  But then if data privacy was important to you, you wouldn't have put it on Threads.
It might just be the cynic in me but let’s be honest my cynical side is right %99.999… of the time and the rest of me is a vestigial organ held on by foolish optimism buuuuut I feel it’s to get all the benefits without giving back, the vast majority of all traction on a post is in the first few minutes and you cant comment on a post in real time unless you join their proprietary walled garden, it’s like free advertising, see a post you like in the fediverse? Oh no it’s already old and people have already made the top comments I guess I have to go to their app.

Apparently they either don't realize that there is a Update mechanism in ActivityPub that allows you to edit your post any time, or this is a temporary measure until they implement it.

a fixed 15-minute* delay

I'm not a native speaker.. interesting, why would that be phrased that way? It's still multiple minutes?
- Generally, when describing a thing, the unit is written as singular. "15 minute delay", "10 foot pole", "5 gallon bucket". When referring the unit itself though, it would be plural: "a delay of 15 minutes", "the pole is 10 feet long", "this bucket holds 5 gallons". I'm sure there's a more precise way to say this, but hopefully it helps.
- The delay is singular. So one delay for fifteen minutes is a fifteen minute delay.

It's nothing like 15 minutes, but Lemmy doesn't federate posts instantly either. At a guess, there's a per-remote-instance worker that sleeps for a bit, then sends everything that's accumulated while it was sleeping. It's most noticeable when you're linked to only one other instance, and you still have to wait before getting anything. The advantages are that it's better to open a network connection, send a bunch of stuff, then close it, rather than opening and closing it for every activity, and it's more efficient to just send an Edit, rather than a Create and then an Edit if they both occurred close to one another.

For Threads, there's the additional advantage in that it means they can offer the equivalent of 'undo send' (like in Gmail), since deleting a non-federated post is easier and more reliable than deleting a federated one. But 15 minutes is crazy high - like the Source says, it makes a nonsense out of trying to do things like comment on a live event.

(In contrast to the above, PieFed will send this Note out instantly. It's all a trade-off between the pros and cons of different approaches, innit)

@Andrew

t's nothing like 15 minutes, but Lemmy doesn't federate posts instantly either.

And for Hubzilla, it depends on the outgoing queue. It can range from instant to awhile.

But we can edit and delete our posts, and most major fediverse platforms will comply with our update and delete requests. But as users who understand a bit about decentralized social media, we understand that once it is sent, there is no guarantee that third parties will delete or update it. The average Threads user probably does not understand that yet.