[Discuss] AeroFS

[tmetro+blu at gmail.com (Tom Metro)]

Richard Pieri wrote:
> Tom Metro wrote:
>> Uses closed-source, proprietary software. Nullifies the first point.
> 
> Here's their Github repo:
> https://github.com/aerofs

Excellent. They certainly didn't make that easy to find on their site.
(Though admittedly I didn't spent much time looking.)

If you are going to bother to pay the (perceived) "price" of making your
code open, you should really be promoting this in your marketing,
otherwise you aren't getting the benefit from it.

Also note that one of my requirements was not just that there be an open
source implementation, but if the implementation isn't community
developed, that there be an independent community developed version. If
you are really paranoid, you use only the community version. If you are
moderately paranoid, knowing that an outside party was able to develop a
compatible client brings you at least a few steps closer to having
confidence in the commercial implementation. For example, in the process
of implementing the community version, developers would discover that
the output used weak encryption or shared keys with the provider.


> It's a peer to peer sync tool.
> 
> I would prefer the open source solution. Problem is, the open source
> solutions don't actually work.

If you are syncing files among machines that are all within your
firewall, you may not even care about file encryption. Wire encryption
may be adequate, and even that may not be needed.

Have you looked at these open source sync products?
http://www.syncany.org/
http://freefilesync.sourceforge.net/
http://www.data-bag.org/
http://synchronicity.sourceforge.net/

Also, on the proprietary side, there is a fairly new sync tool from
BitTorrent, http://www.bittorrent.com/sync .

 -Tom

-- 
Tom Metro
The Perl Shop, Newton, MA, USA
"Predictable On-demand Perl Consulting."
http://www.theperlshop.com/