Believe it or not, I'm working on it.

Last updated: Ⰷ/Ⰹ/Ⱊ (2026/09/07)

Introduction
Current Priorities
Vesterdomains
Update Log

Introduction

Vesterman.com has been serving all of your Vesterman needs since 1999, but it and various other Vesterdomains have for long parts of that time (including in recent years) been unusable, down, broken, and/or extremely bare-bones. This clearly implies that your Vesterman needs haven't been very large during those periods. But I can feel your Vesterman needs growing in leaps and bounds!

Most of the time, such issues were due in large part, or sometimes completely, to my laziness, dumbness, and/or incompetence. The direct cause of the most recent (and ongoing) issues, though, was the horrible, horrible web hosting company that purchased the not-quite-so-horrible web hosting company that the sites were previously hosted on. This is not to excuse my part in the blame, as even in this case I should've migrated to another web hosting company long before the horrible, horrible one recently upped its horribleness game.

I am currently migrating to a hopefully-not-horrible web hosting company (well, two of them, really (well, really really, three of them (and probably more that I'm not remembering at the moment (but who's counting)))).

I'm putting this page up here to log what has been done, what I am doing, and what is to be done in this migration. The reason I'm doing that, in turn, is in the probably-futile hopes that the prospect of public shame will prevent me from not doing anything.

Current Priorities

Making this page slightly less embarrassing from an aesthetic point of view
Making super-bare-bones web pages for various Vesterdomains:
Investigating how to handle a few of the as-of-yet unhandled Vesterdomains:
Mailing list manager for FoodClub.us

Vesterdomains

Domain	Purpose	Status
FoodClub.us	For Food Club!	Email: Migrated to Namecheap, except for a mailing list manager Website: Migrated to Namecheap, and bare-bonesified
RWV37.com	Cybersquatting myself	Email: Migrated to Namecheap Website: Migrated to Namecheap, but yet to be bare-bonesified
ThirtySeven.faith	37	Email: Migrated to Namecheap Website: Migrated to Namecheap, but yet to be bare-bonesified 37: 37
ThirtySeven.science	37	Email: Migrated to Namecheap Website: Migrated to Namecheap, but yet to be bare-bonesified 37: 37
Ultracrepi.date	Vesterdomain infrastructure	Still on the horrible, horrible web hosting company, and therefore may or may not be responsive at any given point in time. Will likely stay there for some time, as it is essentially the link between me and their services (such as they are)
Vesterman.com	Serving your Vesterman needs	Email: Migrated to Namecheap Website: Migrated to Namecheap, and bare-bonesified
Vesterman.net	Vesterdomain infrastructure	Email: Migrated to Namecheap Website: Migrated to Namecheap, but yet to be bare-bonesified
Vesterman.org	Cybersquatting myself	lolidk
Vesterman.sexy	Sexiness	Email: Sexily migrated to Namecheap Website: Sexily migrated to Namecheap, but yet to be sexily bare-bonesified Sexiness: Sexy
Vestertopia.com	Cybersquatting myself	lolidk
Vestertopia.email	Vesterdomain infrastructure	lolidk
Vestertopia.net	Internal Vestertopian infrastructure	Nonpublic. Don't even try it, buster!
Vestertopia.org	The official domain of the Eptatriacontarchate of Vestertopia	Email: Migrated to Namecheap Website: Migrated to Namecheap, but yet to be bare-bonesified
Vstr.mn	Vestertopian-Mongolian diplomatic relations	Registered the domain name years ago, but have been unable to log into my account with the Mongolian domain registrar for quite a long while. So, I haven't been able to point the nameservers to an actual computer to host it. Mongolian customer support has been nonresponsive. The Eptatriacontarchate of Vestertopia has faith that this is a mere misunderstanding, and looks forward to the reestablishment of diplomatic contact.

Update Log

