a hangry mouse
@oscillatory
with loss of generality
here's an example I know of where rendering is slow and bad when you zoom in too quickly. i could get the AI fix it but i was thinking i should probably save a small set of problems to fix by myself
if I was doing hardcore accelerationism, i would simply use my datacenter full of geniuses to invent new breakthrough approaches beyond deep learning that have significantly less expensive scaling laws, rather than just pouring more RL data into ever-bigger models
"just issue some bullshit advisory that doesnt even make sense and everything that touches government funding will be forced to use Made-In-The-USA AI, as a kind of protectionism for frontier labs (i'm currently employed at one of these btw)"
consigned to the permanent underclass for being gab-impaired and rizzless
now i'm picturing ISIS giving powerpoint presentations about fanfiction-based jailbreaks
i originally thought i had managed to avoid posting this, but somehow cognitive offloading discourse returned
sorry claude, the GPU poverty *is* the fork. it's non-large-load-bearing.
emphasis on the "can" so far. most seeds don't manage to solve it, but some seeds can for certain combinations of initialization strategy and learning rule
okay dang, up to around 80 tokens / sec with MTP (though I'm losing track of all the acronyms and modifiers. Gemma 4 12B IT QAT MTP (Unsloth)) "please generate an svg of a guinea pig wearing a top hat riding a unicycle" bsky.app/profile/unsl...
i had a dream that I could fill my tangled.org repo READMEs with incomprehensible mathematical pseudocode, and that dream is one step closer to being real now
got a tangled local appview up and running, currently working with Opus 4.8 to try to get LaTeX rendering working via mathjax. some pre-existing CSS rule is adding display: block to all SVGs, gotta fix that first
"If anything is ever learned about what I am, tell me." same goes for me