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
{{ message }}
This repository has been archived by the owner on Jun 20, 2022. It is now read-only.
I proxy Standard Notes traffic through Tor (via --proxy-server="127.0.0.1:8118") and it leads to a ton of "conflicted copies" when I edit notes, where it creates copies of the same file with some tiny slight difference that can't be identified easily.
This can make SN almost impossible to use when editing longer texts, because you can't always compare all these copies to figure out what has been lost in which version and how to piece it together again.
I assume this is nothing Tor-specific, but just SN struggling with "high latency" / "less predictable" connections. So I'd expect the same if someone was on slow Internet (e.g., mobile Internet).
Not sure if this is a known issue, however, I found no 100% match while browsing the issues briefly.
Version: 3.8.21
OS: I think it affects all supported OS
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I proxy Standard Notes traffic through Tor (via
--proxy-server="127.0.0.1:8118"
) and it leads to a ton of "conflicted copies" when I edit notes, where it creates copies of the same file with some tiny slight difference that can't be identified easily.This can make SN almost impossible to use when editing longer texts, because you can't always compare all these copies to figure out what has been lost in which version and how to piece it together again.
I assume this is nothing Tor-specific, but just SN struggling with "high latency" / "less predictable" connections. So I'd expect the same if someone was on slow Internet (e.g., mobile Internet).
Not sure if this is a known issue, however, I found no 100% match while browsing the issues briefly.
The text was updated successfully, but these errors were encountered: