here’s the variant that i would probably use here: https://jumear.github.io/stirfry/iNatAPIv1_observations.html?per_page=200&ident_user_id=pisum&options=idextra&idextra_user_id=pisum&order_by=update_date
this returns 200 observations at a time (last updated first), with columns that give some statistics about the identifications made, as well as about a particular identifier’s identification. the stats are all relative to the observation ID. although it won’t point out disagreements to your ID(s) specifically, it will point out potentially disagreeing IDs under the same ancestor (IDs that are descendant taxa vs obs), as well as mavericks (IDs that are in (an) “other” branch).
assuming you’re not getting tons of disagreements, it should be relatively easy to visually scan through the page to find disagreements. (i can scan through most batches of 200 observations in under 15 seconds, looking primarily at 3-4 columns.)
…
the identifications parameter effectively determines agreements / disagreements by comparing individual IDs against the community ID (not by comparing IDs against other IDs), and i bet most people would not expect that that’s how that parameter works. it’s a flawed parameter, in my opinion, and not useful except in some very limited use cases.
iNat developers explain it this way:
(this is the reason i wrote the other thing referenced above. if anyone wants a more detailed explanation of the problems with the parameter, read this: https://forum.inaturalist.org/t/how-to-exclude-observations-with-disagreeing-ids/15016/12. folks are also always welcome to adapt my code to make it do things more tailored to their particular workflow. unless any of the existing feature requests for different kinds of disagreement parameters ever get implemented, there aren’t many better options that i know of.)