".... it is possible now to achieve the same result with the standard dashboard and avoid multiple users to see the same?"
It is ...but its best to not think of it as multi user. The solution achieved by mdashboard was '
It just keeps each user from seeing the update to the page from another user. This solution I worked on with @dceejay ... but it has issues with the state of switches (true/false) because if one user turns a button/switch from on to off (true to false) then no other users will see the state has changed.
Over time working on including disableFeedbackToAllSessions to the official dashboard I began to see things dcejay's way and realized what I was doing was stupid: quote from the msg I sent him:
" I've had a total paradigm shift in my thoughts on
I'm sure I'm in the top 10% of people who push the dashboard to its limits without using a template node and now I'm having second thoughts on this path. I'm now thinking making dashboard have this functionality is like making a 11second 1/4 mile Reliant Robin. It's cool and all but a waste of time. Better/cheeper to buy a car made for the task. The amount of maintenance required is not worth it.
The only reason I wanted
disableFeedbackToAllSessions was overhead.
Right now I use individual docker instances or individual linux users all running their own copy of node-red dashboard. Its real easy as I have a main admin page without access to the outside world spin up/down users as needed. Sure it costs me in ram(to be safe) but the old dell 620rx 20 core is never really burdened by it.
I'm starting to wonder if I'm trying to solve a non problem for the sake of tinkering."
I did complete most of the work needed however. If you wish to integrate it into dashboard see these links and have at it. But as dashboard is approaching end of life and both dceejay and I not wanting to include it you will be on your own.