e0qdk

joined 2 years ago
[–] e0qdk@reddthat.com 3 points 2 days ago (2 children)

I'd suggest replacing the shell script with a Python script as a first step. If nothing else, it will probably be a hell of a lot easier to read... Your bots ought to be able to do a first pass at that. If it's actually tripping up on some particular bash/dash-ism like you think, that might even just bypass the issue entirely; if not it should be easier to debug with better readability.

[–] e0qdk@reddthat.com 3 points 5 days ago

Assuming you mean in the computer sense, it's a device that forwards messages from one network connection to another. e.g. between ethernet connections and/or WiFi in home use, typically, or sometimes other kinds of networks in industry.

Messages on the internet are usually transferred as IP packets (Internet Protocol packets). The router looks at the destination address on each packet that arrives, consults a table ("routing table") to determine which connection to use to forward the message out on, and then it actually copies the message onto that connection. The basic idea is pretty straightforward, but it can get complicated in real world situations when you have multiple networks, redundant links, etc.

[–] e0qdk@reddthat.com 2 points 5 days ago

I agree that the hardware being used right now is not well suited. I don't agree that it's strictly necessary to use the right hardware -- there's just less tedious waiting involved for the computation to happen if you've got better hardware. Real-time interaction is the boundary where you need to have good enough hardware. For everything else you just have to be patient enough -- sometimes absurdly so, but you could, in principle, still perform the computation.

LLMs are as close as we have right now, and they have miles to go. But they need hundreds of times more power than the brain does. No it won't be soon and it won't be with this kind of silicon processors.

There are people already baking LLMs into custom hardware -- e.g. https://chatjimmy.ai/

Their demo page isn't the best LLM I've seen (Qwen and Gemma are much more clever and more likely to give decent results) but this is a taste of what's possible... It gives responses at ~17000 tokens a second today.

If I could get answers back from the best Qwen model I've got at that speed, I could just retry every query three times, feed it through another pass to self-assess the results, and then reply before you can blink. That would get rid of a lot of the "confidently claims knowledge about a made up subject" issue we currently see -- we can do the same thing on CPUs/GPUs but you're stuck waiting so long for the result that most people don't bother.

[–] e0qdk@reddthat.com 5 points 5 days ago

Yes. I don't know about the timeline for the higher bar definitions of AGI. For the lower bar definitions, we're basically already at "good enough" today.

If you'd told me 10 years ago that I'd be able to run a program on my computer which would let me feed in an image along with some CSS and JS files and it would then give me a correction that fixes the bug I indicated visually... I would not have believed you. Here I am in 2026 though, and I have done exactly that several times with local LLMs on my own hardware. That same program can also take a natural language description of characters, motivations, and a vague scenario and write a scene. Not an especially well written scene, most of the time, but good enough to get the characters from the initial conditions to ending conditions via complex intermediate steps. I can also define tools it hasn't seen before and it can combine them in sequence to solve a problem defined in natural language. Is it perfectly reliable? Hell no. Is it always coherent? Definitely not. The fact that it can do as much as it can is just bonkers though. If we're getting this far with what I strongly suspect is not the ideal architecture for general intelligence, god only knows what we'll see when we do hit on the right architecture.

[–] e0qdk@reddthat.com 2 points 1 week ago

I mean, if you want to retroactively classify the PornHub jingle as "cerebral catwave", I'm not gonna stop you... 🤔️

[–] e0qdk@reddthat.com 12 points 1 week ago (3 children)

cerebral catwave

That really sounds like it could plausibly be some niche internet microgenre of music even if you pulled it out of your butt, so maybe they just rolled with it?

(If it isn't one yet, someone will probably make it one now that you've posted this... 🙃️)

[–] e0qdk@reddthat.com 4 points 1 week ago

Before I got meds my go to when I woke up from panic attacks and couldn't calm down was putting on an episode of ARIA: The Animation. It's super chill.

[–] e0qdk@reddthat.com 2 points 2 weeks ago

I'm not familiar with the tool you're using and my big, traditionally written projects have largely been organically grown over the years as unpredictable requirements change -- mostly I just try to keep things readable enough that I can jump back in when I need to do so on old projects...

