spent some time last night putting my twitter archive online, because I think the site could evaporate, and a lot of my process of making is tied up there. the gist: take any tweet of mine, replace the twitter . com with twitter.joeycastillo.com and you get the archived version.
it's not perfect. threads don't reconstruct, and it only shows one photo per post (and no videos). I also truncated the archive at 2019, the start of my adventures in making. still, it's the closest I can come to saving the permalinks that are out there. https://twitter.joeycastillo.com
@joeycastillo oh I'm follow this, been thinking about doing the same so it's great to see how you've done it!
@joeycastillo thank you for thinking of this
@joeycastillo I'm glad for your planning for obsolescence, but honestly I'm more hopeful that the bird site goes down spectacularly
@neverused I'm so torn. it does so much for journalism and activism and mutual aid. it was also my home for nearly sixteen years — that's almost half my life! I agree that if it dying spectacularly would hurt him, I would love that. but there's also a cost to that that's almost too much to bear.
@joeycastillo I agree, I think it's just so unfortunate that it is a cesspool of bigotry and hate unless you purposely avoid it. It's more indicative of people as the problem, rather than the service itself. With that said, recent changes have been in management have been good for encouraging people to think about use and where they express their thoughts. It's not fun, but it may be a necessarily transformative trauma.
@joeycastillo What software did you use for this? I've got my archive downloaded and might want to do the same.
@unwiredben I use a tweaked-by-hand version of Tim Hutton's twitter-archive-parser; I can share the code in a gist if it helps. Essentially just dumping each tweet's markdown to a folder structure that matches twitter's — {username}/status/{id} — and then generating the site with Hugo. https://github.com/timhutton/twitter-archive-parser
GitHub - timhutton/twitter-archive-parser: Python code to parse a Twitter archive and output in various ways

Python code to parse a Twitter archive and output in various ways - timhutton/twitter-archive-parser

GitHub
@joeycastillo Thanks for all the pointers. I'll give it a try once I have a free evening.
@unwiredben Here's a gist with the script I'm using. Minimal changes, mostly just some extra processing to tweets_markdown before generating the main file. https://gist.github.com/joeycastillo/02f417a955164f42cfa082b4eef918bb
Twitter Archive Parser, tweaked to generate a page for every tweet

Twitter Archive Parser, tweaked to generate a page for every tweet - parser.py

Gist
@joeycastillo I think I need to do that too but I post too much garbage there lmao

@joeycastillo Did you just put the archived dump online as a static resource, or did you modify it?

Did you do anything to get other user names in context into it?

@mcdanlj Static resource, nothing pulled in from outside of the downloaded archive, which is just the raw tweet text and media from my side. Means I can probably salvage self-reply threads, but any back-and-forth conversations are going to become islands (and necessarily so, since I don't think I have the right to host other people's tweets).
@joeycastillo Yeah, I was mostly wondering about resolving names from IDs, so that you can figure out who you were responding to. ☺ Thanks for clarifying that!
@mcdanlj interestingly for replies, the archive includes the relevant usernames in the text of the tweet, even when it would push the length over 280 characters: https://twitter.joeycastillo.com/josecastillo/status/1587978317428400130/
And it includes the username and at least _part_ of the text of a retweet for retweets, in old-school RT style: https://twitter.joeycastillo.com/josecastillo/status/1588705498647625728/
@josecastillo

@mcdanlj oh LOL. I get it now. The retweet code must be legacy to when the limit was was 140 characters: if the tweet you're retweeting (plus the "RT" and the username) fits in 140 characters, the whole retweet is included in the archive, plus media! https://twitter.joeycastillo.com/josecastillo/status/1586507526949851137/
@josecastillo

@joeycastillo I asked for my archive two days ago and haven't heard back. Sigh. Maybe that's broken now
@WA5PSA @joeycastillo Same. Guess whoever was in charge of that “micro service” is gone.
@Jake @WA5PSA I asked for mine on Monday; haven't received it, can't re-request it. Luckily I downloaded a snapshot right as the layoffs were happening, so I have that, but I fear he has indeed shut this down.
@joeycastillo @Jake well it's not like I'm gonna go back and read it. I guess.
@joeycastillo @WA5PSA I did mine before the micro services debacle and it still took several days.
@smitty @joeycastillo Do they tell you it's ready back on Twitter or send you an email?
@WA5PSA @joeycastillo definitely on twitter, I THINK I also got an email, but I’m not 100% sure.
@smitty @joeycastillo Waiting for SOAR! Best idea ever
@joeycastillo whoa. I’d be super interested in a workshop on how to do that if it’s something you’d be interested in doing.
@alpenglow Definitely interested in improving the tooling! 24 hours later I have a good idea for some improvements; I think I can make it a one-line twitter-archive-to-Hugo-site script, complete with a paginated timeline view at the index. That is, if folks are lucky enough to be able to pull their archive…

@joeycastillo @alpenglow was just about to toot something sarcastic about this (getting the archive).

Then I got my notification that it was ready. Haven't downloaded it yet.

So it seems to be working (at least now, request was days ago). Just very, very slowly. I did not have an enormous number of posts either.

I'm interested in your process as well. There is some stuff I would like to refer back to but not enough to go back there and find it. 👍👍

@kaybee335 @alpenglow mine came through in the end as well last night: middle of the night, almost five days late, but just in time.
@joeycastillo @kaybee335 i downloaded mine a few weeks ago - might try again just to get the last few weeks too.

@joeycastillo @alpenglow in my case that would be:

Darn it showed up, now I actually have to *do* it.

#MasterProcrastinator