A reminder: REQUEST JSON FORMAT for Google Data Takeout
Google HTML is absolutely worthless.
The instructions don't make this clear, but you're going to see this advice repeated repeatedly and repetitiously. With great frequency. Repeatedly.
REQUEST JSON FORMAT for Google Data Takeout
Why? Because the JSON format can be used by tools for extraction and import. Tim Berners-Lee is building one for Solid, there will be others.
https://github.com/solid/solid-takeout-import (not yet usable, but in process).
REQUEST JSON FORMAT for Google Data Takeout
Why? Because the JSON format contains additional, useful, and critical fields for extraction and import to other sites and tools.
REQUEST JSON FORMAT for Google Data Takeout
Why? Because Google's generated HTML is an ugly bastard stepchild of HTML that's not actually useful even as HTML.
REQUEST JSON FORMAT for Google Data Takeout
Why? Because you'll give yourself far more options and far fewer headaches down the road.
REQUEST JSON FORMAT for Google Data Takeout
Why? Because even if you can't make heads or tails of the output, the tools likely to be developed for intake to where you want the data to go will.
REQUEST JSON FORMAT for Google Data Takeout
Why? Because your friendly neighborhood hackers (and Space Alien Cats) can hack something together using 'jq' and 'awk' (or Python, Ruby, Perl, Go, ...) if all else fails.
REQUEST JSON FORMAT for Google Data Takeout
Why? Because it's what you actually want.
REQUEST JSON FORMAT for Google Data Takeout
REQUEST JSON FORMAT for Google Data Takeout
REQUEST JSON FORMAT for Google Data Takeout
(We
Why they can't just include both formats in the dump, is beyond me. Well, I guess to reduce server load by only doing one data conversion...
ReplyDeleteFilip H.F. Slagter I'm badgering Google on this too.
ReplyDeleteYou had me at "REQUEST JSON FORMAT for Google Data Takeout".
ReplyDeleteSeriously, however, you should take out in JSON because that's the easiest for programmers to import. Period. Just have a copy in JSON, and then get whatever else you think you want.
John Lewis Get used to seeing this. A lot.
ReplyDeleteJeremy Seifert What part of EVERYTHING do you not understand?
If you want any of your posts, comments, data, contacts, etc., or anything else on your Google+ or other Google products, THEN you want to REQUEST JSON FORMAT GOOGLE DATA TAKEOUT.
If you DON'T want to export your data, then you can NOT export it in whatever format you prefer to NOT EXPORT it into. Which is to say, IT DOESN'T FUCKING MATTER.
But there are those of use who DO want to preserve data and DO need to REQUEST JSON FORMAT. Which Google utterly and completely fails to make clear, or a default. And for which I've had words with them about.
And if you're not getting the hint, your question is answered in the post. I'm just a wee bit testy on this point.
Please don't do that again.
(This goes for anybody else reading this.)
Kapiche?
I heard you the first time, and my JSON files are safely tucked away on my HD and my backup drive(s). (This from an old broad who doesn't even know what to do with JSON files, but knows enough to recognize a Voice of Authority when I hear one).
ReplyDeletePat Kight Other people will sort out what to do with them. Google if we're lucky. Tim Berners-Lee if we're even luckier.
ReplyDeleteHold on to 'em.
Everyone take a deep breath.
ReplyDeleteExhale.
Good.
Edward Morbius Can you lock comments, you've made your point about JSON.
John Lewis Done.
ReplyDeleteComments closed.