From: John Goerzen <jgoerzen@complete.org>
To: Eric S Fraga <esflists@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: *Good* client for Android?
Date: Fri, 13 Oct 2017 08:34:01 -0500 [thread overview]
Message-ID: <87h8v3dvee.fsf@complete.org> (raw)
In-Reply-To: <87sheny32d.fsf@gmail.com>
Eric S Fraga <esflists@gmail.com> writes:
> On Thursday, 12 Oct 2017 at 16:28, John Goerzen wrote:
>> 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?
>
> I am not sure what you are asking for. What is missing in MobileOrg?
> You say it is suffering from bitrot but it works just fine for me on a
> daily basis, with no issues having multiple Android devices using the
> same location. Okay, it no longer works with Dropbox but it does work
> with a number of other media.
The bitrot is a big concern. Android moves pretty fast, and something
that was last updated in 2013 is likely to not play well with a phone on
Oreo (such as mine). I could be surprised, I suppose.
I want as conflict-free a setup as possible, with good resolution of
conflicts when they do occur. MobileOrg seems to be good at this, just
from reading the manual. I'm not convinced that, say, Orgzly would be.
The other is that there is a lack of support for encryption. It is not
an absolute requirement for me, but is certainly very much a "nice to
have". Storing unencrypted stuff on a server is not really ideal.
(None of the other mobile clients save MobileOrg for iOS seem to have
this feature either.)
> For instance, I have recently started playing with org-dropbox [1] for
> capturing notes from an Android device. But I will keep using MobileOrg
> as I need Google calendar synchronisation.
That's an interesting project - thanks.
-- John
next prev parent reply other threads:[~2017-10-13 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:28 *Good* client for Android? John Goerzen
2017-10-12 23:01 ` Martin Alsinet
2017-10-12 23:02 ` John Goerzen
2017-10-13 6:28 ` Eric S Fraga
2017-10-13 13:34 ` John Goerzen [this message]
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=87h8v3dvee.fsf@complete.org \
--to=jgoerzen@complete.org \
--cc=emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
/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).