Perkeep – Open-source data modeling, storing, search, sharing and synchronizing
perkeep.org
perkeep.org
It is a consumer-oriented storage system that is:
- Content addressable
- Indexed
- Tag-oriented (vs. hierarchical)
- Permissions, encryption, compression, sharing, etc.
- Spans storage across machines and clouds
- FUSE mountable
- Has CLI and Web interfaces built-in
The intent is to be a personal data dumpster that you can throw all of your files and other data (tweets, etc.) into for search and backup.
The website could be better organized to convey this information quickly.
It is true that the website needs some love & updated docs. We've been working on Camlistore for 8 years now (with a few drier spells) but our focus has never been marketing. If anything, we didn't want too many non-nerd users for a number of years because it wasn't ready for non-developer usage. That's starting to change.
We have pretty good docs for configuration and such, but we lack some concise high-level text about what the project is and why.
I'll prioritize that.
The idea is that we should be able to own and manage our personal data - which runs into terabytes across one lifetime - without having to trust and/or pay the big cloud companies. So Camlistore from its earliest days had integrated photo gallery since multimedia is where most of the bytes are consumed.
The whole thing once had the label the IndieWeb movement (which we should revive), and Wired wrote about it here - https://www.wired.com/2013/08/indie-web/
Brad Fitzpatrick is also the creator of LiveJournal where he wrote the original version of Memcached in Perl. He also wrote OpenID, and then went on to work with Rob Pike and team on the Go Programming language. Camlistore was one of the earliest projects written in Go (before Hashicorp made it cool) and I imagine that had something to do with him getting into the language itself, but that's for Brad to clarify :)
Sorry to say I'm still confused by what Camlistore does.
Would it be fair to say it's similar to Syncthing[1]?
* [2014 Jun] https://news.ycombinator.com/item?id=7842629
* [2011 Jan] https://news.ycombinator.com/item?id=2156374
Between replicating between several companies as well as your own hardware & having friends & family mirror your stuff (encrypted or not), the ideas is that some copies will continue to exist.
Hardware failures are a given. Companies failing and friends & family dying is also a given. Natural disasters too. The only option seems to be trusting nothing and replicating all your data to lots of places, in future-friendly formats, and that's what Perkeep aims to do. And then a ton of tooling on top of that.
With this name change, I'm slightly more interested again. We'll have to see in the coming months whether they become ready to displace actual large social media platforms or whether it remains a toy project.
I am so confused by what these people do.
But non-local storage does seem to be designed in, because there is text like “if there’s a daemon running rsync in the background, you’re doing it wrong” and “if your UI requires marking folders to be synched/not synched, it’s broken”, so there appears to be an assumption of putting your data elsewhere.
It's a content addressable storage system. There's plugins to import or export from various major services like foursquare, twitter, etc. and plugins let you store stuff in S3 or mongo or google cloud storage, etc.
Your own hard drive local to the Perkeep instance Your own hard drive local to another Perkeep instance you run Your friend's hard drive local to another Perkeep instance _they_ run with encryption to ensure privacy A removable hard drive you can periodically sync to and from A cloud service like S3, etc
Not an effort to sway your opinion, just pointing out that it's not really as simple as just saving images to a hard disk.
1. It can work with any data storage method you want afaict. S3, B2, GCS, local, etc. 2. It's primary goal is to store your data forever, regardless of hard drive failures / storage companies folding / whatever.
I feel like OwnCloud is more compelling, from a glance. Anyone use one or both and able to comment?
If you only store files, sure, use ZFS.
Perkeep (Camlistore) doesn't write to a block device. It has storage backends for a filesystem (which can be ZFS) and any number of cloud object storage providers (S3, GCS, etc).
Perkeep's main value over a fancy POSIX filesystem is storing nameless things (tweets, other social media content + interactions, bookmarks) in common schemas, and permitting search over it all, and then having a variety of ways to browse it (CLI, FUSE, API, web UI, etc).
It's also good at sync to & from things any which way without merge conflicts.
Tho I don't think that many of the self-burned CD's from 2 decades ago are still any good, I know mine usually ain't.
They have neither the skills nor budget to do in-house nor outsourced forensics for this. At this point they don't even know what exactly might be lost to humanity's knowledge, and the descendents of these people, forever.
https://www.officedepot.com/a/products/490099/Bytecc-Interna...
work?
Maybe something like this: (USB floppy) https://www.amazon.com/External-Floppy-Portable-Windows-Requ...
I'm glad to report that, since last I'd spoken to them about the problem, they've figured out what to do and consider the matter solved. The material is recovered, recatalogued, and in good order.
Thanks again everyone for the concern, interest, and offers! I know where to come if something like this comes up again!
My biggest concern is getting the disks. I can walk into my local supermarket and buy a DVD-R or CD-R no issues, but BD-Rs (especially high capacity discs) are hard to find even now.
https://en.wikipedia.org/wiki/M-DISC
It's supposed to provide a decent (not degrading over time) DVD and BluRay backup approach.
Years ago, with CD's I used to use Kodak "Gold" for archival things. M-Disc seems like the modern version.
For those looking to buy one, I would personally recommend just going for a simple one that has an external AC adapter. I've found a lot of the ones that attempt to power the drive straight from USB ports can unexpectedly have the drive power-off due to the USB ports not being able to supply enough power, which is obviously a huge issue (Even my eSATA with a Y-cable has this issue with some drives, making it basically unusable). Powering it externally is a lot more reliable.
You'd be surprised. I went recently through several of mine and lo and behold they could all be read. I guess it depends a lot on your storage conditions.
In other words, anyone can, with enough engineering resources, create a drive capable of reading those discs, which is more than can be said of more proprietary formats.
[1]http://www.ecma-international.org/publications/standards/Ecm...
[2]https://www.ecma-international.org/publications/standards/Ec...
Century? Startup sites like the one above last on average 6 months, that is, until they find out that their $6/mo DigitalOcean droplet suddenly costs... $10/mo! Or $100/mo or whatever and then they find out they cannot fund their $100/mo droplet and call it quits.
So... if you need the data to be around for 100 years, maybe not give it to the random startup.
They adhere to DVD-R, BD-R, and BD-XL standards so it's readable in standard disc drives. You need a special drive to burn them, however (requires a high-power laser).
This is only true of DVDs and a rare variant of Blu-Ray called LTH. Even cheap shitty Blu-Rays from Chinese manufacturers use inorganic dyes these days.
Also, the French Archives did a test of a variety of DVDs for longevity in adverse conditions and found that M-DISC didn't last significantly longer than competitors, even those with inorganic dyes: https://documents.lne.fr/publications/guides-documents-techn...
The US DoD also did a similar test under different conditions and found it performed much better than the competition though: http://www.esystor.com/images/China_Lake_Full_Report.pdf
I suspect the difference between the French and US tests might be the French using a longer test duration and the Americans using light. The French went up to 1000h while the Americans only went to 24 as far as I can tell.
And unlike DVDs, I haven't seen any studies of longevity for M-DISC Blu-Rays.
So let's look at ease of use! You need to have a server and separately manage GPG keys. Looks like an archival blu-ray wins on that front. (And yes I see where it's a goal to make this easy to use for everyone, it's not there yet.)
So whether tabeth is wrong or right to think it's of limited use, they are not fundamentally missing the point.
The biggest problem I found was getting documentation on replication. Having two+ servers mirror-each other, across the internet, seems like a good idea given that otherwise you have a single point of failure as you import all your media/files.
Is this supposed to be used directly by users or as an API for a user-facing application? How is this different from a document DB like MongoDB?
If someone would like to explain to me how (if?) the garbage collection works I'd appreciate it, because I like the concept and kinda want to use this, but deleting stuff is a rather important feature for me. All I could find searching was a post by the devs saying it was already mostly implemented but not finished and not a priority...
https://github.com/camlistore/camlistore/issues/792
Like, I understand that this is a spare time project (I think) but not considering deleting/pruning files to be an important feature is really confusing to me. In its current state, if I accidentally upload the wrong file, am I now stuck with it forever?
Edit: ok I figured out how to at least delete things in the UI (clicking the check mark opens a side menu apparently, `camput delete` doesn't seem to do anything), but as far as I can tell it doesn't actually delete them from the database without running a garbage collect, which isn't implemented so it just hangs around in purgatory.
And so is perkeep.
A RAID is not magically more reliable than a single drive, it needs a bunch of infrastructure and it needs to be duplicated to some other location far away enough to ensure that a single catastrophe such as a fire does not destroy your entire raid.
You are missing the wood for the trees: hard drives and raid devices are storage mechanisms that fall far short of the boundary conditions set to keep something permanently, at worst you will store your data for a couple of hour like that and in ideal conditions maybe for a couple of years, but on a scale of decades or centuries they are useless as a complete solution, though they could be part of such a solution.
You could be made to feel better if the alert only came when it concerned your data. But even then, and going by the NAS sitting under my desk you could be months without any activity and then suddenly two drives fail in two weeks. It's a nice little random data generator.
e: Also, is it so surprising that your drives failed around the same time? It’s likely they were purchased together!
If long-term accessibility is the goal, not off to a good start...
Trying to get data in to an air-gapped environment is a true PITA.
The French found that M-DISC didn't perform much better than regular DVDs and that a weird kind of glass DVD beat everything else hands down.
The Americans found no errors at all in their tests of M-DISC while all other disks encountered them.
I suspect the important differences were:
- The Americans' tested the discs after light exposure, the French did not. It may be that the light caused the regular DVDs to fail but not the M-DISC.
- The French tests were far longer (1000h) than the Americans' (24h). It may be that M-DISC can't survive the adverse conditions past a certain point that the Americans didn't reach.
Also as far as I'm aware, there are no tests of the Blu-Ray variant of M-DISC.
Personally, given the cost of M-DISC, I'd buy a few cheap terrible Blu-Rays instead and just make sure they're not exposed to too much light.
French test: https://documents.lne.fr/publications/guides-documents-techn...
American: http://www.esystor.com/images/China_Lake_Full_Report.pdf
Edit: after seeing some good suggestions about physical storage, I've decided to increase the difficulty of the question, hard mode- How would you do this without physical stuff? (more, new answers about physical welcome too)
Bank vault might be a good idea (assuming they id me fine)
Generate a random seed sentence of so many words. From the secret seed + site domain name generate a password
Store piece of paper with:
Algorithm (could be public in github too) Seed word Site names
Finger prints aren't very good (they end up everywhere!). Retina scan? Not very cheap I'm guessing. Face? Definitely not secret.
Store one copy in a gmail account, and another on imgur.
> assuming [...] memory goes away. (to be safe)
And tattoo the site+username+pass on your thigh.