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
Is your feature request related to a problem? Please describe.
One of the greatest things in a remote obsidian solution is the ability to share that with people so that they can collaborate or manage their vault remotely. However, (maybe this is an open box problem, idk) whenever a user is logged in using Obsidian (let's call the first user, user A) and another one accesses the application (let's call the second user, user B), the user B "steals" the mouse from user A. User A can solve this problem by refreshing the page, but then he "steals" the mouse from user B.
Describe the solution you'd like
Be able to have multiple users using Openbox at the same time
Describe alternatives you've considered
Have the option to initiate multiple openbox'es instances, allocating each one to a specific port (heavier on the server RAM). Then, user A will always use port A, and user B will always use port B. The obsidian vaults are still shared between them.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
One of the greatest things in a remote obsidian solution is the ability to share that with people so that they can collaborate or manage their vault remotely. However, (maybe this is an open box problem, idk) whenever a user is logged in using Obsidian (let's call the first user, user A) and another one accesses the application (let's call the second user, user B), the user B "steals" the mouse from user A. User A can solve this problem by refreshing the page, but then he "steals" the mouse from user B.
Describe the solution you'd like
Be able to have multiple users using Openbox at the same time
Describe alternatives you've considered
Have the option to initiate multiple openbox'es instances, allocating each one to a specific port (heavier on the server RAM). Then, user A will always use port A, and user B will always use port B. The obsidian vaults are still shared between them.
The text was updated successfully, but these errors were encountered: