1,142 karma · joined October 11, 2015
We need to decouple online payment infrastructure from the duopoly/oligopoly of private corporations that control how and when users can exchange money online.
I made a tiny contribution to the ddcutil-db database when I did exactly that. My monitor wasn't supported initially, but it wasn't hard to use the utils and templates to poke around and find the correct addresses for basic settings and input switching.
It was a nice afternoon's work to get it all working.
How would the allocator know that some block is unused, short of `free` being called? Does glibc not return all memory after a `free`? Do other allocators do something clever to automatically release things? Is there just a lot of bookkeeping overhead that some allocators are better at handling?
So you might have, in a red font, the word "blue", followed by the word "green" in yellow letters. The correct response is to say out loud "red, yellow". This is hard to do when the words are in your native language. So if the words are in Russian, it's an easier task for someone who doesn't read that language, because they aren't distracted by the meaning of the word and can just see the colors.
See the example on the wiki page for reference: https://en.wikipedia.org/wiki/Stroop_effect
You'd basically draw giant triangles by visiting the vertices (or coordinating with remote team members) to control territory.
It'd be neat to see it explored more.
So the linux DisplayPort driver at least supports the feature, whether or not it's fully standardized/required.
It'll be interesting to see if/how they try to lock it down genetically, I think it's possible to make the plants unable to produce seeds, but propagation is trickier. Monsanto might have some tips for them.
Starting clean also has the benefit of knowing the prompt/history is in a clean/"known-good" state, and that there's nothing in the memory that's going to cause the LLM to get weird on me.
There are two hard problems: naming things, cache invalidation, and off-by-one errors.
If you have a Steam Controller you can do this, as long as you use the USB dongle and not Bluetooth to connect. I have the official dock with the dongle plugged into that, and the Deck wakes up with the controller just fine.