Flashback to last year's process of restoring and completing the stained glass menorah piece my grandfather left unfinished when he died.
Looking back over that writeup, it bothers me that (as with a *lot* of my art process documentation over the last few years) almost all the primary source material is my twitter feed. I grabbed an archive of my twitter late last year when I wrote off using it, but grabbing an archive is far easier than managing to stage it as its own thing and update any extant links in other places to connect to that.
@joshmillard I think this would take a bit of tweaking but here's a pretty good stab at putting your Twitter archive online on your own site: https://github.com/jvns/tweets-archive
@joshmillard https://www.zachleat.com/web/tweetback/ has been really nice — i’m doing some tweaks to it for my own purposes but it’s a super soild starting point for a durable self-hosted archive…
Fixing inbound links is definitely trickier, though.
@joshmillard I'm in the process of rebuilding my web site and a lot of the articles are cobbled together from skeletal mastodon threads. It's a good way of getting ideas out there, but not so good for solid documentation. My ideal model would be to sketch out the doc as toots, and then replace them all with a link to the actual doc when it's done.
@joshmillard for posting an annotated picture of physical work in progress, toot/twit threads can't be beat. You can't sit down and update an article as you work without breaking flow.
@phooky Yeah. And, like, I do that sometimes! This post is at least a partial go at that. I would like to be much more thorough and consistent about it though, and especially to get stuff *off* of twitter eventually.
This is beautiful