Finished, well you never really finish, setting up fedora + i3 on my ThinkPad X280. Such a lovely form-factor, & the full-screen/tiling approach for the 12.3" display works like a dream.
Any conversation
azรฉrt aranyos, hogy egybลl sandbox-ba kell tenni (a Virtualbox egy sandbox), hogy szรฉt ne barmoljon mindent a gรฉpen vagy a szerveren, vagy mรกshol, azรฉrt alapvetลen bรฉkรฉs kis รกllatkรกk ezek az ai chatbotok, na
It's cute because you have to put it in a sandbox right away (Virtualbox is a sandbox) so it doesn't mess up everything on the machine or the server or anywhere else, but these AI chatbots are basically peaceful little animals, right?
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. Itโs an analytics โdashboardโ so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.

