You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of the problems I've had with maintaining and updating mobtime is that all the data is kept in memory on the server.
I thought I was making a good decision with a memory-managed timer, and I still hold to that - I don't want to store any of your project/details/NDA information in a database, and I want users of mobtime to own their own data.
Moving forward, I'm going to make a radical change; I want all of your data to be managed and shared in your browser, and give you 100% control over who can see/share it.
I'm currently leaning towards PeerJS - after some testing with it on some higher data-performance applications, and some experience with the PeerJS signalling server, I feel confident moving towards this solution.
Some extra benefits could include:
Voice chat
Data privacy
Data resiliency
Opt-in web updates
The text was updated successfully, but these errors were encountered:
A lot of the problems I've had with maintaining and updating mobtime is that all the data is kept in memory on the server.
I thought I was making a good decision with a memory-managed timer, and I still hold to that - I don't want to store any of your project/details/NDA information in a database, and I want users of mobtime to own their own data.
Moving forward, I'm going to make a radical change; I want all of your data to be managed and shared in your browser, and give you 100% control over who can see/share it.
I'm currently leaning towards PeerJS - after some testing with it on some higher data-performance applications, and some experience with the PeerJS signalling server, I feel confident moving towards this solution.
Some extra benefits could include:
The text was updated successfully, but these errors were encountered: