Oh no, one fewer shines for neo-Nazis to worship at!

Okay. So presumably you now feel happy.

What does using that word change about the practical matters being discussed here? Any effect at all?

There's a fine-tuned version called Swift that's been trained to use 58.3% fewer reasoning tokens, apparently with almost no loss of quality. I've not been in a hurry with my personal usage (I set my coding agent loose on a task and then go have tea or whatever) so I haven't experimented with it much but it might be worth checking out if the verbosity of reasoning is a problem.

Qwen4 will be coming out soon too, it has a 27B version, so perhaps they'll have incorporated more efficient reasoning into it from the start. I'm looking forward to testing it out.

Ooh, this looks fantastic. My first thought was "doesn't this just move all the costs to the relay?" But the relay has a 30-day retention limit, so that'd keep storage costs well under control there.

Heh. I use Qwen3.8-27B as my main coding agent, and I sometimes feel really bad for it as I watch the stream of thought go by filled with "wait... am I doing this right? What if I'm completely wrong about this? Is this really what I should be doing??" I want to pet it and assure it that it should have more confidence in itself. :)

But it's the tradeoff that Qwen made to cram that much smarts into such a small bundle of parameters, I guess.

If they pay you money then you can exchange that money for huge amounts of raw meat, if that's what you really want. :)

Oh, I'm sure you wouldn't love to look at it. :) It's not exactly messy, AIs are good at keeping things tidy, but everything about it is ad-hoc. It was never intended to be seen my another mortal's eyes than mine. I don't think there are any API keys or other secrets tucked away in the repo's history but I'd rather not risk it.

Your mess of files is different from my mess of files and the things you'd want to do with them is different from what my code does, I'd suggest getting your own agent on the task from a blank slate. That's the whole point I've been arguing here, that coding agents make these kind of bespoke "home-cooked" applications a lot easier to spin up.

As I recall, my first steps weren't even to have the coding agent write code. I explained my general goal and told it to look through the folders itself to see what work it thought needed doing. That was how I learned that almost all the cover art I'd downloaded from Udio years ago was actually AVIF format that had just been given the file extension JPG, for example - I didn't even know that needed to be fixed.

Make sure you back up your files before turning an AI loose on them, of course. Mine's been very well behaved (I warned it that avoiding data loss was the most important priority) but mistakes can be made.

Oh by all means then. Free is free. :)

It is, in fact, all original work. Much of it has never been off the hard drive it was generated on (the stuff by local models), and when Riffusion got bought out they deleted all the stuff their users had generated so my local copies of those are the only ones left. The metadata is in sidecar .json files, except for the Udio tracks which were in .txt files that first needed to be converted to .json. All very ad-hoc stuff to begin with.

Also, it looks like Dropped Needle is aiming to make the music available for streaming through things like Jellyfin. That's not what I wanted, I wanted to make a web site specifically so that I could control the layout and contents for when I share it with friends (many of whom are not technically savvy and so only know how to click on a web URL).

This really wasn't a "just use pre-existing application X" situation. Even if there had been one that could handle all of that, configuring it would have taken just as much work as explaining to the coding AI what I wanted.

I'd say "sure, why not?"

Depends on how expensive the tool is, mind you. I use local models so I've never had to poke around much at how much the paid ones go for, I don't know what you're using.