Date	Antiquated date	Update #	Info
Ⰷ/Ⰹ/Ⱊ	2026/09/07	Ⰲ	Super bare-bones web page added to FoodClub.us. Now I'm off to sleep.
Ⰷ/Ⰹ/Ⱊ	2026/09/07	Ⰱ	Over the past week or three -- time is a blur -- I have started in earnest on getting off of my horrible, horrible web hosting company. I signed up for a web hosting account at Namecheap. In the short term, I intend to use it for pretty much everything for all public Vesterdomains. I have long used Namecheap as my primary domain registrar, and have been mostly happy with them for that. In the longer term, the intention is to host the actual websites at a different hosting company, Linode (at which I've actually had, but have not really used, an web hosting account for quite some time now). The advantage to Namecheap is that it should be relatively quick for me to get some bare-bones stuff up and running. The disadvantage (at least for me personally) is that a lot of functionality is hidden behind a user-friendly GUI "control panel" (Webuzo) whereas I would greatly prefer low-level control via a CLI. In the interest of not being misleadingly unfair to Namecheap, I want to say that they actually do give me low-level CLI access. The issue isn't really "Can I get low-level access"; rather, it's more "Can I use that low-level access without inadvertently breaking something that the GUI control panel is already handling." I'd also like to say that I don't mean Webuzo is bad; it's fine, and I'm sure it's actually significantly better for many people. Not for me, though; I always wind up fighting against things like it, and so except in the quick-and-dirty short-term bare-bones sense, they always wind up being counterproductive for me. The advantage to Linode (again, at least for me personally) is that I can install my preferred OS (FreeBSD) and easily use my other preferred tools (such as using Caddy instead of Apache as the web server), and I don't have to worry about fighting some tool I don't actually want to have in the first place. There are a couple disadvantages to Linode. First, it's going to take me longer to get something up and running on it, simply because doing so will be more manual. But the other main disadvantage is that (at least by default) they don't allow you to run a mail server on your site. This is probably wise of them, as mail servers are pretty complicated. So, at least for the medium term, I will still be using Namecheap for mail-related purposes even after I've migrated the websites to Linode. My pie-in-the-sky plan for handling the mail involves migrating it off of Namecheap and to Proton, but that's at best a plan for the long term. With all that said, the current state of things is that for most Vesterdomains, I have set them up on Namecheap. Email support on Namecheap is done (mostly, with one important exception, mentioned below). That was the thing I needed to get done the most urgently; email (among other things) suddenly became unusable for hours or even days at a time at my horrible, horrible web hosting company, and email is... pretty important. Website support on Namecheap is done in the sense that I can (and in some cases have) quickly get little web pages up for any Vesterdomain. This is the way it's going to stay; like I said earlier, I'm going to move this kind of thing to Linode, so as a temporary short-term thing before then, I'm just going to have a few little bare-bones pages. The next tasks I have immediately planned are (1) making this very page look slightly less embarrassing than it currently does, (2) getting those little bare-bones pages up for all (or at least most) Vesterdomains, (3) investigating the current status of a few as-of-yet unhandled Vesterdomains and dealing with them, and (4) resolving that "one important exception" related to email. Specifically: One Vesterdomain, FoodClub.us, has long had a mailing list that some of us use to help plan upcoming Food Clubs. The recent extra-horribleness of my horrible, horrible web hosting company killed this (and other things), or at least made it unacceptably unreliable. So, I want to migrate the mailing list to Namecheap. Unfortunately, I don't see a quick way to set up the same mailing list manager I had been using (GNU Mailman) on the Namecheap site. So, I'm going to spend some time investigating further to figure out what my reasonable options are.

Date

Antiquated date

Update #

Info

Ⰷ/Ⰹ/Ⱊ

2026/09/07

Ⰲ

Super bare-bones web page added to FoodClub.us. Now I'm off to sleep.

Ⰷ/Ⰹ/Ⱊ

2026/09/07

Ⰱ

Over the past week or three -- time is a blur -- I have started in earnest on getting off of my horrible, horrible web hosting company. I signed up for a web hosting account at Namecheap. In the short term, I intend to use it for pretty much everything for all public Vesterdomains. I have long used Namecheap as my primary domain registrar, and have been mostly happy with them for that. In the longer term, the intention is to host the actual websites at a different hosting company, Linode (at which I've actually had, but have not really used, an web hosting account for quite some time now).

The advantage to Namecheap is that it should be relatively quick for me to get some bare-bones stuff up and running. The disadvantage (at least for me personally) is that a lot of functionality is hidden behind a user-friendly GUI "control panel" (Webuzo) whereas I would greatly prefer low-level control via a CLI. In the interest of not being misleadingly unfair to Namecheap, I want to say that they actually do give me low-level CLI access. The issue isn't really "Can I get low-level access"; rather, it's more "Can I use that low-level access without inadvertently breaking something that the GUI control panel is already handling."

I'd also like to say that I don't mean Webuzo is bad; it's fine, and I'm sure it's actually significantly better for many people. Not for me, though; I always wind up fighting against things like it, and so except in the quick-and-dirty short-term bare-bones sense, they always wind up being counterproductive for me.

The advantage to Linode (again, at least for me personally) is that I can install my preferred OS (FreeBSD) and easily use my other preferred tools (such as using Caddy instead of Apache as the web server), and I don't have to worry about fighting some tool I don't actually want to have in the first place.

There are a couple disadvantages to Linode. First, it's going to take me longer to get something up and running on it, simply because doing so will be more manual. But the other main disadvantage is that (at least by default) they don't allow you to run a mail server on your site. This is probably wise of them, as mail servers are pretty complicated. So, at least for the medium term, I will still be using Namecheap for mail-related purposes even after I've migrated the websites to Linode. My pie-in-the-sky plan for handling the mail involves migrating it off of Namecheap and to Proton, but that's at best a plan for the long term.

With all that said, the current state of things is that for most Vesterdomains, I have set them up on Namecheap.

Email support on Namecheap is done (mostly, with one important exception, mentioned below). That was the thing I needed to get done the most urgently; email (among other things) suddenly became unusable for hours or even days at a time at my horrible, horrible web hosting company, and email is... pretty important.

Website support on Namecheap is done in the sense that I can (and in some cases have) quickly get little web pages up for any Vesterdomain. This is the way it's going to stay; like I said earlier, I'm going to move this kind of thing to Linode, so as a temporary short-term thing before then, I'm just going to have a few little bare-bones pages.

The next tasks I have immediately planned are (1) making this very page look slightly less embarrassing than it currently does, (2) getting those little bare-bones pages up for all (or at least most) Vesterdomains, (3) investigating the current status of a few as-of-yet unhandled Vesterdomains and dealing with them, and (4) resolving that "one important exception" related to email. Specifically:

One Vesterdomain, FoodClub.us, has long had a mailing list that some of us use to help plan upcoming Food Clubs. The recent extra-horribleness of my horrible, horrible web hosting company killed this (and other things), or at least made it unacceptably unreliable. So, I want to migrate the mailing list to Namecheap.

Unfortunately, I don't see a quick way to set up the same mailing list manager I had been using (GNU Mailman) on the Namecheap site. So, I'm going to spend some time investigating further to figure out what my reasonable options are.

bob@vesterman.com