News Posts

Posted on Sat 2021.04.17

Feeds are now back to normal.

The feed system message broker has been replaced and rebuilt.

It should be a lot more robust now as well, as I've segmented the various broker and swarm management components into VMs this time.

Posted on Wed 2021.04.14

Feeds are down due to a hardware failure

Automatic feed updates are down due to what I believe to be a hardware issue in the feed system message broker.

Fortunately, this is fairly straightforward to re-create, but feeds will likely be down until the weekend when I have time to do the required set up.

Posted on Fri 2020.12.25

New Server

Welcome to the new (and hopefully more performant) WLNUpdates.

I've migrated the site to a server with a SSD, in hopes that it'll improve some of the page-load times for people with very large numbers of watched series. Personally, my watched series page has ~2.1K items on it, and it can sometimes be slightly slow to load.

The new site is up and running and synchronized with the old site (which is still up at old.wlnupdates.com if you need it, for probably another month or so, though it's in read-only mode). wlnupdates.com and www.wlnupdates.com should point to the new server shortly, as the DNS update propagates.

If you encounter any issues, please let me know on either the forum, or if that doesn't work, the github project: https://github.com/fake-name/wlnupdates/issues/

Posted on Mon 2020.09.07

Server updates

WLNUpdates was down for a while earlier this evening, as I was updating the server OS.

Normal services should be resuming now.

Sorry for the inconvenience.

Posted on Wed 2019.09.18

Signup and login issues

I updated the site dependencies, and it broke logins again.

Anyways, this lead me to finally vendoring the password encryption wrapper library the site uses. Hopefully this should fix the problems in the future.

Additionally, signup now requires filling out a simple captcha. I've been having issues with people effectively using the site to spam a e-mail address. This should hopefully at least make it a little bit more involved. I've deliberately chosen a simple, self hosted captcha implementation because I don't want to feed the creepy google data-mining project that is ReCAPTCHA.