Give Diaspora* the ability to push notifications and messages from server to clients so we can see notifications and messages without refreshing the page. All the other social networks are doing it. It can be done with websockets and with a ajax fallback for old browsers.
Note: This discussion was imported from Loomio. Click here to view the original discussion.
I love this feature on #Friendica, it’d be great to get it on D* too!
why should we vote for this? to give it some more attention? that’s okay of course, but it makes me wonder if there are any objections against it. I can’t think of one… so with my limited knowledge about it, I’d say definitely YES.
I think it’d be great to get this. We could even make use of a good jquery notification lib so that notifications could appear in a corner of the browser as they happen.
+1
+1
Yep. I think having a vote on it is still necessary to check we all want these things…
Please don’t put up a vote without explaining a specific possible implementation and what technology would be involved. We had this feature but it got removed due to technical issues. Saying “I want this!” one more time (it’s about the 80th one in the history of this project) is completely meaningless and a waste of everyone’s time.
"Yep. I think having a vote on it is still necessary to check we all want these things…"
wouldn’t it be better to wait for someone who doesn’t want it, and then vote?
We could even wait for someone who wants to start working on that and another one who doesn’t want that feature. 
I’d just like to say that it’s important that users are given the option of disabling notifications. I know several people (myself included) who find popup notifications distracting.
Try this GreaseMonkey Script meanwhile:
http://userscripts.org/scripts/show/162873
Works fine; except the notification bar at top.
Please, ask your podmin before changing the interval in the script (traffic for the server, you know ;-)).
Jonne Haß what where the technical issues that made you remove the feature? Is there a discussion/issue on github or any issue tracker?
Also was it implremented with websockets or with Ajax? I immamgine a Ajax implementation will fill the server with requests while a websockets one will just send notifications when they are needed.
It was based on Websockets. It got removed back when the decision process was in-transparent (and I wasn’t involved with it). Iirc the reasoning was something along the lines of too much load on the server, too much code complexity and thus instability in it, back then bad browser support and probably also easier migration for JD to Heroku.