Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mesh peer to peer network #91

Open
mrozbarry opened this issue Jun 20, 2020 · 0 comments
Open

Mesh peer to peer network #91

mrozbarry opened this issue Jun 20, 2020 · 0 comments

Comments

@mrozbarry
Copy link
Collaborator

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant