writer, seamstress, onliner
just trying to have a good time
secrets page was @schlock



cactus
@cactus

the term itself is fascinating. there is nothing natural or organic about a hyperlink, i've never seen anyone call a working link alive, and yet a broken link is dead and links becoming broken over time is rot. the breaking of a link can, depending on the context, be frustrating, tragic, amusing; this it has in common with the more conventional kind of death. but we recognize that to live is to one day die, and there may be no justice in when or how but no justice can be asked of if. we will not last forever; why should our work? decay exists as an extant form of life, as they say. that iconic post itself doesn't exist anymore, it seems; we keep it alive through active preservation, and if it outlasts all its authors it will be because so many people found it compelling. a former drama youtuber recently removed several of his toxic edgelord videos, and of course they're not gone (and the links themselves may still work, i don't care enough to check) but it's good that he can do at least that much to clean up the cultural mess he helped make. maybe the fact that links can rot is a good thing, actually. may the worst of all our links rot before we do.

but of course, there's a spectrum, and just because the median tumblr post or youtube video deserves ephemerality doesn't mean there's nothing to be said for permanence. if we really could recover dinosaur DNA from mosquitoes trapped in amber, that could be very neat as long as we didn't do anything unwise afterwards. there's always nonprofits volunteering to be the metaphorical amber, but it takes a lot of money to remember everything for all of time, and they have an unfortunate tendency to also use that money to pick losing fights with big industries and get into Web 3.0, plus you only need them after the link has already rotted, so the simplest solution would be for links to just always keep working. the issue with that is that internet domains are like real estate in that you can only ever rent, and if you don't pay then someone else will so goodbye. i've had several domains lapse and immediately be squatted, especially later in grad school when $20 was a silly amount of money to waste to preserve the domain for a side project i'd long since given up on. links rot because domains expire, and one of the reasons domains expire is that someone else will pay for them if you won't, therefore, if you want to get rid of link rot, you absolutely have to get rid of capitalism.

computers really are a land of contrasts, huh.


cactus
@cactus

my domain registrar deleted pig.observer with no warning, after sending me an email a few weeks ago that said the renewal was successful. i contacted support and they gave it back, though.

i hadn't decided whether i actually think domain expiration is a bad thing or not - i briefly had a digression about that in the original post but i took it out for concision - but now that it has happened to a thing i still care about and that still has users, i am officially anti-domain-expiration.

also the site is still down, because i haven't been able to log in and fix the NS records, because i can't connect to their control panel. and i can't ping it from my home internet, or from a datacenter in Los Angeles, or from a datacenter in London, so i think they may have fucked up their network configuration. does anybody have DNS registrar recommendations that actually support a reasonable set of TLDs? if i can't have botto.ms and pig.observer on a single professional registrar i'm going to shit a brick and cry.



You must log in to comment.

in reply to @cactus's post:

in reply to @cactus's post:

glauca just seems to have full-on k8s networking failures on a weekly monthly basis, which i learned by having monitoring on haha.business (lmao) and it being one of the first domains i moved over from gandi years ago. led to me just hosting my own authoritative DNS

which i don't mind terribly because i know glauca is like. at most, half a full-time person. but it sure is annoying when i want to change something (outside of DNS because i have control over that now) and it happens to be a bad time for the overengineered distributed systems

i've also had a dumb issue where the database believed the domain was renewed a year out, and so did not attempt to renew a domain, and then it expired. (apparently this was some interop problem between glauca and rrpproxy and the actual registry, but they fixed it?)

i thought about self-hosting when i was getting monthly downtime on all my domains at the same time, but i am not confident i'd do it better, and i'm skeptical i could get ACME DNS challenges working properly, so the end result could easily still be dubious uptime and manual HTTPS cert renewal but now if anything goes wrong it's my job to fix it.

DNS challenges make it a pain, but i don't use those so. your mileage would definitely vary

i should blog about my setup someday but it's just DNS files in a private github repo and github actions + tailscale to shove them onto my hosts running a fairly standard powerdns authoritative config