↳ In-reply-to » 👋 Thanks for joining us on our Sept monthly Yarn.social meetup today y'all 🙇‍♂️ We had @david @sorenpeter @doesnm @falsifian and @xuu 💪 Nice turn out! (not all at once of course, as we normally run this over 4 hours as we span many time zones!)

@movq@www.uninformativ.de Yes! Basically @david@collantes.us points out that if we mandate that authors should retain the original timestamp in their feed when adjusting content, making fixes, etc, that they retain the original timestamp and leave it unaltered. We already do this anyway, we just need to say so.

Now we have a situation where folks participating in a “conversation” (thread) with appropriate clients can automatically detect edits with almost 100% accuracy by mere fact that the next time they fetch a feed that contains an edit, they now see two versions of the Twt with two different hashes, but identical timestamps.

You can use the fetch time to approximate a “version number” and deal with the display (UX) appropriately.

I can’t believe I didn’t think of this before 🤦‍♂️