Memory requirements for ~100 concurrent users

General Discussion

Suggested Topics


  • 0 Votes
    1 Posts
    316 Views

    @bentael said in away, busy invisible etc. UserStates:

    away - when user is online but no activity for an X amount of time.
    busy - set by user
    invisible - set by user

    etc.

    Currently, it seems that the 'away' state is not auto-enabled when user has no activity for a certain amount of time :

    If it is really the case, wouldn't be greater like this ? (in fact, I need this functionality but don't see it working... Found no code about this in nodebb source code). If it is not the case, what is the time amount for status change to 'away' ? Can it be changed ?

    @administrators : Add on... Would it be possible to have the following operating mode for statuses (more realtime, with socket.io, like smart messaging apps) ? When a user is previously logged in nodebb :

    If he makes actions on nodebb (open a page, posting, typing, scrolling...) and if he is not in 'dnd' or 'invisible' or already 'online' mode, auto-set him in 'online' status and update status on all connected clients (update widgets etc...). If he doesn't do anything for a while and if he is not in 'dnd' or 'invisible' or already 'away' mode, auto-set him in 'away' status and update status on all connected clients. If socket connexion is lost, auto-set him in 'offline' status and update status on all connected clients. If socket connexion is reconnected, auto-set him in its previous status and update it on all connected clients.

    etc...

    In short, knowing in a more realtime status of the users would be a big plus for nodebb. I know it can be ressources consuming but there may be a trick with socket.io (?).

    Another thing : online-cutoff time seems too restrictive for me. If a user is inactive more than this time, he should go into 'away' state but he could always receive notifications because he is not offline. There could be a different time to cut notifications...

    (sorry for this long post ! Hope I'm clear ; I'm french... 😉 )

  • 0 Votes
    3 Posts
    809 Views

    @pitaj Right, Admins and Moderators can see deleted topics.
    I did not think about that.

    But do I also get a notification, when an Admin is replying to my deleted topic?

  • 0 Votes
    5 Posts
    2k Views

    What I see as beneficial is a core feature (or a plugin I supposed) that exposes the database (read-only -- either Redis or Mongodb) keys in such a way that an administrator could create his own search queries with desired results.

    I envision a picker of the thing that can be searched, a way to filter the results and then a picker on what fields should be displayed.

    Does something like this exist?

    @PitaJ

  • 0 Votes
    5 Posts
    2k Views

    @PitaJ Thanks, it is actually not the issue of NodeBB, it is the decision on which strategy to choose. Anyway, I've done no worse than before, that is enough.

    Test the out image links:
    outlinks

  • 0 Votes
    2 Posts
    2k Views

    Hmm... there's always /nickserv identify, but I have absolutely zero idea how that even works.

    What if you made your own bot that listened for private messages from users, and verified them? So all I had to do was /yourbot julian hunter2?

    Then your bot would probably communicate with a companion plugin on our end to verify users by username/password... There's a possibly MITM issue present if you don't use HTTPS though... less so if everything is on one machine and you're communicating via localhost connections...