3
$\begingroup$

This question already has an answer here:

I have read this question about the feature request for adding an option to get a notification when a "followed" question gets answers posted to them.

The top answer seemed to indicate that such a feature was unlikely to be implemented in the near future, without really giving a reason why. However, that question was asked in 2016 and I was wondering if the powers that be have perhaps had a change of heart on the matter (or have been overthrown and replaced by powers that think this is a good idea).

So, with hopes that this question doesn't get marked as a duplicate I pose the following question (for which I haven't been able to find answer yet).

Exactly why are we unable/unwilling to implement this feature?

$\endgroup$

marked as duplicate by Buzz, peterh, user191954, ZeroTheHero, Chris Jan 13 at 1:09

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 7
    $\begingroup$ Possible duplicate of Feature: Subscribing to Questions $\endgroup$ – Blue Jan 6 at 10:55
  • 1
    $\begingroup$ See also (from 2010). It would be nice to get an answer to the italicized question from someone in the know. $\endgroup$ – rob Jan 6 at 14:32
  • $\begingroup$ By "followed" do you mean favorited? $\endgroup$ – David Z Jan 6 at 22:31
  • $\begingroup$ @DavidZ That would be fine as well if there were a feature to get notifications when answers are posted for favorited questions.. $\endgroup$ – InertialObserver Jan 6 at 22:34
  • $\begingroup$ I mean, as far as I know there's no such feature as following a question. I'm just wondering if, when you say following, you mean favoriting? Or are you talking about some other feature such as the rss feed? $\endgroup$ – David Z Jan 6 at 22:36
1
$\begingroup$

Exactly why are we unable/unwilling to implement this feature?

There's no "we" when it comes to implementing features. The entirety of the software that runs Stack Exchange sites is written by Stack Exchange, and it is essentially the same software that's in use for over 150 different sites. We, as the user community of one of them, can request features, but it is up to SE to decide whether those features are worth investing developer time into.

For a large chunk of the history of SE, the best way to request features for the software which cut across the full spectrum of sites has been as a feature request on Meta Stack Exchange (previously Meta Stack Overflow, until MSE was unfolded out of MSO in 2014). However, as you may be aware if you followed this recent fracas, it appears that SE feels that the feature-request-on-meta is not scaling well enough with the growth of the site base, user base, and code base - see in particular this thread.

For the feature request you're interested in, there are already MSE posts here and here with substantial support. So, with that in mind, it is perfectly legitimate to ask

Exactly why are Stack Exchange developers unable/unwilling to implement this feature?

and the short answer is that we don't know. As Tim Post writes in the thread linked above, the communication channels to and from SE on this type of request have not been working very well lately. There's good reason to hope that they're working on ways to improve those types of communication channels, but for the time being it's hard to know.

That specific example, for instance, is certainly a worthwhile goal, and if you get ahold of Adam Lear, Tim Post, or Shog9 (say) on the MSE chat, I suspect that they'll tell you that it's something that they would like to implement. However, it's not an easy thing to roll out: there are significant design questions and challenges (how should it work? how should it look like? are users going to understand it?) and there are significant performance challenges (the feature would represent a whole lot of extra calculations regarding who needs to get notified, over a very large userbase×questionbase, and that has a significant impact on server load) so it could be that it's just not feasible enough. Or it could be that it's potentially feasible but they don't feel it'd be useful enough to merit the investment. Or it could be that they disagree that it would be ultimately useful or in line with the site design goals.

Which of those is the case, though? at present: we don't know.

$\endgroup$
  • $\begingroup$ I see . I didn't know that. Thanks for your clarity. $\endgroup$ – InertialObserver Jan 7 at 6:06
  • $\begingroup$ @InertialObserver No worries. Glad to help. $\endgroup$ – Emilio Pisanty Jan 7 at 6:07
  • $\begingroup$ FYI, Joe Friend is no longer on SE (his profile is not updated). $\endgroup$ – Andrew T. Jan 8 at 2:38

Not the answer you're looking for? Browse other questions tagged .