From: Brett Viren <bv@bnl.gov>
To: David Belohrad <david@belohrad.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: working on cloud
Date: Thu, 09 Jan 2014 10:28:43 -0500 [thread overview]
Message-ID: <ir461ptjhsk.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <uaxd2k1zh47.fsf@beesknees.cern.ch> (David Belohrad's message of "Thu, 09 Jan 2014 09:36:40 +0100")
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
David Belohrad <david@belohrad.ch> writes:
> 1) privacy: you're basically giving your data to somebody else. In case
> of emacs init there is no danger. In case of your org data, which
> might contain sensitive information you want to encrypt it, what
> complicates matter when switching between two win/lin machines
An alternative to consider is btsync. It will provide you similar
functionality as Dropbox but removes reliance on a central server which
is outside your control. All storage endpoints are peers. Peers are
authorized by a shared key so only your machines, or maybe your friends
get access - it's not an anonymous p2p system despite the "bt" in its
name. You can also allow read-only access. Even with no "well known"
server involved I've yet to find a case where peers can not be located
behind firewalls or NAT'ed routers.
Of course, btsync brings it's own issues. The main one for me is that
it's not Free Software (it is a free-of-charge binary) but then the
server side of Dropbox is even more restricted. I guess let your own
conscience be the guide here.
Personally, I go the git/github route for .emacs files and a private git
repo for org files. I would like to not have the (explicit)
commit/push/pull steps for org files and so have been testing btsync.
Ideally there would be some way to marry the benefits of both, but I've
yet to come up with one.
-Brett.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-01-09 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 18:59 working on cloud Renato
2014-01-08 19:28 ` Nick Dokos
2014-01-08 19:32 ` Sam Flint
2014-01-08 21:28 ` Joseph Vidal-Rosset
2014-01-08 23:35 ` John Kitchin
[not found] ` <CAF83ECCdCt8NZK-h5O1t8_M5PytxcvJf71R6csqaBHYLCwM5=A@mail.gmail.com>
2014-01-11 15:38 ` John Kitchin
2014-01-09 7:19 ` Paul Rudin
2014-01-09 8:00 ` David Belohrad
2014-01-09 8:14 ` Paul Rudin
2014-01-09 8:36 ` David Belohrad
2014-01-09 8:48 ` Ian Barton
2014-01-09 15:03 ` Ted Wiles
2014-01-09 15:28 ` Brett Viren [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-13 11:52 Renato Pontefice
2014-01-13 11:54 ` Bastien
2014-01-14 11:45 ` Renato Pontefice
2014-01-14 12:24 ` Nick Dokos
2014-01-14 12:58 ` Alexander Baier
2014-01-14 7:20 ` Paul Rudin
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=ir461ptjhsk.fsf@lycastus.phy.bnl.gov \
--to=bv@bnl.gov \
--cc=david@belohrad.ch \
--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).