Sunsetting liquidex.house (please update my website in your feed reader)

Hi hello!

Due to personal finance and budgeting stuff, I have to shut down the domain liquidex.house. It is currently on the chopping block waiting to be axed by my domain provider, and unless someone wants to shell out $35 US dollars to keep it alive for another year, it’ll expire on 2026-08-27 (in about two months).

Back when I had a stable job, keeping it alive wouldn’t have been a problem, but right now I’m trying to start a new company and have a total of zero stable monthly income for at least the coming year, so I prefer to cut costs wherever possible.

If you’re reading this, there’s a 99.999% chance it doesn’t mean anything to you; you can replace liquidex.house with riki.house in any existing links to the old site that you may have in your linklogs or blog posts or whatever, and they will continue working. You can also use the Wayback Machine.

I am writing this specifically as a blog post though, because there are still a whopping 4 (four) Atom feed subscribers polling away at https://liquidex.house/feed/new.atom, and I wouldn’t want my website to just disappear from their feeds without a trace.

So um, this is that trace! Your reader should have found this post before the old domain died. Of course, the feed currently emits valid links to the new domain, so you’re able to read this without a hitch.

If you’re reading this and want to stay subscribed, please ensure the URL in your feed reader is pointed at https://riki.house/feed/new.atom or even the more current https://riki.house/feed/all.atom if you feel like it. Both work, and will continue to work for as long as this website’s online.

I unfortunately cannot contact the individual subscribers with the problematic links, as I don’t have their email addresses—however as a hint to filter out the potential candidates, here are their User-Agent strings:

  • Mozilla/5.0 (compatible; Miniflux/2.3.x-dev; +https://miniflux.app)
  • node

So uh, if you have a bleeding edge Miniflux instance running, or a homegrown reader in Node.JS, you might wanna have a look at your subscription list I guess. Or don’t, if you don’t care.

I’m sure our paths will cross in the future anyhow.