A little bit about my twitter archiving approach
I've had my account since 2007. Since then, I've archived and then mass erased my tweets multiple times.
It's been a few years since the last purge, and since then I've increasingly relied on using twitter to document things I've been working on, and going back to those threads for reference.
I want to make sure I still have access to that info. The new twitter archive is pretty good for that.
But then there's also threads that I want to preserve for public visibility. I plan to turn most of those into blog posts, but it's time consuming.
In order to remember what they are and put them on top of my list to do, I'm running them through a service https://tinysubversions.com/spooler/
It spools a twitter thread and gives it to you as html. It's great for direct copying into wordpress where you can then edit it. One problem -- the images are still hosted on twitter.
So what I've been doing is actually pasting the contents into gdocs, which uploads the images to google's servers.
while I would love not to depend on Google either, I am still all in, so this works for me now. I can also download those docs as .odt with all the media.
This is my primary manual way of archiving, catching a fraction of a percent of my posts. For everything else I'll rely on the actual archive.
what I'm concerned about is the ability for folks to find my posts when I transfer them to my blog eventually.
twitter was really good with SEO. for obscure topics like Yugoslav computing, you could put "galaksija" or "orao computer" into Google and my threads would pop up immediately.
i've heard from folks how helpful that's been. I sure know how much I've searched for reliable resources on such topics.
but it is what it is.
when I'm ready (hopefully some time today) I'll run twdlt on my account, erasing everything since the moment I generated my last archive and started crossposting
Vlado Vince