@anildash I've been building business websites since 1997. I always took pride in making sure dead links got redirected.
Recently worked with an expensive firm to migrate my college's site (3000 links), & they regarded my concerns as quaint. 'We think you should abandon all but your top 100 legacy URLs, & that's what we'll agree to redirect for you.' Any more I wanted, I had to do myself.
@anildash would be interested to see your process for accomplishing this. I have two 18 year olds blogs and the updating has been on my mind for a while.
And agreed on the personal web vs corporate.
@anildash For 12 years now i’ve meticulously, thanklessly maintained a list of 301s in our corporate .htaccess file.
Perhaps the business has accrued no benefit from this, but I can sleep at night.
How many articles are on your blog? I started mine in 2005 and it has more than 1200 articles since then. That's a LOT of articles to check for broken links.
And, since links keep breaking, you'd need to keep fixing.
I often point to past articles and when I do I check for broken links, both to external websites and to my own past websites, which are now only available on the Internet archive.
Do you have a strategy for how you're finding and fixing broken links?
Warning: This Article Is Poorly Written With the ongoing collapse of Twitter, there has been a lot of talk about the Fediverse, and primarily Mastodon, which in spite of it probably not wanting to be, is the flagship in the ActivityPub fleet. I want to preface this by saying that I think Mastodon is really great software from the user side. It’s a very powerful tool and deserves all the credit it gets for it’s UI, it’s filtering features, and it’s very in-depth profile settings.
@KevinMarks @film_girl @anildash
I’m iterating (off and on, in bursts as I find time and desire) on an improved Docker-Compose.
The article claims you need S3 and you definitely don’t. Especially for a single user instance unless you are very popular.
https://github.com/bplein/mastodon-docker-compose/tree/main
I think the heavy lift here is docker experience. If you have it, this is easy. If you don’t, instead of learning all the mastodon bits up front, learn Docker and Docker Compose (which are useful elsewhere)
@KevinMarks @film_girl @anildash
But I agree with the premise that someone with little experience running apps, that consist of multiple services, well biting off Mastodon is a learning curve.
But it all is. Getting stuff running is the easy part. Doing so it lives on “forever” is another thing entirely. Day 2 and beyond.
@film_girl @KevinMarks @anildash the long-term answer here, IMO, is Mastodon-compatible services that let you bring your own domain/identity without the hosting hassle. Ideally, they’d also provide domain registration and light DNS.
Micro.blog isn’t really that, at this point. They’ve chosen to be a separate, but connected network.
Identity and hosting should not be intrinsically linked!