I suspect Amethyst's OTS implementation isn't taking edits into account... https://image.nostr.build/2ce250a74f1a977ea7d00d215fecd09c6e36983133a0ceb941a9ba9f82b3eebb.jpg https://image.nostr.build/a9046862d7c876241ae4ade8f106dd083775a4fb7d2f1cd88289cd1dabe538e6.jpg https://image.nostr.build/359440c19b7f45f61639e0a7b8b31fb71e3a76d700e9e4fba52190efed9be947.jpg nostr:nevent1qqsgk2ekevj3pm035gveqwyx0cu4ecw4s5m8xjy5uvhldmur6txljmsppamhxue69uhkummnw3ezumt0d5pzp5x7h70mzt00s86r6lrfg2dm0pyp9tq7f5k48gszmd42cl4yk3nvqvzqqqqqqyfu5lyw
Spell it out for me. What is wrong? The ots field is showing the same for all?
Exactly.
But if all edits took place yesterday, maybe it's not an issue of taking it into account, but showcasing enough time precision to pick them apart.
No, Amythst shoes OTS resolution down to the second, and they're all identical. I'm pretty sure I remember time-stamping that note myself yesterday, prior to it being edited.
Just tested this on my post: editing it doesn't seem to invalidate the existing timestamp.
That kind of defeats the point of OTS right?Everyone can just edit their notes with hindsight while the client is erroneously showing a timestamp proof for the original.
It would be nice if @Vitor Pamplona can clarify how timestamping works. But my guess is that it is linked to a note not edit. It would be better if one could timestamp each individual edit as separate notes and as one switches between edits one can see if they are timestamped or not.
Good catch! I will fix it