Skip to main content
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented beforecommented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

replaced http://meta.stackoverflow.com/ with https://meta.stackoverflow.com/
Source Link

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

I am definitively in favor of that process.
By the time the 5 "close" votes are here, not enough people are still looking at the question to care to vote for reopening, even if they wanted to at the time where closing votes were being (slowly) set.

Of course, it has been proposed "numerous" time on UserVoice already:


Note: since 2014-05-13 ("When did I get close-vote superpowers?"), users with a gold badge in a tag for a question can immediatly reopen a question closed as duplicate.

This is a (very small) improvement, which doesn't address the initial issue: there is no way to be notified when a question get (finally) closed in order to cast one's own reopen vote.

As I commented before, notification is really broken or non-existent on Stack Exchange sites.
(That is why I have almost 8000 "favorite" questions, in a desperate attempt to catch some of the events which can change the questions I have answered to)
... and "close" events aren't detected anyway, even when you "favorite" a question.

add reopen power
Source Link
VonC
  • 13.7k
  • 7
  • 40
  • 57
Loading
Source Link
VonC
  • 13.7k
  • 7
  • 40
  • 57
Loading