by wallabra
This is a retelling of a drawing tablet Linux driver hacking journey, about how I got a budget tablet, had trouble with the generic driver, mistook where the issue was, found a better userspace driver, then realized it was miscalibrated. I close it off with potential roadmap points.
by Gustavo Rehermann (wallabra) - contact: gr.wallabra@proton.me
I'm happy that we are starting to see AI safety initiatives. I understand their problem statement. But I think they are very myopic when it comes to the extent of what it means to have AI widespread in society, not just misaligned AI, but any AI.
How about we start making AI do the parts of life we actually don't want to deal with, while we get to keep the enjoyable parts like art, writing, and trust in a meaningful and real reality, for ourselves? Or rather, how about we use it once we know it can do these things, and do them sustainably?
And, ultimately, what if the problems rightfully attributed to AI actually go much, much deeper than just the AI itself? Let's dive in.
You have a project? Cool! Do you know what you want to do next? Then don't put your hands on the keyboard yet!
Or maybe you're already halfway through one, only to realize you got lost in a big forest of what-ifs and unknowns and what-abouts and now it's gonna be a hell of a journey just to climb your way back on track.
Here's how you break down a project into tasks organically, while still affording to change directions when necessary.
| // = hello world in 6502 assembly with memory mapped linux syscalls | |
| // :author: wallabra | |
| // :email: gr.wallabra@proton.me | |
| // | |
| // literate 6502 assembly with asciidoc comments | |
| // | |
| // * uses Linux syscalls | |
| // | |
| // addresses exposed by 6502 VM:: |
| #[derive(Clone, Debug)] | |
| pub struct GroupedKey<K: Clone> { | |
| group_key: K, | |
| item_key: usize, | |
| } | |
| impl<K> GroupedKey<K> { | |
| fn new(group_key: K, item_key: usize) -> Self { | |
| Self { | |
| group_key, |
This shows how Tokio concurrency can be used inside Vizia.
Usually, Vizia expects you to create a new system thread every time you want to spawn a concurrent task (see
vizia::context::Context::spawn).
System threads are usually heavier than async concurrency, especially with a high performance library like
Tokio, so it would be desirable to be able to use both.
Fortunately, by making main into an async routine and running vizia's main event loop inside of it, it is
The DSG is a planned political & mutual aid organization which seeks to encompass as broad a range of issues and as possible. This breadth shouldn't be tackled on all at once, but gradually; starting small is good. A good and specific start would be starting as a small digital mutual aid group, with other common interests such as political outreach.
The initial stage is an embryo. From there, the organization would develop other "departments of interest", such as logistics and union relations, as we expect a slow growth of political influence and of material presence power, i.e. the ability to
| import Data.List | |
| data Letter = Found (Char) | NotFound (Char) | Dash | None deriving Eq | |
| type LetterSequence = [Letter] | |
| data Hangman = Hangman { | |
| word :: LetterSequence, | |
| tries :: Int, | |
| won :: Bool |
You need to interact (left-click) with an eastern bank booth in Varrock while possessing exactly 6,667 gold coins in your bank account (which does NOT include your backpack holdings). If you do, interacting with the booth will force a dialogue interaction with the banker behind, instead of taking you directly to the bank account screen. However, if those specific circumstances are met, and you interacted with the booth rather than the banker, there will be a hidden dialogue response option "Ask about the Lumbridge Doomsayer¹". The banker will