4 ms·
Tarsnap public beta
- cperciva 18y agoAnother small step towards launch: After many months in private free beta and a bit over a month in private paid beta, tarsnap has now moved into public beta.
- aston 18y agoIn case people aren't paying attention, this is well-respected news.yc-er cperciva's big project. Looking pretty good, Colin! edited for clarity
- cperciva 18y agoI'm well-respected now? When did that happen?
- aston 18y agoWell, you're above me... http://news.ycombinator.com/leaders http://news.ycombinator.com/leaders
- abstractbill 18y agoWhen did that happen? 481 days ago. http://news.ycombinator.com/item?id=35083 http://news.ycombinator.com/item?id=35083
- sanj 18y agoI simultaneously feel proud and shamed for making that happen! No hard feelings, I hope.
- cperciva 18y agoNo hard feelings. :-) More than anything else, I'm amused that people here care so much about the Putnam -- I personally consider winning the Putnam to be a relatively minor accomplishment.
- lacker 18y agoIt's a good signal since it is hard to exaggerate (like you can with claims like "I was the first person to X" for vague X) and very simple to describe. Although maybe I am biased ;-)
- dfranke 18y agoThose of us who pride ourselves at merely having gotten a non-zero score on the Putnam think otherwise :-)
- MaysonL 18y agoAnd here I thought my scoring on it the three times I took it was an accomplishment (like you my first score was probably my best, as it was my freshman year, and my high school didn't offer calculus - I studied it on my own).
- cperciva 18y agowell-respected yc-er cperciva I saw the "well-respected" part before, but didn't notice the "yc-er" part. To avoid any confusion: I'm not funded by YC, I just happen to have been on news.yc for a long time.
- tptacek 18y agoToo much crypto, not enough value prop! Everyone believes you on the crypto stuff already, Colin. Move out of privacy --- privacy is a dead end, nobody has ever capitalized on it successfully (see: the original PGP, Zero Knowledge Systems, that stupid data center in the pylon off the coast of England). Rewrite your content to focus on shared hosting. Emphasize that you don't keep the keys to the backup data. Consider an OEM deal with a Slicehost-like provider. Backup services at hosting providers fucking blow. People won't pay much for privacy, but businesses will pay a decent premium over basic hosting for CYA security. Take your crypto content off the front page; ironically, I think you're decreasing its value by fronting it like this. Instead, brand it: 100% audit-ready, fully transparent, something like that: "the only secure backup provider with [blah blah blah]". I should have to click to see that stuff. For normal users, they should just see the stamp of assurance and a page they can click to with lots of docs. I'm a lot less concerned about the clientside security here and more concerned with the serverside --- even though I know intellectually it doesn't matter much, because the security has been factored out to the client. That could mean one of many things, including these two: (1) People are never going to get over their concern about serverside security and you're going to have to do so something to demonstrate that the server code and associated web apps are secure. (2) You're not doing enough with your pitch to emphasize that your design moves security off the server and onto the clients, where the customers control it. How do you do dynamic updates? Spend less time sniping at SSL, because SSL is still the weak link in this system.
- cperciva 18y agoKeep in mind that this is my blog, not the tarsnap website itself. The tarsnap website -- once it's more than a placeholder -- won't have technical details about the cryptography, but will instead (as you suggest) have it on a separate page which only the interested people will go and visit. My blog, however, is the blog of someone who regularly critiques other people's security (and complains about companies which don't provide details about their security), so people would start asking questions if I avoided the question of security in a blog post about tarsnap. :-) Server side security -- you're right, I should probably talk about that more. The cryptographer in me says that there's no need to talk about it because it's irrelevant... but people tend to care about irrelevant things anyway. What do you mean by "do dynamic updates"?
- Harkins 18y agoThis is like JungleDisk but at twice the storage price and lacking the GUI or cross-platform clients. The per-transfer and per-storage fee sounds like tarsnap also stores back to s3.
- Harkins 18y agoTo be slightly more constructive: You have at least one entrenched, successful competitor with lower prices and more features. This proves there's a market, but it means you're also going to have to be good at marketing to succeed. Especially because the product is something people are very risk-averse about and the switching cost of re-uploading everything is a big pain. You might enjoy the book The Knack: How Street-Smart Entrepreneurs Learn to Handle Whatever Comes Up by Norm Brodsky and Bo Burlingham. There's a lot of war stories from author Brodsky about his document-storage business (a similar market to yours) and how he differentiated it from competitors.
- deleted 18y ago[deleted]
- callmeed 18y agoOk, so I currently use cron + s3sync + s3 buckets to backup servers/sites. How would this differ (other than the price)?
- cperciva 18y ago1. Security. 2. Snapshotted backups. With tarsnap you can take a backup every day, but only pay for each unique block of data once -- which is useful if you don't want your nightly cron job to "synchronize" the fact that you just accidentally deleted some files to S3. 3. I don't know all the details of how s3sync works, but how efficient is it at handling files which have had small changes made to them? (Or, in the case of log files, data appended to them?) Tarsnap doesn't have to re-send the entire file. 4. Does s3sync compress data before storing it? Tarsnap does (and you pay for the bandwidth and storage used, post-compression). 5. When looking at the price, keep in mind that S3 has a per-request fee which can get pretty expensive if your average file size is small.
- naish 18y agoSorry to hear that you aren't up to dealing with the hassles imposed by the Canadian tax systems. Perhaps you can offer a limited storage/bandwidth account free of charge to fellow Canucks. :) There aren't that many of us...
- Andys 18y agoIdle thought: Here in Australia, you don't have to deal with sales tax until you've reached about $50,000 per annum income. I always thought this limit should be much higher, say $200,000, since it is in society's interest for small businesses to keep growing to that stage anyway.
- cperciva 18y agoFor Canadian sales tax (GST) there's a lower limit before people have to collect. For British Columbia sales tax (PST) there isn't any such limit. Rather than allowing in Canadians but worrying about making sure that I figured out how to deal with GST before I hit the limit, while still keeping BCers out, I figured that it was simpler just to keep all Canadians out.
- cperciva 18y agoSend me an email and I'll try to sort something out.
- paul 18y agoLooks nice. How fast is it? I wonder if you could make this into a simple off-site backup system for databases. It might require some more complex interaction with the db or os to do it right though (since the data is changing while you are reading it).
- SkylerNovak 18y agoMy question precisely.
- cperciva 18y agoHow fast is it? How fast is your internet connection? On a decent CPU the tarsnap code can easily push 50 Mbps -- the largest part of its time is spent in zlib, compressing data before it is encrypted and uploaded -- so the limiting factor is almost certainly going to be bandwidth. I wonder if you could make this into a simple off-site backup system for databases. Tarsnap isn't likely to be useful for "real time" replication, but if you get your database to write a transaction log you might get interesting results by having tarsnap loop creating archives containing that one file.
- paul 18y agoI was thinking of the snapshot speed, where most of the data hasn't changed. Do you keep a local cache of block checksums or something to avoid having to check the server? How about an option to not examine the data if the file size and mtime haven't changed? (like rsync does)
- cperciva 18y agoI was thinking of the snapshot speed, where most of the data hasn't changed. On modern CPUs, somewhere in the 20-50 MB/s range. Do you keep a local cache of block checksums or something to avoid having to check the server? Yes. How about an option to not examine the data if the file size and mtime haven't changed? (like rsync does) Tarsnap already does this for unmodified (file name, inode number, file size, mtime) tuples.
- jfarmer 18y agoYou're free to ignore me, but what I see is someone really impressed with their technical prowess and the engineering that went into this software. It looks like cool technology, but the packaging is all wrong. A command line tool? I'd build a seamless front-end a la JungleDisk and bill it as an online safe deposit box -- nobody but you has the key. Just my $0.02.
- bayareaguy 18y agoSounds interesting, this could replace a scheme I use to store files in AWS. However if you're using AWS under the covers I'd rather use my own AWS account via dev pay instead of paypal and I'd rather grant your service permission to store stuff in my own bucket.
- cperciva 18y agoI am using S3 under the covers, but they are very thick covers. It's not feasible to separate out individual users' data to store it in different buckets via devpay. (Also, I'm in Canada, where FPS and devpay aren't supported yet -- as soon as they are, I'll be accepting payments via FPS.)