@zenfin Possible. I'm not sure if the local ID (113341243798432480 vs. 113341243819953213) is created in a deterministic way.
Conversation
Notices
-
Embed this notice
Nemo_bis 🌈 (nemobis@mamot.fr)'s status on Saturday, 30-Nov-2024 21:50:11 JST Nemo_bis 🌈
-
Embed this notice
Johann z. Baag (ej af Puss-B.) (zenfin@mementomori.social)'s status on Saturday, 30-Nov-2024 21:50:12 JST Johann z. Baag (ej af Puss-B.)
A cancelled boost, maybe?
-
Embed this notice
Johann z. Baag (ej af Puss-B.) (zenfin@mementomori.social)'s status on Saturday, 30-Nov-2024 21:50:13 JST Johann z. Baag (ej af Puss-B.)
Hmm. How did I find the original URI...
404 URI: https://sauna.social/deck/@ChristosArgyrop@mastodon.social/113341243798432480
New URI: https://sauna.social/deck/@ChristosArgyrop@mastodon.social/113341243809413066
Original: https://mastodon.social/@ChristosArgyrop/113341243819953213
-
Embed this notice
Johann z. Baag (ej af Puss-B.) (zenfin@mementomori.social)'s status on Saturday, 30-Nov-2024 21:50:15 JST Johann z. Baag (ej af Puss-B.)
What is happening, when expanding a Mastodon post gives 404, and then taking the URI and opening it on the original server somehow still finds the post – with a new ID?
Two IDs somehow collided? Or the same post was assigned two IDs by mistake?
In conversation permalink
-
Embed this notice