Root_Access

8 ms·

1.
by Root_Access 12d ago
Someone doesn't understand how to use gates.
2.
by Root_Access 29d ago
reticulum.network/manual The full protocol spec is there, I built mine from this without even touching the reference implementation.
3.
by Root_Access 29d ago
Most everyone else is talking about the problem while you mapped the room. Solo is basically pg83's answer to the architecture you just described. If there is no libc independent ABI, build your own loader and shim the boundary. I can
4.
by Root_Access 29d ago
We have a similar no dependency philosophy SQLite already does this with its VFS layer. You hand it the OS functions it needs instead of it grabbing them, etc. You could look at going straight to syscalls, mesa would be a rewrite nightmare
5.
by Root_Access 1mo ago
The protocol itself is more mature than the maintainer situation suggests. I built a complete independent implementation from the public spec in a few sessions. If one person can do that without touching the reference codebase, the foundati
6.
by Root_Access 1mo ago
There is a published spec, I built a clean-room implementation from it. And mine makes at least two Python implementations. The protocol itself is solid, the spec just isn't marketed.
7.
by Root_Access 1mo ago
I'm with you 4.6 is still King for me although all models require careful attention to ensure they maintain taste. If you don't know enough about what you're doing to keep the code clean yourself they will all add complexity
8.
by Root_Access 1mo ago
Claude models have seriously digressed since 4.6 and in some of the most meaningful ways to pro and vibe coders alike. I'm holding onto 4.6 until the bitter end.
9.
by Root_Access 3mo ago
This is true but if you remove the need for credit then you can just get back to work and not have to create a category about it.