Hacker News Reader

Comment by trotsky | Hacker News Reader

Looks like a pretty neat project, though I didn't have a very good sense of what they're trying to do until I read the use cases page: http://camlistore.org/docs/uses

Too bad they mostly seem to be focusing on go (for local) and google app engine (for remote) implementations. That's probably a serious barrier to excitement for most people I know, even if they plan to encourage other implementations in the future.

View on HN

What Brett said. Also, as the project matures we will provide binaries and downloads but for now the barrier to entry is probably convenient.

Go isn't the project's choice. It's my personal choice as I continue to love the language. The project encourages all languages.

It sounds more like Tonido (http://www.tonido.com).

At least, the broader principles:

    * Disk is cheap and getting cheaper

    * Put the user in control. Own your data.

    * Privacy and paranoia

    * Decentralization is important, but..

    * End users won't be dorks. Must also be possible to be easy, hosted.

    * Content-Addressability has so many awesome properties (validation, cachability, etc). Use it as much as possible.

    * Redundancy and over-explicitness is fine. Compression will help. Redundancy and over-explicitness will be convenient for future digital archeologists, too.

http://camlistore.org/docs/contributing

Write code. We have Go, Java, JavaScript, Python, Perl in the repo. Multiple implementations are the goal.

I also found overview.txt (link below) in the documentation useful for getting a picture of the project, which if I had to summarize in three words would be "git-like content-addressable filesystem." Some of the things they're talking about for synchronization are neat and could open up some really interesting possibilities.

http://camlistore.org/code/?p=camlistore.git;f=doc;hb=master

overview.txt:

http://camlistore.org/code/?p=camlistore.git;a=blob_plain;f=...

Reply on news.ycombinator.com