How to not automatically follow observations I identify?

Apologies if this has been asked recently, but the most recent discussion of this I could find was from 2019, so may be outdated.

Is there any way to not automatically follow observations that I add an ID to? The notifications from it are super annoying when all I want notifications about are my own observations (+ mentions etc), and if I identify a lot of observations then unfollowing each of them manually will take a lot of time. In fact, this is one of the things that makes me averse to identifying, which isn’t good for anyone.

1 Like

No, there isn’t. I’d recommend turning off notifications for confirming IDs, though, that will probably remove the vast majority of your notifications.

5 Likes

Whilst not an answer to your question (apologies), a good reason not to automatically unfollow observations you’ve identified is that if your identification is wrong, you will never see the conflicting IDs, comments etc, and therefore you won’t have the opportunity to retract your ID (meaning that it will take more identifiers to correct the community taxon).

If you only ever identify easy taxon where there’s no real room for doubt, this is less of a concern. But if you’re identifying invertebrates, plants, etc. even taxon experts can make mistakes or have room for conflicting opinions that can be corrected, let alone rookie identifiers just hoping to contribute. Leaving notifications on in this case is pretty imperative to ensuring you aren’t making bad contributions that create more work than if you didn’t identify at all, and provides the opportunity to learn more from followup comments or IDs.

14 Likes

No, there isn’t.

That’s frustrating, especially considering this isn’t a new issue - like I said, I found threads about this exact issue from 2019.

a good reason not to automatically unfollow observations you’ve identified is that if your identification is wrong, you will never see the conflicting IDs, comments etc, and therefore you won’t have the opportunity to retract your ID

I feel like the solution here would be an option to only be notified of conflicting IDs on others’ observations, rather than having to choose between no notifications for confirming IDs on my own observations and getting lots of superfluous notifcations/having to manually unfollow all observations I ID.

6 Likes

There is an option to not get notifications for confirming Id’s. I haven’t tried turing it off yet so I can only assume that it does what it says.

6 Likes

Check out this tool made by @pisum https://jumear.github.io/stirfry/iNat_observations_updates.html

Instead of opening the notifications one by one, you can use the above instead. It shows all the observers in chart form, so you could just open the ones with your own name.

3 Likes

If I go to my main page, right above the first notification I see four options:

All updates - Your content - Following - Live discussions

Now if I click on Your content, it shows me a list of notifications for only my own observations. Maybe that helps for you!

9 Likes

I really appreciate all the workarounds that everyone is suggesting! It’d still be very nice to have this as a native notifications setting though, since I like getting notification emails (and none of the workarounds apply to that).

1 Like

As tiwane said, that applies to all observations, not just those by others, which would also stop notifications for my observations (which is not what I want).

2 Likes

If you’re using the website, you could identify someone else’s observation, then click the down arrow next to “Follow” and unfollow it. It’s a bit clunky, though.

1 Like

We have asked for better / ANY management of our notifications.
Not going to happen, sadly.

@suntooth I know notifications are irritating (but you have made 12 IDs?) Some of us deal with hundreds around CNC or GSB.
https://forum.inaturalist.org/t/management-of-notifications/60134

But the Community taxon algorithm is also a pain between insisting on more than two thirds, and Ancestor Disagreement. For example

  1. Your ID is wrong. Needs 3 more identifiers. Irritating.
  2. Your ID is wrong. And someone agrees with you. 5 cross identifiers!
  3. One of the wrong hard disagrees at I know it is A Plant. Now we add Ancestor Disagreement to ANY plant IDs. The queue of identifiers wonders why ‘they’ never withdraw their wrong IDs.
  4. If you are sure your ID will not be an issue for future identifiers? Unfollow. Or ID more thoughtfully, where you do want to follow the discussion?
1 Like

But it is good for subsequent identifiers, if yours would have been wrong.

2 Likes

In the context of this discussion of present and future IDs, my understanding is that the dreaded Ancestor Disagreement is no longer an issue because it’s now handled properly - right?
(Not disagreeing with your overall point that keeping track of disagreements in case you’ve made a wrong ID is important, but can we not make things sound worse than they currently are?)

If - the wrong ID has been withdrawn, or outright deleted - the algorithm concedes that there is no disagreement.

While the ID remains active - so too - does the $%#$ Ancestor Disagreement.
https://www.inaturalist.org/posts/25514-clarifying-ancestor-disagreements
iNat’s own explanation. With 5 years of comments.

I am haunted by the graphic someone put up recently. Obs represented as ‘the world’ with an Equatorial girdle of identifiers.

1 Like

For a page that’s entitled ‘Clarifying ancestor disagreements’, I’d have to say it left me more confused that I started. My understanding was that it used to be that a disagreement with an ID automatically disagreed with anything finer than the new ID (which makes no sense, and I thought was what was referred to as ‘Ancestor Disagreement’). Now, though, I believed a disagreement only disagreed with anything directly on the path between the original ID and the disagreeing ID. Is that approximately right?

TBH I click the algorithm

  • if I am unsure if my ID ‘does what it says on the box’

  • Also for obs I ID where the Community taxon is confuddling or confuddled.
    What do I have to do, what can I do - to break the gridlock??

And I leave a comment with a link to that blog post. We remain confused. iNat can explain. Again.

I’ve never understood why I can’t follow ALL notifications for my own observations, and disagree-only for others’ observations. I want to know if I’m wrong about an ID on someone else’s observations. And I want to know EVERYTHING that happens to my own observations, including confirmatory IDs, because that’s useful information for me.

With IDs for others, I’m cautious, and generally only give IDs I’m extremely confident of.

With my own IDs, I often put a lot of work into trying to figure them out. I want to know if that work has been successful! Also because I’m vain, and get a big kick out of finding out I was right. ;-)

3 Likes

This has always been such a major pain point for me also. I am doing quite a few ID’s for others and if I leave active the notifications for confirming ID’s then I get tens or even hundreds of notifications every day, which will also hide any useful notifications about disagreeing ID’s and I will just miss those…
However, if I turn off confirming ID’s then I will no longer get notified about ID’s on my own observations, which is something I would always like to have.
So I ended up turning off confirming ID notifications, but still hoping some day there could be a distinction between notification settings for my own observations and for ID made for others… e.g. only get notified on disagreeing ID’s on others’ observations and get notified about everything happening on my own observations.
I don’t think there is any feature request related to this for now…

1 Like

Def not perfect, but you could sort your research grade obs by recently updated and scroll thru those to check out some of those confirming IDs: https://www.inaturalist.org/observations/identify?reviewed=true&quality_grade=research&order_by=updated_at&user_id=amatala

Notifications are already on the iNat staff’s list of planned upgrades, so they’re not currently accepting feature requests related to them.

1 Like

@Joeb said what I was going to say, and said it better.

1 Like