I just found, when using sync, that logseq android connects to 1.12.12.12 (Tencent Computer Systems). If I block that connection, sync fails. Why is Tencent required if AWS is already being used? Are there any plans for self-hosted sync or git over ssh (not github)?
Thanks for your report.
This is a fallback for DNS lookup. I made the mistake of letting it be the default option.
I’ll fix this in the next release.
To be clarify, only 2 DoH packets(DNS over HTTP requests) will be transport:
- DNS resolve of “api.log.com”
- DNS resolve of “logseq-file-sync-bucket-prod.s3.amazonaws.com”
to add: you can self host sync by saving your graph somewhere and syncing that folder via for example syncthing to a folder an a self hosted server which is then synced as well to a folder on another device.
Another way to do it would be via git, but i never tried that option