Step 2: Notice the number of species listed does not include species where the only observer is blocking you, this screenshot is from the actual search where the problem is. This is a search for a genus in a state and there are 2 species with iNat obs (RG in fact) in that genus and state, but I only see both species listed if I am logged out (the other species has only been observed in that state by someone who is blocking me)
Step 3: I tested this with a different genus and state where the same observer is the only one to observe a certain species there and got the same issue
I understand that obs by someone blocking you are not supposed to show in identify, that makes sense since the identify window is specifically for you to add IDs to the observations. But a search for a taxon in a region is more for informational purposes than for identifying the obs listed. In my case I am gathering range data for a book I am writing, and almost missed a critical species because the data is incomplete unless I am logged out. Given that users may not even be aware they are being blocked by a certain person, this is problematic as it presents false data to logged in users who may have no way to know they are being presented incomplete data.
Since blocking is not meant to (and does not) make observations secret from another user (the observations by the user blocking me still show on the map of the species, and are obviously fully visible even in region search when logged out) it does not seem that the species being hidden in region search when logged in is an intended effect of blocking. I’m wondering if the same code was used for the identify window and the region search and this is causing an error.
Turns out everything shows fine if I do a region search for the species, but the species is wrongly omitted if I do a search for the genus
What is the purpose of this? It causes incorrect data to be displayed to users who don’t know they have been blocked, or don’t realize blocking does this (this is not stated clearly anywhere on the website that I have seen), and yet doesn’t seem to do anything to protect the blocking user, as their observations are still visible in other contexts, just not this specific circumstance where the blocked user is looking for a taxon list while logged in. And even if the blocked user was able to see the observation in explore, they still can’t interact with it, so it is no different than when they see the observation on the species page or while logged out.
I’d understand this if it did something meaningful to protect the blocking user, but I don’t see that?
From the account settings page (and FAQ), bolding mine:
Blocking someone prevents them from messaging you, commenting on your observations, identifying your observations, and otherwise interacting with you on iNaturalist. It also removes their observations from your search results and removes your observations from their search results. However, it does not make you invisible to them. They can still find your observations and view your profile, they just can’t interact with you.
I saw that, but the part “However, it does not make you invisible to them. They can still find your observations and view your profile, they just can’t interact with you.” makes it sound like it is only hidden in identify, not explore as well. What is the benefit of hiding them from explore?
Nothing in the quoted text there mentions a difference between the Identify page and Explore. It includes both by virtue of the phrase “search results”. They can find observations in ways you mention above, such as by logging out or being provided a direct link.
I’m unable to answer your other question accurately as I didn’t design the system, but I’m assuming it is a partial harm reduction measure, balancing iNat’s public data philosophy.
For cases of stalking, which was the original motivation for blocking, it does make the victim’s observations a bit harder to find if the stalker doesn’t know any workarounds. Whether or not that’s worth the tradeoff for situations like this I don’t know, but so far I’m lucky enough to not have been stalked.
That makes sense, though as implemented it seems completely ineffective for that purpose. I feel like as implemented blocking is more about ending conflicts and stopping people you don’t trust from IDing your obs than it is about preventing stalking. In my experience dealing with harassment accounts, they always go to the userpage to find obs to post harassment on, and even if you are blocked you can still see all the observation locations from the blocking user’s userpage. It’s hard to imagine that a harassment account would search the genus that includes a species the target observed rather than just going to the target’s userpage.
That said I have never experienced iNat-related stalking IRL nor have I ever blocked anyone (well I once blocked someone for like 40 minutes and then decided I didn’t need to)
