MatthiasPortzel
Joined 8 years ago
Joined 8 years ago
Minecraft isn't a intelligence problem. An LLM is more than smart enough to play Minecraft. It's a robotic problem. Even a normal human player can click several times per second, can press two different buttons at the same time, etc. Mineflayer gives you an API that is more limited than a human in some ways (can't see far away from you) and less limited in others (can see through blocks) (if I remember correctly, I could be thinking of Baritone or a different project). Robotics or playing a video game requires a tight continuous feedback loop. When there's 500ms of latency in order to ask the model for every mouse movement, it's no wonder fighting a spider is scary.
Fun fact, Mineflayer, the Minecraft bot interaction API used by YCombinator for these tests, was originally developed by Andrew Kelley (before he started Zig).
Sounds like the “blockchain” part of this is marketing, since it’s on a private blockchain controlled by the exchange. The real selling point is 24/7 trading.
Just also wanted to note that this model has a questionably-enforceable non-commercial use clause in its license. I really wish they had consulted with an IP lawyer, it’s very confusing.
But that’s a shallow moat, and the rest of the features here are not particularly interesting to me. I don’t have a use for plugins or a model-server proxy (I can connect other tools directly to the model provider).
https://codeberg.org/ziglang/zig/src/branch/master/.gitignor...
That fixes the problem of every project enumerating the settings files for every editor.
Then, as others have said, you should commit only the files you intend to commit; and ignore the files that you don’t intend to commit. This shouldn’t be difficult if you’re reviewing what you’re committing anyways.
Listing new files is easy with git status, at which point you can decide to ignore them. If everything is ignored, how do you know what files are new in order to know to un-ignore them?
This is an interesting rabbit hole if you bother to go down it, I encourage you to do some more research.
They’ve been having issues for a while.
Unsloth recommends 18GB of RAM for Qwen3.6-27B (for their version of the model).
> Our team is currently experiencing an unexpectedly high volume of tickets which has resulted in longer response times than we prefer. We acknowledge the long wait and apologize for the experience.
> Sometimes our abuse detecting systems highlight accounts that need to be manually reviewed. We've cleared the restrictions from your account…
Fully self-hosted IMO can be an overcorrection. The issue isn’t “relying on other people”—it’s relying on GitHub, when they’ve made it clear they don’t care about uptime and they don’t care about support turn-around-time.