Conversation
Notices
-
Sorokin Alexei (xrevan86@loadaverage.org)'s status on Thursday, 03-Sep-2020 21:20:11 EDT Sorokin Alexei @vegos I haven't actually seen that happen, really shouldn't on a very deep technical level: every status has a unique id, and in the database that's a unique constraint, which means it's physically impossible to save the same status twice.
Do they have the same notice id or what are the properties of them?