One of my favorite things about my custom mechanical keyboard, is being able to remap the entire key set in the firmware with VIA. I have fn+arrow keys for media, fn+space for play/pause fn+end for calculator, and a bunch of random others. It is so useful I could never get another keyboard that doesn’t have a similar functionality.
Something about qwen models hold up really well even at low quants. for most other models anything under q5 is cooked, but on 35B-A3B I can get a lot of things done even at q3_xl. It is definitely better than full precision 9B
I am always worried that popular software like this is getting compromised. But what about all the smaller stuff? I download and run a bunch of small programs, especially for game modding. Do the small tools not have the same risk because of their smaller scale invites less dedicated attacks? or do they get compromised and fly completely under the radar?
Mechjeb does a lot of automation for complex maneuvers like planetary transfers, ascent autopilot, target interception, etc..
You can even do a porkchop plot for interplanetary transfer.
but lagrange points are not possible in KSP because of the Sphere of Influence Model.
and orbital slingshots are not included, I assume because they require an intense bruteforce calculation.
I relied on Mechjeb too much in my game, so I did a run using KRPC and built my own autopilot features with it. It was a lot of fun, and I would recommend it.
I do love using local models when I can, but qwen-35B is the best model I can run, and while its an insanely good local model, it does not compare to the big ones.
I liked copilot because I didn't have to think about tokens. I get hung up when having to think about the price of things, and its hard to think about the project at the same time I got to think about token usage like a gas bill. The usage system had its own issues, but having a set amount of requests was a very comfortable way to use a paid AI service.
I would say byteshape is smaller and faster, I can’t really notice a quality difference. But I haven’t used it as much as I only started using it a few days ago.
Now that I have tried out on a few tasks, Qwen3.6 is a huge jump in capability.
It can make improvements to a project that qwen3.5 always struggled with.
I have been using Qwen3.5-35B-A3B a lot in local testing, and it is by far the most capable model that could fit on my machine.
I think quantization technology has really upped its game around these models,
and there were two quants that blew me away
Mudler APEX-I-Quality.
then later I tried
Byteshape Q3_K_S-3.40bpw
Both made claims that seemed too good to be true, but I couldn't find any traces of lobotomization doing long agent coding loops.
with the byteshape quant I am up to 40+ t/s which is a speed that makes agents much more pleasant.
On an rtx 3060 12GB and 32GB of system ram, I went from slamming all my available memory to having like 14GB to spare.
I don't like the Netflix CGI slop movie style filter look it gives everything. But that is a more general trend in tv and movies that I just can't stand.
I do think this will eventually be a major part of the graphics pipeline, but I hope it will be limited and masked to things like hair, which is almost impossible to get right in real-time rendering.
without discussing copyright, I don't believe any of this is copied. Which I think should be the argument that actually matters.
I downloaded both 6.0 and 7.0 and based on only a light comparison of a few key files, nothing would suggest to me that 7.0 was copied from 6.0, especially for a 41x faster implementation.
It is a lot more organized and readable in my armature opinion, and the code is about 1/10th the size.
Small local models are the only thing that still have that magic feeling to me. While large models are still useful and impressive, it makes more sense that they are happening on a giant super computer in a datacenter somewhere. But all the intelligence and capability that can run on my mid level gaming PC is astonishing to me.
Anonymous account unmasking represents a new threat to anonymity.
not just this technique with llms, but the earlier text similarity one.
But I think it would be generally easier to counter in the same way.
Use an llm or heuristics to pose as someone else.
not only do you erase your traces, you add false positives in to the system which reduces the overall effectiveness of these techniques in the future.
A bit of poisoning the well.
I hope eventually an easy to use tool, with maybe a small local llm, can make it easy enough to do this, so that any future deanonymization attacks would be too untrustworthy to rely on
I am curious on how you would algorithmically find the optimal solution for this kind of problem for much bigger grids.
I wanted to do some seed finding in Factorio for the same exact problem using the generated map images, but never found a good solution that was fast enough.