From: John Goerzen <jgoerzen@complete.org>
To: emacs-orgmode@gnu.org
Subject: *Good* client for Android?
Date: Thu, 12 Oct 2017 16:28:42 -0500 [thread overview]
Message-ID: <4916869e-5f2d-479c-b4a6-864d771be3c9@complete.org> (raw)
Hi folks,
All along, I anticipated using this with Android (and, ideally, also
iOS). The MobileOrg feature set looked great, and the syncing mechanism
looked a lot better than sharing Dropbox.
I use git to share my ~/org between two computers (laptop and desktop),
using git-remote-gcrypt to store on a server. This makes syncing and
resolving conflicts easy (I move between the two throughout the day, so
Dropbox is really not a great option here.) Sync integrity -- or at
least robust detection of conflicts -- is a must. Encryption is a "very
nice to have."
Suggestions?
Here's what I've found so far:
MobileOrg - supports WebDAV storage. Has a robust sync system,
integrated with org-mode, in which it seems to be able to write out its
changes to a separate file that the computer can integrate. Sounds
smart, though I suspect it will require additional hacking to support
multiple Android devices. org-mode docs mention encryption for this,
but the encryption is not supported by MobileOrg. Also, MobileOrg was
last updated 4 years ago and seems to have bitrotted.
Orgzly - Supports only Dropbox or local-on-Android storage. The latter
is insecure, as it permits any app on the system to read the files. I
am really not sure how to integrate this with my workflow. It seems
like potentials for conflicts are extremely high.
SyncOrg - Shows some promise, but couldn't even test locally due to the
folder selection screen not working for the "External/Local Only."
Suspect it's trying to do something insecure as well, or doesn't work on
Oreo? ssh support seems to actually be ssh+git, which is nice - except
that it's unencrypted. doh. The documentation made no mention of
resolving conflicts. https://github.com/wizmer/syncorg/wiki/FAQ seems
to suggest it uses the old MobileOrg push/pull in org-mode, but I can't
see how that possibly works well with Git. I suspect that FAQ to be
totally obsolete, because it also talks about a Dropbox synchronizer
that SyncOrg doesn't even have. I could use this if I drop
git-remote-gcrypt, I hope.
MobileOrg-NG - Last updated in 2012. Didn't really look past that.
next reply other threads:[~2017-10-12 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:28 John Goerzen [this message]
2017-10-12 23:01 ` *Good* client for Android? Martin Alsinet
2017-10-12 23:02 ` John Goerzen
2017-10-13 6:28 ` Eric S Fraga
2017-10-13 13:34 ` John Goerzen
2017-10-13 13:49 ` Eric S Fraga
2017-10-13 16:45 ` Leslie Watter
2017-10-13 8:47 ` Neil Jerram
2017-10-13 13:28 ` John Goerzen
2017-10-25 13:36 ` Adonay Felipe Nogueira
-- strict thread matches above, loose matches on Subject: below --
2017-10-14 4:30 Eric Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4916869e-5f2d-479c-b4a6-864d771be3c9@complete.org \
--to=jgoerzen@complete.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).