If you close your eyes and imagine some text, why it looks like ai-generated?
Any conversation
a Gemma 4 a Google tulajdona, nem tรกrol mรกs adatot, csak amirลl a gรฉpen fogom a Rezsล nevลฑ OpenClaw รผgynรถkรถt kรฉrdezgetni, helyileg azt sem itt tartja, hanem a felhลnek csรบfolt infrastruktรบrรกban, ami legvalรณszรญnลฑbben valamelyik brazรญliai esลerdลben foglal helyet vagy Finnorszรกgban
Gemma 4 is owned by Google, it doesn't store any other data, except what I'll ask the OpenClaw agent named Rezsล about on the machine, it doesn't keep it locally either, but in the infrastructure mocked as the cloud, which is most likely located in a Brazilian rainforest or in Finland
Morning everyone, I've started a project to bring back "classic" era Instagram, from say the 2012 - 2013 time frame, long before it was ensh**ified.
It's nowhere near ready for public consumption, so I've closed off registrations. Right now it's mainly for me to show my photography.
halation.photos
โฆ
what?
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.
WezTerm for local and remote multiplexing really is the ideal experience - it's so much better than using zellij, tmux, zmx, and friends.. I don't think they pitch this feature hard enough on their site.
I think the in-terminal multiplexers have their place - e.g. if you need to access from mobile (no WezTerm there) or on machines where you simply don't want to install WezTerm for some reason. WezTermrm could probably eliminate that last one by packaging just the mux server.




