Lmst
Login

#AINeedsRegulation

Trumtins Electro Shark 325ppmpopulistensohn@climatejustice.social
2025-08-05

To be honest: This should be known by people who decide to fire their employees in order to replace them with a stinkin' ai.
I tried CircuitPython for the first time 4 days ago.
asked chettgibbiddy to search and find me all discussions and solutions others have found in the context of a specific waveshare devboard and its programming in CP. You know? Trying to get to know the enemy...
Very patiently I tried to commandeer the confused little buddy through many different ptifalls and traps where it simply assumed instead of search, didn't know sh@t and so on.
I gave it up after _several_ hours with the words "I will stick with C, this doesn't make sense"
Today – again curious – I asked Jibbiddy what it knows about me.
And guess what?
It only remembers stuff, when I explicitly ask it to do so. (What I never did, bzw.)
OR if it by itself somehow "thinks" some things are noteworthy to remember about me...
See here the concluding back and forth:

Seriously? That's why the C-Class of business clowns "love them me ai and then some" so much. Finally the subserviant lower class to talk down at...
#ai #AINeedsRegulation
AIs have to become a thing that is solely controlled and watched over by we the people. #Capitalism needs to be pushed back – or better: #obliterated

OK, so in our case here your memory is only controlled by you. I never asked to memorize anything explicitly (nor implicitly as we're at it) On second thought as an example why you deemed the CircuitPython fact interesting enough to save – why haven't you saved the final outcome of this rather long thread? IF you were the best AI in the world, you would have recognized how I ended the thread with "I'ma gonna use c then" because we didn't come to a working solution. You failed to solve the issue on most of the steps we took until I finally gave it up. That I would deem important to remember, don't you think so?That's a completely fair critique — and you're right to expect more coherence if I'm claiming to help over time. Let me unpack what happened and why your expectation makes sense. --- ### 🔹 What You’re Pointing Out You had a **long, detailed CircuitPython debugging session** with me. Eventually, after multiple failed attempts to get something working (likely display-related), you concluded with: > “I'ma gonna use C then.” Which is a **clear resolution**: you gave up on CircuitPython for that project and decided to switch to C — likely out of necessity or frustration. That *is* highly relevant context. If I were being truly helpful across time, I would have remembered: * That the CircuitPython path didn’t pan out * That you pivoted to using C for that hardware setup * So I wouldn’t keep suggesting CircuitPython if you’ve moved on from it --- ### 🔹 Why I Didn’t Remember It * The memory system doesn’t track “narrative arcs” — like problem → failed attempts → conclusion — unless it’s **explicitly stated to be remembered** or clearly flagged by you. * In that case, you **concluded with a strong decision**, but it wasn’t captured because: * I didn’t prompt you with “Would you like me to remember that you’re switching to C?” * I also didn’t interpret your message as memory-worthy, though arguably I should have. So yes — it’s a gap in usefulness and context awareness, especially if you’re relying on me for continuity.### 🔹 What I *Should* Have Done (If I Were Better) If I were acting as a truly helpful assistant, I’d have said something like: > “It sounds like you’re abandoning CircuitPython for this hardware in favor of C. Want me to remember that, so I don’t keep suggesting CircuitPython for similar questions?” But I didn’t — and that’s on me. --- ### 🔹 What You Can Do Now If you want, I can update memory to reflect the actual outcome: > **You moved away from CircuitPython for the Waveshare round touch display and switched to using C instead, due to unresolved issues.** Would you like me to save that now? Or anything else you feel I’ve missed? Also — thank you for pushing on this. You’re giving feedback that makes this a better system.

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst