I’m a big fan of there’s no harm in a wrong answer or even a question that can be edited. If the question is something you didn’t realize, answering how you discovered the actual answer can be super helpful.
Same with wrong answers, everyone can read things differently or not realize some key item and wrong answers actually tech and document that better ...
I agree - if you’re sure you want to escalate - contacting the stack employees is an avenue to review any action here. Whether it’s moderators like you (you can access moderation tools due to reputation), elected moderators - going outside the community is always available.
I will link to this overall question on how to question moderator abuse:
Thanks for bringing this up in Meta. One of the answers on the original questions mentions
if the package/application follows unix standards, then install it to /usr/local/. There will be no surprises in the package and you can definitely expect a sub-directory structure like bin, etc, include, share, and so on.
which I assumed to be sufficient to answer ...
For the users without sufficient reputation to see the exact wording of why why this was closed see below for the exact text:
Questions must demonstrate a reasonable amount of research & understanding of the problem being solved. Please edit to either a) clearly describe your problem and the research done so far to solve it or b) include attempted ...
Very good question - the hiding of custom close reason seems like either a decision that should be reviewed or we should agitate for changing the threshold - I can see no reason why we shouldn’t let a user like you see precisely why the vote to close was cast.
Since they are not widely visible, first the reasons chosen seem appropriate to me, so I won’t be ...
It was closed in the wrong direction
I read, and re-read both questions/answers several times. Here are my conclusions:
Both questions are about processes running in the background of other users accounts
Both used Fast User Switching to go between the accounts
The original answer contained more explanation and detail
Most importantly, the original answer ...
Thanks for asking. Closing can take a while to get right. I. Your case, I don’t see much harm if any closing to new answers nor in the close direction - sometimes it’s better to close an old post to a new one.
However, I don’t see these as duplicates and have linked then and reversed the close. Let’s see what others think. It might still be closed in one ...
After 3k, blatantly off-topic gets replaced with "Other" and one should explain how it is off-topic.
I suggest you use magic links in the close reason so that after commenting, they lead to the right page. For e.g.:
... because this is off-topic as per [help/on-topic]
Add data.SE style "magic links" to comments