@thenasaplusit

Well, I switched to a ridge regression model, which yielded far better results. Did you know most regression models can have inference run with just a few basic json parameters? Well, I didn’t until today, but they can.

Anyway, with that done and mostly accurate, I got my first prediction working and with the assistance of Copilot, even a window! Now, there is still serious work on the table, but it feel good to finally have something tangible, doesn’t it?

It seems that maybe using a gradient-boosted tree with the limited features I can use with only 12 data points is perhaps a bad idea….

A one-point swing in the generic ballot causes a double-digit swing in the predicted national lean, turning a predicted blue wave into a comfortable Republican win.

Preprocessing the data is finally over (I really slacked off for a while, bad idea)!

This was actually fairly straightforward to do, it’s just that I kept having different ideas on how to implement the model. What I ended up settling on is a XGBoost gradient-boosted tree that predicts the national House lean (even though this will start by predicting Senate races) using three fundamentals, and then it will use a polling aggregate per race that gets more weight as election day nears.

I pushed it to Nest, and now it will forever be live!

I implemented the logic, now I need to wait for my Nest account to get approved!

It’s finally done!!!!

To round it off, I added a short-ish list of my recommended “must-have” tweaks.

My god, this was a mess…

Basically, I tried to add a IPA downloader, but Git LFS was weird with links and didn’t work, so I removed LFS and the IPA.
That completely broke the repo so I needed to jankily purge everything.
So no, I don’t have much to show for the 2h, but I do have something, a huge QoL improvement: a back button!

I added a survey! Apparently you can just use a Google Form as your backend so you don’t need to make your own infrastructure (see my code).

So, I fixed the sizing issue (which was one line in the , makes you wonder why it isn’t on by default), removed the AI slop, and then, funnily enough, I had AI add all the ~160 needed thumbnails to make sure the wallpaper pages don’t slow to a crawl upon loading (I am NOT doing that by hand, sorry)

I deployed it, I thought I was pretty much done, but it’s all kinds of broken when actually deploying on mobile…

Not to mention my AI assistant apparently decided to add random nonsense I never asked it to that broke legacy compatibility, so now I must fix all these annoying issues…

I haven’t tested it on an iOS device yet, but it’s turning out pretty well!

To round it off, I made the selector responsive to your theme so you don’t suddenly get blinded in the night.

It’s been a long day, but I have some stuff to show for it!
Firstly, I added persistence for all the settings.
I also added both the Material and Cupertino designs, and you can choose which one you want to use!

I added a meme “terminal” (not the easiest, but it was fine especially with some AI assistance).

The coolest change, however, is that I added my new custom domain! It’s not HTTPS yet (thanks GitHub Pages!), but it shouldn’t matter given you don’t have to input any personal data, and I’ll add it as soon as I can.

I added window resizing and a music toggle. The former was just a two-line CSS patch surprisingly.

I added a mode to switch between decimal and binary prefixes, as well as getting rid of spaghetti logic.