Is there any way we can determine if we're on someone's ignore list, or if there are posts being [systematically] ignored in a specific thread? If not, any consideration to make this change? (don't know if it would require a simple system config, an add-in or a completely custom code change)
Here's a few issues:
Some of us spend cycles replying to someone, and there seems to be some kind of response ... but maybe not. It's not always clear if it's just some kind of general topic reply that happens to also relate to your comment (it's like talking to someone on a call with hidden earbuds, they're smiling and responding to the caller, you're talking to them, they're nodding their head ... but not to you)
In some long running threads, there are users (who are high volume posters), making general topic posts, some of us have already made, there are - let's call them 3rd parties - who appear to not have either user ignored, and they're commenting on one post, and the first poster is making follow up posts that seem to conflict - it just really diminishes the flow of the discussion when you can't tell who can see which posts.
I'm _sure_ there's some kind of concern over "retaliation", but this isn't like an up/down vote, if you've been put on an ignore list you're essentially nonexistent to them - and I understand not wanting constant mention of "Since I'm being ignored ...".
It's also my opinion that doing a reverse ignore on someone you only suspect might be ignoring you doesn't encourage an open communication environment, maybe they just selectively don't reply (maybe they feel like you'll call them on their content), they may have interesting contributions and you'd be happy to tell them, but your comments are going into the ether, maybe you could engage them differently over time, by watching how the interact with other users (that is of course, wasted time if they never see your replies).
I think at the very least it would be nice to be informed that you're quoting a user that has you on ignore.
I've been online a _long_time_ , so I get some of the difficulties in this area, having dealt with some of them, even way back in the BBS/DU days, but I think there's a better answer than the current implementation.
Thanks!