Of course there is always VLC
611 karma · joined August 7, 2024
Of course there is always VLC
Or maybe just luna too dumb idk. I’ve even had good success with a style guide on Bonsai 2 27B though so I doubt luna is dumber than that
It’s worth taking the time to setup a style guide for your agent to remove llm-isms like this. Somewhat paradoxically, you can even have the agent help write it. Just include a couple of snippets of “bad” phrasing from previous chats, add some commentary about why it’s bad, and what to replace it with, and put that in your system prompt. I could provide examples but the whole point is that you can tailor it to exactly how you want it. This has the added bonus of being a quick sanity check for model quality. If you start noticing llm-ism appear, then likely the model is not following your instruction’s and the thread should be discarded/you need to switch to a better model
They have some AI stuff that they try to push on you during the install, but it can all be disabled so day to day it doesn’t bother you.
Games still came on disk so there wasn’t the madness of endless buggy updates (disks had one opportunity to be bug free so quality was at a higher standard) and internet connectivity was not guaranteed, so there was no way for micro transactions.
However, internet connectivity was available, so things like optional online play were still possible, as well as some basic user generated content.
It’s a bit like when a human brain remembers facts, if you sat down and computed the hash values of the thing you were trying to remember, and traced out a DB lookup in your mind, it’d be a lot slower than just “oh yeah I remember that”.
I’m not sure if lossless h.264 is I only or not, but if it uses inter-frame compression then it’s difficult to randomly access arbitrary frames. For any arbitrary frame you’d have to find the nearest key frame, then interpolate from there based on the inter-frame compression metadata.
LLMs are really weird sometimes. I had some issues using a coding harness where the agent was failing to use the correct tool call syntax (I was using some rando free model on OpenRouter). I sent a message “look closelier at the tool call format” then all the tool calls for the rest of the session succeeded.
Of course for anything of consequence I’d go and actually read the sources (but for plenty of every day stuff it’s fine). On the free plan btw
[1]: https://github.com/anadim/AdderBoard [2]: hn discussion https://news.ycombinator.com/item?id=47170030&utm_source=per...
https://news.ycombinator.com/item?id=47441499&utm_source=per...
And then the maintainer could easily filter out and ignore all the PRs that were tagged such.
Other places have 1 star reviews mentioning mold, pests, break-ins, etc.
I use a similar approach for amazon reviews. If all the 1 star reviews are telling the same story then it’s bad. If there’s not much consistency then it’s probably fine. That and the percentage of 1 star reviews. generally I aim for <5%
5 star reviews are all: “I did the tour and the agent was friendly/place looked nice”
meanwhile the 1 star reviews: “I actually live here and this place is terrible.”
no doubt they ask you to review 5 stars on the tour…
that’s a good clarification, skimming some of the comments here I was thinking they trained it on a single GB200 gpu. THAT would be a huge win for indie AI
Edit: Nvidia GB200 does not refer to a single gpu, Nvidia’s naming scheme is very confusing. Considering past gpus were called H100, H200 etc, I thought GB200 would just be a newer GPU, but it does actually refer to their 30+ gpu rack scale systems. The claim of “we trained this on a single rack of gpus” is definitely much less impressive than “we trained this on a single gpu”
*: Except for the “Random label: sentence that has nothing to do with the label” construct. That one drives me crazy and it makes no sense
Thanks for the link, definitely saving that one