Return to Question

At Why is the result of this for and while loop different? [duplicate] (and that's just an example), I've voted to close the question as a duplicate.

But because of my reputation on the shell tag, that question has been closed straight away with the "Users with the [shell] gold badge can single-handedly mark [shell] questions as duplicates" message.

I don't like it for several reasons:

• I'm not aware of all the questions posted around here. I know (and sometimes manage to remember) about the ones I've answered, so that's the ones I will typically suggest as duplicate. There may be better ones. So there's an unfair bias here toward high-rep users I'd say.
• When I click close, I do mean suggest to close or vote to close. I like that being reviewed by others, including the OP who may want to edit the question to clarify why his question is different.
• When I see "Closed by John Doe", my reaction is "Who's that John Doe, who does he think he is?", while when I see "Closed by John Doe, user2, user3, user4...", even if I don't agree, my reaction is "fair enough, it's been closed through a democratic process by several people who cared to consider the relevance of the question".
• I don't know which tags I have a gold badge for, nor want to have to check what were the original tags in the question, so I don't know when "close" is a close or a vote to close.

On Unix.SE, that's aggravated by the fact that half the questions are initially tagged as bash or linux, while most of the time, they're really about neither, but more about text-processing, terminal, gnu, files, shell-script, debian...

Some are re-tagged properly, and that means the original tag (like bash (I don't even use that shell and I've got a gold badge on that!)) is no longer visible, which makes the UI even more misleading.

That example above is quite typical. The question was a FAQ, it's a very common issue. I've seen countless similar questions on usenet, and a few on SE as well. It's a shell question, but it's a problem caused by ssh, so tags don't help. Searching for them is not easy. I've voted to close as a duplicate of the first one I found.

So, is there a way to relinquish one's right to close questions single-handedly (other than by creating a separate user as I just did)?

Alternatively, could the interface please be changed so the "close" link becomes a "close!" one, or some other way like a different colour or confirmation dialog to make it clear that the question is going to be single-handedly closed.

At Why is the result of this for and while loop different? [duplicate] (and that's just an example), I've voted to close the question as a duplicate.

But because of my reputation on the shell tag, that question has been closed straight away with the "Users with the [shell] gold badge can single-handedly mark [shell] questions as duplicates" message.

I don't like it for several reasons:

• I'm not aware of all the questions posted around here. I know (and sometimes manage to remember) about the ones I've answered, so that's the ones I will typically suggest as duplicate. There may be better ones. So there's an unfair bias here toward high-rep users I'd say.
• When I click close, I do mean suggest to close or vote to close. I like that being reviewed by others, including the OP who may want to edit the question to clarify why his question is different.
• When I see "Closed by John Doe", my reaction is "Who's that John Doe, who does he think he is?", while when I see "Closed by John Doe, user2, user3, user4...", even if I don't agree, my reaction is "fair enough, it's been closed through a democratic process by several people who cared to consider the relevance of the question".
• I don't know which tags I have a gold badge for, nor want to have to check what were the original tags in the question, so I don't know when "close" is a close or a vote to close.

On Unix.SE, that's aggravated by the fact that half the questions are initially tagged as bash or linux, while most of the time, they're really about neither, but more about text-processing, terminal, gnu, files, shell-script, debian...

Some are re-tagged properly, and that means the original tag (like bash (I don't even use that shell and I've got a gold badge on that!)) is no longer visible, which makes the UI even more misleading.

That example above is quite typical. The question was a FAQ, it's a very common issue. I've seen countless similar questions on usenet, and a few on SE as well. It's a shell question, but it's a problem caused by ssh, so tags don't help. Searching for them is not easy. I've voted to close as a duplicate of the first one I found.

So, is there a way to relinquish one's right to close questions single-handedly (other than by creating a separate user as I just did)?

Alternatively, could the interface please be changed so the "close" link becomes a "close!" one, or some other way like a different colour or confirmation dialog to make it clear that the question is going to be single-handedly closed.

At Why is the result of this for and while loop different? [duplicate] (and that's just an example), I've voted to close the question as a duplicate.

But because of my reputation on the [shell] tag, that question has been closed straight away with the "Users with the [shell] gold badge can single-handedly mark [shell] questions as duplicates" message.

I don't like it for several reasons:

• I'm not aware of all the questions posted around here. I know (and sometimes manage to remember) about the ones I've answered, so that's the ones I will typically suggest as duplicate. There may be better ones. So there's an unfair bias here toward high-rep users I'd say.
• When I click close, I do mean suggest to close or vote to close. I like that being reviewed by others, including the OP who may want to edit the question to clarify why his question is different.
• I don't know which tags I have a gold badge for, nor want to have to check what were the original tags in the question, so I don't know when "close" is a close or a vote to close.

So, is there a way to relinquish one's right to close questions single-handedly (other than by creating a separate user as I just did)?

Alternatively, could the interface please be changed so the "close" link becomes a "close!" one, or some other way like a different colour or confirmation dialog to make it clear that the question is going to be single-handedly closed.

At Why is the result of this for and while loop different? [duplicate] (and that's just an example), I've voted to close the question as a duplicate.

But because of my reputation on the shell tag, that question has been closed straight away with the "Users with the [shell] gold badge can single-handedly mark [shell] questions as duplicates" message.

I don't like it for several reasons:

• I'm not aware of all the questions posted around here. I know (and sometimes manage to remember) about the ones I've answered, so that's the ones I will typically suggest as duplicate. There may be better ones. So there's an unfair bias here toward high-rep users I'd say.
• When I click close, I do mean suggest to close or vote to close. I like that being reviewed by others, including the OP who may want to edit the question to clarify why his question is different.
• When I see "Closed by John Doe", my reaction is "Who's that John Doe, who does he think he is?", while when I see "Closed by John Doe, user2, user3, user4...", even if I don't agree, my reaction is "fair enough, it's been closed through a democratic process by several people who cared to consider the relevance of the question".
• I don't know which tags I have a gold badge for, nor want to have to check what were the original tags in the question, so I don't know when "close" is a close or a vote to close.

On Unix.SE, that's aggravated by the fact that half the questions are initially tagged as bash or linux, while most of the time, they're really about neither, but more about text-processing, terminal, gnu, files, shell-script, debian...

Some are re-tagged properly, and that means the original tag (like bash (I don't even use that shell and I've got a gold badge on that!)) is no longer visible, which makes the UI even more misleading.

That example above is quite typical. The question was a FAQ, it's a very common issue. I've seen countless similar questions on usenet, and a few on SE as well. It's a shell question, but it's a problem caused by ssh, so tags don't help. Searching for them is not easy. I've voted to close as a duplicate of the first one I found.

So, is there a way to relinquish one's right to close questions single-handedly (other than by creating a separate user as I just did)?

Alternatively, could the interface please be changed so the "close" link becomes a "close!" one, or some other way like a different colour or confirmation dialog to make it clear that the question is going to be single-handedly closed.