"I've deleted my diagram, can you restore it for me?"
"No. We don't store your data, we never even see it"
"What a useless service, just get my data back or I want to speak to random escalation person"
99% of users don't care about privacy, architecture, etc. They want it to just work (TM). They want us to be able to undo their deletion, find their data when they forget where they moved it.
So it's users pressuring suppliers in the wrong direction, it's not all one way traffic.
We can do both. Google stores, backs up, secures, and generally ensures your data is safe, and you can click a button to download it all if you think you can do any of that better.
This is probably too hard to ask every company to do the same, as it would exclude smaller companies who don't have the resources (this takes a lot of time and development!). So it makes sense for them to offer a different feature set, and accept that it's not going to be suitable for some people.
It doesn't really secure users' data, since Google is able to read that data. Were it truly secure, it would all be encrypted with a high-entropy keys known only to the users.
People without backups could always choose to store their keys with Google, but people who want their data to actually be secure would be free not to.
This is exactly the right solution, and credit to Google for providing it.
> This is probably too hard to ask every company to do the same, as it would exclude smaller companies who don't have the resources (this takes a lot of time and development!).
I'm surprised you say that; it doesn't seem to me that 'dump this user's dataset to JSON/XML/whatever' should be very hard to do. Admittedly I've never worked on anything at Google scale. What am I missing?
To pick a few things I can talk about - sufficient replication to not lose data, data security that actually works (small companies can't - and shouldn't - afford disk shredders and internal access audits), targeted obliteration of customer data on request (including getting it out of the backups without rendering the backups worthless), and making sure that your exported data dump which contains massive amounts of personal information is only ever released to the correct user.
Doing any one of these things in isolation is not all that hard, because you can trade off against the others (for example, it is dead easy to do a data dump if you don't care about data security). Doing all of them at the same time is a large, expensive development project that would sink any startup.
Google Drive 53%
Dropbox 4%
OneDrive 1%
I don't think you're having a problem selling the idea :).
What's hard about "Backup to google drive / dropbox / icloud"?
I've seen single-developer applications do this. If a company of 10 people can't do this, they need to question the competence / diligence of their team.
This is the sad Catch 22 we live in where privacy is jeopardized at the cost of ease of use
Do you think there is any value in educating the customer further? Periodically (5mins) reminding the user with a small notification to save (and backup) their work? I agree it can become a UX Nightmare (e.g. MS Paperclipguy), but having a checkbox "do not remind me again" could possibly go a long way as well.
So may be managing data by product supplier is NOT the wrong direction?
He didn't understand a word.
There have been advances in systems that reclaim or duplicate ownership of third-party data back toward the user, personal API/quantified being the most recent. I think the missing link is not the technology, but rather a social movement that promotes the value of data access and ownership. This might be one silver lining to recent data breach and hacking scandals.
@nsrivast: a movement is exactly what we need. EFF is great, but they have a lot of things on their plate, and are not always consumer friendly. I've been working on core ideas for a Users First movement, because the web, contrary to the ideal results of a free-market, has been putting users last. Much of that has to do with users being the product not the customer. Your ability to "organize & visualize information for efficient teaching & understanding" would be invaluable!
@twhb: you have no email address on your account. please contact me if you are interested in helping articulate such a movement.
Evernote seems to instead have lumped identity and authorization together. And had only one set of authorization permissions: all of your stuff. So when the permissions change, they all change.
This approach is nothing more than laziness. It's not just "not thinking ahead", it's completely ignoring 40 years of practice in the field.
I do agree with your other points, although there are significant limitations to using the filesystem for storage in an application like Evernote. Perhaps a good compromise would be to use a publicly available database engine like postgres (although I'm sure they derive advantages from their proprietary format beyond the mere fact that it's proprietary).
I have been an Evernote Premium user for a long time, and since the company seems to be having a rough time, I recently looked at getting all of my data out of Evernote. What a nightmare.
I loved Evernote. I loved the fact that Phil Libin said he wanted it to be a 100-year company. I don't know all the details, but the fact that he seems to have given up... what a letdown. I'm working on getting my data out. Once I'm done, I think I'm going to let my subscription lapse.
Why do you consider it a "nightmare" to get your data out of Evernote? You can select one, several, or all of the notes in a notebook and export them in either HTML or XML format, with all metadata (tags, etc.) and embedded media included. That seems pretty good to me, and it's certainly easy. If you wanted something more sophisticated, Evernote on the Mac has exceptionally complete support for AppleScript, so you can code up whatever kind of fancy extraction you need.
I'm not asking to be argumentative; I've always considered Evernote's support for extracting data to be pretty darn good, and clearly superior to many competitive apps/services, so I'm curious to know what additional functionality you would require before you'd say it's not a "nightmare" to extract your information.
My point doesn't apply so must just the plain text. It's everything. You put it in in source format, and you get .enex out. It's not so cut and dry.
Going in, it's one step. Coming out, to get it back in the same format you got it... it's multiple steps, and manipulation with other tools.
1. Evernote has dual-language OCR of PDFs and images (and a few others crappy formats that normally shouldn't be used like .docx, .xlsx, etc). That's a great idea. DevonThink doesn't even have Japanese support (their licensed OCR only supports Western languages).
2. Uh... OK god dammit that is really the only feature that keeps me using Evernote's horrid apps. Shit.
And perhaps the analogy is still useful. I'm ok with that situation because I understand and accept the logic of indexing. If the fund I owned changed their prospectus and decided to start active management, or significantly increased their management fee, or whatever, I could pull my money out and invest it elsewhere. Similarly in software there are definite advantages to having a dedicated steward for a given type of data, but it's much better if there is some way to take your data back should you decide to put it elsewhere.
With Evernote, it is possible to export all your notes in a variety of formats, including XML, which can then be imported into other note taking applications if you wish. So to me, the bare fact that the application controls the data isn't necessarily an issue. What was becoming an issue was the fact that they didn't appear to treat it with sufficient respect. I hope we'll see that start to change now.
Close, its a principle fundamental to modern cloud-based companies.
Offer the cloud storage for free, for 0 privacy and the permission to read, copy, access, and sell your data to third parties
> Offer my butt storage for free, for 0 privacy and the permission to read, copy, access, and sell your data to third parties
Moreover, data loss is not a possibility, it's pretty much a certainty, because it's backed straight in the business model. At some point investors need to get their money back, and what better way to do that than have the company acquired? It's such an effective way that a lot of people starting their companies do that hoping that they'll get bought by a big corp. That the product gets subsequently shut down doesn't seem to bother anyone (except the customers, who at this point really should know better than to do business with a startup unless they're prepared for the moment said startup shows them the middle finger and disappears).
No, you don't sound cynical at all. I think It's perfectly reasonable to think that and it seems to be shaking out that way. It does seem pretty douchey to pontificate about your views on applications and data access in the form of a "this is why I don't use applications of this type" and then launch into an example of exactly what happened to someone who just said "I lost all my data with this service." It's kind of like "no shit. Thanks for telling me after the fact, professor."
Not really. It's not like MS Word reading your .doc find can't corrupt it leaving you hanging if you don't have a backup. Catastrophic data loss isn't cured by the "data accessed by an application" model.
> an application failure won't prevent you to 1. keep your data (because backups)
My point is that you don't inherently get backups just by having control of the data file. It requires extra action on your part. If you don't backup, an application failure can easily destroy your only copy.
If all your data exists in a file hierachy that you can browse, edit manually, and back up, then you have the safety of relying only on foundational systems for the survival of your data, and the power to use your data as you please with tools of your choosing. But if the application owns your data—if it stores it behind the scenes and never exposes it to you directly—then your data is exactly as fragile as that application. If there’s a bug, your data can disappear. If the company goes under, your application can rot to unusability. If the product is discontinued, the same. If the company kills a feature, you have to do without it. Or, most likely of all, the company could start publishing buggier and buggier updates, and you’ll have no choice but to use buggier and buggier software.
It seems like a clear choice to me: if the data is anything I value, I must have direct access to it, regardless of what tools I use to manipulate it. The only data I let websites or applications own is data I’d be OK with losing.