emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: Alex Roper <alex@aroper.net>
Cc: Jude DaShiell <jdashiel@panix.com>, emacs-orgmode@gnu.org
Subject: Re: mobile org
Date: Mon, 18 Nov 2019 12:04:54 -0500	[thread overview]
Message-ID: <rmi36elw1xl.fsf@s1.lexort.com> (raw)
In-Reply-To: <29008bd9-77f8-a60e-856f-cdea841aea79@aroper.net> (Alex Roper's message of "Sun, 17 Nov 2019 18:14:34 -0800")

Alex Roper <alex@aroper.net> writes:

> One other thought, if your only concern with orgzly is Dropbox, you
> might consider an open source alternative such as Syncthing. I used to
> use that on my computers and phone to sync my org before moving to
> termux. By default it does use some sort of cloud locator service for
> NAT hole punching etc, but I believe you can turn that off.

I've been using orgzly, and I didn't even realize it had dropbox support
:-) Looking at f-droid, I don't see an antifeature, so I'm not sure
what's up there.

I keep my org files in git.  I use orgzly as readonly because sync/merge
is basically messy, especially since orgzly has a notion of sync from
orgzly internal to android filesystem, and then one has to sync that.
(It might work fine, but I have never tried.)

I have a clone of my org repo on a regular computer, and run syncthing
there and on the phone.  The org repo that is special for syncthing gets
updated every morning.  So whenever the phone has power and wifi
(because I set it that way), it gets a copy of the repo that is
reasonably fresh.

orgzly itself has been solid  and it is kept updated on f-droid.

It is true that syncthing has relay and discovery servers, but they can
indeed be turned off.   My understanding is that the servers run open
source code and do not have plaintext access, but I can of course see
why you don't want that, both to avoid traffic analysis and on
principle.

  parent reply	other threads:[~2019-11-18 17:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18  0:01 mobile org Jude DaShiell
2019-11-18  0:13 ` Alex Roper
2019-11-18  2:03   ` Jude DaShiell
2019-11-18  2:14     ` Alex Roper
2019-11-18  2:34       ` Jude DaShiell
2019-11-18 17:04       ` Greg Troxel [this message]
2019-11-18 20:03       ` flow
2019-11-18  3:38 ` Charles Philip Chan
2019-11-18 12:42   ` Anssi Saari
2019-11-19 14:59     ` Charles Philip Chan
2019-11-18 21:08 ` Richard Lawrence
2019-11-19  8:56   ` Diego Zamboni
2019-11-19  9:16     ` Neil Jerram
2019-11-19 20:03       ` Richard Lawrence
2019-12-04 15:31   ` Jude DaShiell
  -- strict thread matches above, loose matches on Subject: below --
2017-01-23 12:49 Mobile org Paul Schlesinger
2017-01-25 23:13 ` Sean Escriva
2017-01-30 17:26   ` Kenneth Jacker
2017-01-30 17:59     ` Paul Schlesinger
2017-01-31  3:59       ` Sean Escriva
2010-04-24 13:11 mobile org charles snyder
2010-04-20  2:12 clsnyder
2010-04-20  7:44 ` Reinout van Rees
2009-09-02 15:44 Mobile org Marcelo de Moraes Serpa
2009-09-02 16:06 ` Matt Lundin
2009-09-02 18:31   ` Delwood Richardson
2009-10-03  6:25   ` [AvataR]
2009-12-10 21:11     ` Adam Spiers
2009-12-11 16:30       ` BKnoth
2009-09-02 20:53 ` Bernt Hansen
2009-09-03  6:33 ` Ian Barton
2009-09-07 18:54   ` Eric S Fraga, Eric S Fraga
2009-09-08  2:26     ` Miguel Fernando Cabrera
2010-02-03 14:57 ` news

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=rmi36elw1xl.fsf@s1.lexort.com \
    --to=gdt@lexort.com \
    --cc=alex@aroper.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=jdashiel@panix.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).