[WIP] #198 Online Status

[appinteractive]

Save the current lastActiveAt timestamp on the user when requesting the api.

Todos

• Write tests
• Let user decide if last date is shown to other users
• look into queuing the timestamp updating

Related with

Human-Connection/Nitro-Web#262

[roschaefer]

@appinteractive do we really store this in Neo4J? Apollo Server is good at fetching data and/or writing to various services.

This feature would be one of the exceptions where I would be interested in the performance impact.

To me this is more a logging functionality. How about researching a good logging solution before rolling our own?

[roschaefer]

To me it would also be interesting to see not only the last time active, but a visualization of activity. Maybe there is a good solution out there already?

[appinteractive]

What do you mean? It’s just the timestamp of the last activity to be able to show if the user was active in the last 15 minutes, the same that is done in the current alpha. It has nothing to do with logging or audit.

But I agree that we could throttle it with a small queue for that for saving every 30 sek or something like that.

This was just the first shot to validate the idea.

And what did you mean with visualization?

[appinteractive]

@roschaefer now its queued and updated in batch! should be enough for the moment.