Recent example: https://www.inaturalist.org/observations/27958234
Not sure what workflow(s) are creating these, but I see them a lot. Maybe adding an ID manually, then accidentally (or intentionally?) hitting Agree right afterward? Maybe double-hits on Agree in the same or different windows?
Maybe these are a mere annoyance, but they do unnecessarily clutter up the Activity feed in the observation detail, and add some unknown (to me) data load to the system. Don’t know if they affect ID counts or anything else.
Stopping these from being created, plus a simple pop-up indicating “This is already your current ID for this observation” might help folks learn how the various user interfaces work (and don’t work) a little faster too.
If this should be a bug report instead, I’m happy to recategorize it, but my sense is that this has been expected behavior so far, maybe for good reasons I’m not understanding yet.
UPDATE: I see that currently I can’t agree with my own ID, so that’s not a possible workflow. But the duplicate IDs in the example above happened within 1 second of each other, so I can’t imagine that it was add 1st ID ==> withdraw 1st ID ==> add 2nd ID either.