After receiving this comment, I discovered that there's a reputation requirement for realtime notification updates: Using my Sock Puppet, I checked that 90 reputation is not sufficient.

  • What is the (reputation) requirement for realtime updates using Web Sockets?
  • What's the motivation for this requirement (including the rep. threshold)?

EDIT: I did not test properly. 90 rep worked fine.

  • 2
    Good catch.. maybe Established User? The motivation is obvious, to reduce server load. Millions of live connections are HUGE burden on any server. Edit: well, 101 reputation are enough, used account on other site. Are you sure that with your sock puppet account you don't get web socket connection? How did you check it? – Shadow The Vaccinated Wizard Nov 19 '12 at 13:07
  • @ShaWizDowArd I just tested again, and 90 rep worked fine. I put the wrong user ID in my extension. I had to use 2055992 (the SE ID (I probably used the Stack Overflow user ID). – Rob W Nov 19 '12 at 14:15
  • So I would say now for 90% of certainty that 10 reputation points are needed, being part of the new user restrictions. :) – Shadow The Vaccinated Wizard Nov 19 '12 at 14:25
  • You should rename your Sock Puppet to Socket Puppet – ypercubeᵀᴹ Nov 20 '12 at 0:05

There is no reputation requirement for Web Socket notifications. I verified this by finding a one-rep user, and put his ID in the Desktop Notifications for Stack Exchange extension.

Then, I pinged this user... ...and saw a desktop notification. From which I conclude that web sockets are available for anyone.

I can also confirm that real-time inbox notifications (at the site) should be available at 90 rep. Probably earlier.

You must log in to answer this question.

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