Root_Access

Op doesn't realize there are so many legal terms that will make what he thinks is criminal not criminal and give them so many ways out of it these same people literally write the law good luck sir

Someone doesn't understand how to use gates.

reticulum.network/manual

The full protocol spec is there, I built mine from this without even touching the reference implementation.

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 understand Linus's obsession with taste and the areas it was overlooked or traded.

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

I went zero-dependency on a production CMS. Rust, no framework, no external crates beyond argon2 for password hashing. Running live on client sites. The hard part wasn't building it, it was accepting that everything you reach for is pulling glibc or similar assumptions back in through the side door. SQLite's VFS model is the right pattern. More things should work that way.

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 foundation is solid. The risk is to Mark's implementation, not to Reticulum as a protocol.

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.

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 and drift with time until you get to a point that you must rely on the model to fix it because you no longer understand it. That's a situation I hope to never find myself in.

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.

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.