Automatic Refreshing of Content

@karthikeyanak : Lots. The opening of framasphere in France made not-so-concernd-by-privacy people sign up. It's only a matter of who talks about it and the influence they have.

@jonnehass : no source. I just thought I read someone say it, but there's a good chance I'm wrong.

others made it (on other social networks)

Other social networks tend to be either contained on centralised servers and awash with investor money (Facebook, Twitter) so they can just buy as many extra servers as they like, or, in the case of many other decentralised networks, they have few users compared with Diaspora, and generally don't have the historical problem of a few pods having a very large user base, which Diaspora still has. Just because other networks have been able to do this in their circumstances doesn't mean that Diaspora, a volunteer-run and -funded project with a largish user base, can do it without problems.

If Diaspora won’t keep up to modern times, who wants to use it other than few privacy concerned people?

I love the idea that 'modern times' = ' auto-refresh of a page'. Thanks for a morning giggle!

I think the key here is to have this disabled by default, allowing the podmin to enable this if the podmin wants the additional impact on the server. This may provide additional reasons to spread the users to smaller pods, since they (with only a few users) may be more likely turn this feature on.

In addition: If the pod supports auto-refresh the user should be able to enable it for the account.

This would be 2-level opt-in to not impose additional work if not wanted.

I agree with Faldrian here
It should be opt-in
I am not sure how much more load this would make though
Since I am no programmer I cannot really have a say in this, I am only voicing what I've heard from people using diaspora

An automation of the stream and notifications should be in this project, because it makes using the pod more effective and it's easier to reply to stuff in a timely manner

Personally I'd really want something scalable, like socket.io that works on (almost) any browser, using websockets where it can and falling back to whatever is supported.

But that solution would require a small component in between to listen to clients and send over notifications from the server. It doesn't make, imho, sense to bloat the diaspora core server with something like this.

I'm going to say what I've said many times before - diaspora* should have not just one server application that is decentralized to create a network, but also other apps that people can run to contribute towards the network. Because at the moment we're just adding to the already heavy server app.

One of those components could be a simple and light node.js socket.io server app that does comms between clients and servers, relaying only minimal info like "new stuff in feed, please refresh" - then client gets data automatically from server directly. Implemented this in one previous job and man it was efficient, lightweight and worked on any decent browser I could try it on.

Another app I've suggested before is the public posts relay component that could relay posts around the network without making the core server any heavier in federation calls.

All these kind of apps could be run by community members in a decentralized fashion.

Please do not do this without the option to disable or pause, many hate it, I hate that :) is terrible to be reading something and everything moves down.

The diaspora.net.gr pod has a notification system in upper bar indicating the amount of actalizaciones, I like most, is less annoying and consumes less resources.

Not everything do on facebook and g+ is good, I find a very bad reference.

@juansantiago well that is a given, content sliding around is not an option, no sir
either it should auto load the content and reposition your view of the page without you noticing, or as you say, let you know with an indicator, that there is something happening
Incidentally I really like the idea of adding that to the upper bar, do you know how they made that?

@linusigbyoneill

They said that it is a few lines of code that were under consideration for future Diaspora versions.

The podmin is: [email protected] the pod is currently not working, it's a small pod and the server is at Manolis home with slim internet line.

the group of diaspora.net.gr on loomio https://www.loomio.org/g/bT8IoW0k/diaspora-net-gr

@juansantiago Please bring in the other people that were working on this feature, ty.

BUMP please! :)