1. I have to say that whilst ’s data export functionality is rubbish, their URLs and use of conneg made it really easy to roll my own. A little hacking with the web inspector (tracking XHR, looking up headers and content) was all that was required — and now it’s documented, so no-one else will have to spend time doing so.

  2. Sophie Dennis: @BarnabyWalters I agree with @laurakalbag : the challenge for #indieweb is ease-of-use - that, not privacy/control, is how platforms win

    sophiedennis one of the interesting things about is that there’s almost no discussion about privacy or security. It’s completely focused on sharing, content ownership and lowering the barrier to entry.

  3. Laura Kalbag: @BarnabyWalters unfortunately not easily enough to setup on your own space. (I’m talking really basic users).

    .Laura Kalbag “on your own space” is important but not a prerequisite of (IMO at least). The domain name is the most important thing, so starting with hosted wordpress.com or tumblr or even just redirecting to it is valid and an easy first step.

    I’d encourage you to check out the Getting Started Guide — feedback/edits gratefully accepted, it’s important to me that the guide is as helpful and clear as it can be.

  4. Laura Kalbag: @BarnabyWalters I agree in theory, but in practice the indie web of which you speak is only available to those with tech skills to make it.

    Laura Kalbag would you agree that wordpress.com (and to a lesser extent, other wordpress services) is non-techie-friendly? It supports most of the infrastructure we’re using on our sites (e.g. pubsubhubbub, pingback, microformats) and provided you hook up your own domain name is an equally valid way of owning your content/identity online as rolling your own.

  5. I was going to spend this evening working on browser extension, but I think it would be better spent providing a /data export utility for fellow ex users.

    From my initial researches, it looks like /u/username.json is the best bet, as it gives a JSON array of all posts written by username, along with like and comment data. It accepts a max_time=timestamp query param, and a _ query param, the function of which I am not sure of.

    To iterate through all the pages of posts from a certain user, start with their profile URL w/ .json tacked on the end, fetch all the items, get the datetime of the last item, convert that to a timestamp, fetch the same URL with ?max_time=timestamp, repeat until an empty array is returned.