Today's gentle side project, because I'm at home sick, is finally killing off my Twitter account. Not because I've remained active over there all this time - god no, I functionally bailed on that dumpster fire years ago - but because that task is so relatively unimportant it's been waiting for a low-energy, low-stakes day like today to happen.

There's a few threads to come over, a few dangling anchors around the internet to update. Some fun stuff will get posted in the coming few days.

One meta-thing to come over is the realisation I had that paying a regular subscription to use a service is actually the right thing to do. If your Mastodon server admin has a link somewhere to throw them a few bucks a month in return for being there, please do it.

"If the service is free, you're the product" works both ways - if you directly support the things you use, they are less likely to resort to extracting value from you as a means to survive.

Have you ever walked around your home town, early in the morning on new year's day? You might see one or two cars on the road, you might pass a sweaty jogger thumping by, but by and large it's an eerie ghost town sort of experience.

That's Twitter, today, looking through my post history for nuggets to bring across. Half the accounts I've interacted with or boosted are long gone. My last post was quoting someone else posting about Twitter's anti-trans stance; that account is now suspended.

Nothing on the internet is forever.

Oh sure, you might toot something funny that gets pasted all over Reddit and Threads and achieves some level of semi-permanence. But Reddit is well into the private equity value extraction phase, and I don't actually know anyone who even uses Threads.

Like Twitter, every website you use today was made by somebody, and like Twitter, every website will go functionally extinct some day. It's transient data on computers made by people, and those fail, in time.

Putting my stuff on more decentralised networks, owned by people like me, seems like the better bet. I doubt digipres.club will hit the PEVE phase any time soon, so it's pretty safe. But it's still run by (lovely) humans, and the fact I moved here after initially landing on Fosstodon says something about the transient nature of websites and people.

I still stand by my strategy for picking a Mastodon server - find one aligned with your interests that has a long-term financial plan.

So: I don't concern myself anymore with the task of preserving my work for future generations. I'm not playing old games and analysing old gamepads for people born next decade - I'm doing it for me, in the here and now, because making stuff about stuff I like makes me happy. If Gravis or their digital protocols or whatever become particularly interesting in future, I hope my work survives to inform that research; but it's not up to me to decide what stuff makes it into the future or not.

There's other lessons to be learned, basic traps to avoid in order to prevent huge swathes of your stuff becoming suddenly and unexpectedly unavailable or offline.

Don't fall into the engagement trap of posting in one place, but linking to another you hope people visit more. One of my tasks today is to more verbosely explain something I uploaded to the Internet Archive, *on* its page on IA, rather than linking to a Twitter post I thought would stand the test of time.

Lesson two there is to avoid using unusual TLDs. It was funny for a while to create websites ending in .af, but it became a lot less funny when a foreign government turns around and shitcans your entire website because it doesn't suit their politics. That's a shitty and pretty unnecessary cause for your cool drawings or discourse or stuff you've made to disappear from the internet.

I once registered a very cleverly named website, using the TLD of a country I'd had nothing to do with, for one of those cool project ideas that never really went anywhere. I paid for it for a couple of years, then realised I wasn't ever getting around to it, and shut it all down. Or so I thought.

A while ago, I got a nasty email from that registrar demanding years of back pay. They gave up after I politely told them to pound sand, but I wouldn't be brave enough to ever visit there, now.

Lesson three: Avoid link shorteners. You're just building another point of failure into whatever you're doing - any URL that gets physically printed is now entirely dependent on that service remaining online, forever, in addition to whatever other service it *actually* links to.

We don't need link shorteners anymore. Entering a URL is no longer a chore on any modern device. You can literally tell your phone what website to go to now. It's extra risk for the sake of vanity and it's silly to do.

To further poke and prod at Twitter, I'll point out it uses its own link shortener at t dot co. Visiting that page, you're greeted with the following message:

"X uses the t.co domain as part of a service to protect users from harmful activity, to provide value for the developer ecosystem, and as a quality signal for surfacing relevant, interesting posts."

The "Learn more" button leads to this article, where they're a little more verbose about it: https://help.x.com/en/using-x/url-shortener

X link shortener (t.co) and how it works | X Help

X automatically shortens links within posts or Direct Messages. Find FAQ surrounding t.co links.

The quality signal part - fair enough, it's crucial data for their core business, I get it. Reducing the character count for URLs is kind of a nothingburger - Mastodon solved this completely by counting any URL as a maximum of 23 characters, and (to my knowledge) most servers have much higher character limits on individual posts, so we're really not punished by websites with poorly constructed URLs. (Twitter's solution, I understand, is to charge a premium for features that are free elsewhere.)
The safety thing, though - they say they check every link against a list of malicious ones, and warn you if you click on a link they think is a bad egg. For that to work, though, the list must be constantly updated, and implicitly trusted; there's nothing stopping them making their own judgements on what websites are good or bad to show to their users, and by hiding URLs with a link shortener you also obfuscate the full fact of them from users, which IMHO makes it easier to go phishing.
@timixretroplays having built a roughly equivalent thing at another company before:

it's probably just the google safe browsing list. it's the bare minimum thing you can do to make the legal people happy

i did add some other domains from a particularly persistent phishing operation to the one i built though, which seemed to annoy them enough to go away once they realized they'd bought like $100 worth of domains so far and i could easily continue doing the same thing