It sounds like you want to incorporate LLMs into brainstorming though. Maybe try using the word "elicitation" in your prompts for early phases? e.g. "ROLE: Requirements Elicitation Specialist" or "ROLE: Architecture Design Elicitation Specialist". You can also meta-prompt to get a system prompt tailored to your specific needs.

[–] e0qdk@reddthat.com 1 points 3 weeks ago

Hmm. I'm not exactly sure how I got there or what would work for other people, but it can be done.

Maybe try thinking of it like pressing the clutch in a manual drive car? The engine might keep spinning, but if you hold down the clutch and ignore it eventually it'll run out of gas...

Or maybe think of it like tuning out someone annoying chattering nearby. They might keep talking for a bit but if you ignore them, eventually they'll get bored and shut up / leave. Even if they come back, just ignore them again if you don't want to engage.

Or, try focusing on sensory details instead of mental chatter. Really notice what you're seeing/hearing/feeling without actively describing it or planning anything.

I don't usually stay in that state all that long, but sometimes it's nice to just be.

[–] e0qdk@reddthat.com 15 points 3 weeks ago (5 children)

I suspect most of them do not have an internal monologue in the same (verbose) sense that humans can have, but the relatively closely related ones (e.g. mammals, probably) likely have similar memory/sensory integration experiences. It's possible to get your own inner monologue to "shut up" for a bit, and just be and feel and do. You can still remember an experience without talking to yourself about it as well. I suspect that closely related animals' experience is like that -- although differing based on the particular set of senses and drives unique to their species.

The further away you go from that, the less idea I have of what's going on (besides "state machine" of some sort). I have only the vaguest notion of what it might be like to be a spider, and even less of an idea of what it's like to be a starfish.

[–] e0qdk@reddthat.com 23 points 3 weeks ago (1 children)

If you're happy and you know it, honk your goose!

HONK HONK

If you're happy and you know it, honk your goose!

HONK HONK

If you're happy and you know it, and you really want to show it -- if you're happy and you know it, honk your goose!

HONK! HONK!

[–] e0qdk@reddthat.com 11 points 1 month ago (1 children)

Imagine some future PugJesus type excavating our memes from the archives and reposting this 1000 years from now. 🧐️

 

I had some free time this weekend and I've spent some of it trying to learn Go since mlmym seems to be unmaintained and I'd like to try to fix some issues in it. I ran into a stumbling block that took a while to solve and which I had trouble finding relevant search results for. I've got it solved now, but felt like writing this up in case it helps anyone else out.

When running most go commands I tried (e.g. go mod init example/hello or go run hello.go or even something as seemingly innocuous as go doc cmd/compile when a go.mod file exists) the command would hang for a rather long time. In most cases, that was about 20~30 seconds, but in one case -- trying to get it to output the docs about the compile tool -- it took 1 minute and 15 seconds! This was on a relatively fresh Linux Mint install on old, but fairly decent hardware using golang-1.23 (installed from apt).

After the long wait, it would print out go: RLock go.mod: no locks available -- and might or might not do anything else depending on the command. (I did get documentation out after the 1min+ wait, for example.)

Now, there's no good reason I could think of why printing out some documentation or running Hello World should take that long, so I tried looking at what was going on with strace --relative-timestamps go run hello.go > trace.txt 2>&1 and found this in the output file:

0.000045 flock(3, LOCK_SH)         = -1 ENOLCK (No locks available)
25.059805 clock_gettime(CLOCK_MONOTONIC, {tv_sec=3691, tv_nsec=443533733}) = 0

It was hanging on flock for 25 seconds (before calling clock_gettime).

The directory I was running in was from an NFS mount which was using NFSv3 unintentionally. File locking does not work on NFSv3 out of the box. In my case, changing the configuration to allow it to use NFSv4 was the fix I needed. After making the change a clean Hello World build takes ~5 seconds -- and a fraction of a second with cache.

After solving it, I've found out that there are some issues related to this open already (with a different error message -- cmd/go: "RLock …: Function not implemented") and a reply on an old StackOverflow about a similiar issue from one of the developers encouraging people to file a new issue if they can't find a workaround (like I did). For future reference, those links are:

view more: next ›