-
Notifications
You must be signed in to change notification settings - Fork 801
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
Sync issues with RemoteStorage #377
Comments
Yeah, it still needs to be improved. Currently we are working on improving encryption. We'll try to find out what's happening later. |
Can the issue be closed? It seems like you fixed it :) |
I am a bit unsure about one thing: what happens when an object is completely deleted from machine A? I do think that if it's still live on machine B, machine B is going to re-create it (as it's not on the remote's storage backend), and I'd like to make sure this doesn't happen. Or I could open a different issue, only if needed :-) |
You're right. We haven't tested the removal. I think if an object is removed, it is going to sync it with empty values. Because when an object is removed, the app makes all values of the item empty. |
@bnjbvr we've just received bounty from 5apps for fixing bugs with RemoteStorage. Since you worked on fixing them too, we are eager to share that bounty with you. If you are interested, you can send us your Bitcoin address :) |
Nice, thank you! I've just sent you my bitcoin address to your email address mentioned on Github. Cheers! |
Hi,
I've been using Laverna with RemoteStorage sync for more than a month and I am quite happy so far :-)
I do see some synchronization issues sometimes, though:
That's a bit annoying, because it also makes notes "reappear" from trash, etc. It's not a deal breaker though; I keep on using Laverna on the same machine and these problems don't happen, but that kinda breaks the spirit of sync :-)
Nothing weird seems to appear on the JavaScript developer console.
Please let me know if I can provide further information.
Cheers!
The text was updated successfully, but these errors were encountered: