first, i think it’s worth noting that folks should never just agree with identifications. any identification you make should indicate that you actually believe a particular organism is a particular taxon. it’s okay to not agree with others’ identifications if you don’t actually know how to identify that particular organism / taxon.
that said, as far as i’m aware of there’s no mechanism that regular users have access to which will have iNat’s servers filter for and return only cases of disagreements or subsequent refinements, etc. the best you can do is to get a set of observations and then filter on your end for what you’re looking for.
if you know how to do a little programming, you can accomplish this by writing something to get data from the API via /v1/observations and then looking for whatever you’re looking for within those results.
short of that, you can use the page referenced in the first link in your original post. to make things slightly more efficient, you can probably use a few additional parameters:
&per_page=200to bring back more results per page&quality_grade=needs_id,casualsince these are most likely to have further refinements or disagreements&idextra_user_id=[your id]– this a special parameter that works only on that page which shows how your identification compares to the observation taxon. in your case, you would look for cases where your identification taxon is not obs. (you would want descendant, ancestor, other, and maybe N/A.)
here’s the specific configuration of that page that i would use based on the above notes: https://jumear.github.io/stirfry/iNatAPIv1_observations.html?per_page=200&user_id=dineshs&quality_grade=needs_id,casual&order_by=updated_at&options=idextra&idextra_user_id=dineshs
note that because the above page includes a parameter to order by update date, once you go through the initial set the first time, in the future, you’ll only have to look through observations updated since the last time you did this kind of review.