#39c3 .ending .. quite an enjoyable blast, and thanks to all the wonderful people just dropping by to say "thank you, it all works very nice for us"! 🥰 Certainly raised team spirits :)

This year around, apart from one #chatmail relay setup workshop we didn't do any registered events at congress. Pushing out releases, Illnesses and engagements in various other organizing prevented more public sessions. Next ones will be around #fosdem2026 where also several of us will be around. Cheers!

If you read the footer of amazon.com with a screenreader, this is what it says:

© 1996-2025, Amazon.com, Inc. or its affiliates
Test: amzn-nv-flyout-healthy-choice
Test: nav-rufus-disc-txt
Test: a-truncate-cut
Test: sp-cc-wrapper
Test: .mo-wp
Test: sp-cc
Test: .amzn-box-inner
Test: .js-order-card
Test: pldn-deep-link
Test: add-to-cart-btn
Test: amzn-nav-app-banner-container
Test: .sparkle-container


More money than God and they still can't propperly enclose their containers 😂

This entry was edited (2 hours ago)

#Catima 2.41.0 is out!

github.com/CatimaLoyalty/Andro…

This release adds support for UTF-8 barcodes (by default, the encoding will be extracted from the pkpass file or auto-detected if set otherwise).

It also contains some bugfixes and UI tweaks.

Due to Google dropping Android 5 compatibility in their libraries, this will be the last release available for Android 5.

Coming soon to an app store near you.

#IzzyOnDroid #FDroid #GitHub #GooglePlay

in reply to Sylvia

This is also the first release using Jetpack Compose, Google's "new" UI toolkit. It is only used in the About activity for now but the plan is to eventually use this in all activities instead of the old Android XML layout engine, which Google is definitely giving less priority for bugfixes and features.

I would like to specifically thank @theimpulson and @Iamlooker for helping me out so much while I was trying to wrap my head around it, your help has been amazing.

Happy new year everyone :)

My personal stance on AI over the past 6 months has slowly shifted from being very strongly opposed to much more of an optimist. I still think that so much of the hype around it is overblown, it's being shoved in all sorts of places it doesn't need to be, etc., but since I started using AI coding agents, my productivity has gone through the roof. Notice too that I didn't say speed, because honestly I think I take longer to ship code now, but productivity. I actually get more done. I spend a while writing out a good prompt, let Claude run for 20-30 minutes while I go get some food and stimulants, then spend a couple/few hours at least tweaking the code, reviewing it, testing it, etc. But I can now just throw out ideas! If I want to quickly try adding oCR to Paperback, I can tell Claude to try it, go eat, then come back, read the code, learn not what to do when I try this later, and git reset. I forgot where I heard this, and I'm paraphrasing, but the quote goes something like: "AI does not create fast experts; it makes experts faster". Can definitely say that's been my experience. A lot of these dumb tiny AI startups will probably die, I hope AI browsers go to the software graveyard, etc., but LLMs are here to stay and honestly I've come around to it. I still get queezy when thinking about what it's doing to the environment, but also, humans are doing plenty of horrible things to the earth right now that I'm not even aware of that are taking out endangered species and eliminating lifeforms that make the chemical we need to survive, so with or without LLMs we're fucked and headed for global warming. That doesn't mean I don't think we should solve the problem, but it's not the only problem either.

Re last: I absolutely love doing accessibility work with Jujutsu. Often I start with an inaccessible base and iterate my way out of the fog--fixing one accessibility issue only reveals another, and another. Git's model makes that tricky--make commits, then individually peel them off onto separate branches when it's time to merge.

With JJ on the other hand, I can stack changes one on top of the other without even thinking about it. Fix accessibility issue, jj new, fix another, jj new. It's usually obvious from jj diff what I fixed, so I can jj edit and jj describe the changes later if I'm just in the zone and don't want to workshop a commit description right now. When it's time to pick apart PRs, jj rebase -s q -s r -s s -s t -d p rebases everything on the most recent upstream change at once, then I just jj edit q and jj bookmark set <branch-name> for each change. A jj git push --allow-new pushes everything at once. When the inevitable PR feedback arrives I just jj edit <bookmark name>, make the changes, and jj git push again. No need to explicitly re-commit since that happens automatically. Then when I want my own private build with all the new a11y goodness, jj new q r s t puts me in a brand new commit with everything merged. Find a new accessibility issue with code I've edited? No problem--just edit the code live on my change, jj absorb, and it merges that code into whichever revision in my history last touched it. If it's at all ambiguous, jj squash merges the changes into an explicit target, and a jj git push updates all the affected PRs without me having to think about it.

Where has this been all my life?

miki reshared this.

Passwords. We all hear “make them strong,” but here’s the real deal: SIZE matters.

A longer password isn’t just better; it’s exponentially harder to crack.

Upgrade your security and better protect your digital identity:

✅️ Create strong and unique passwords.
✅️ Store them in a password manager.

Learn more here: tuta.com/blog/minimum-password…

When people say: "billionaires shouldn't exist" that isn't a call to violence. "Being a billionaire" isn't some inherent property in the way that say, skin color is.

Wealth taxation is a perfectly acceptable way of eliminating all billionaires. That doesn't mean billionaires stop being people, they just stop being billionaires.

Mastodon* is in desperate need of a rebrand and a repositioning in the minds of the general public (imo).

There's no reason why a Mastodon address couldn't come with all the cachet of a public library card, or a PBS tote bag—that is to say something that signals “I am more than just a content creation machine for a corporation.”

It could be a status symbol for all the right reasons.

*The collective brand, so much as the general public sees Mastodon as such.

MONTAR UNA COMUNIDAD ENERGÉTICA

+ Para instalar autoconsumo colectivo en tejados que no son el tuyo, entre otras posibilidades...

☀️ ¿Qué es eso de una Comunidad Energética?☀️

La figura de las comunidades energéticas son conceptualmente difíciles porque tienden a explicarse con enrevesados textos legalistas, a pesar de que el concepto es tremendamente sencillo:

👉 Una comunidad energética es un tipo de asociación o de cooperativa (gente, comercios e instituciones juntas, pero no grandes empresas) haciendo cosas sobre energía. Cosas en general.

Tú, tu primo, la dueña de la frutería del bajo del edificio de enfrente y más personas conocidas más podéis juntaros un día a tomar un café, costituiros como asociación y montar la comunidad energética. Lo cierto es que es relativamente fácil y hay muchos modelos de estatutos para hacerlo (más adelante pasaré unos cuantos), siempre y cuando tengáis en cuenta algunas normas básicas como:

1) Las grandes empresas no tienen permiso para ser asociadas o cooperativistas. Sí pueden ser proveedores de servicios o productos, pero mi consejo es que las grandes empresas queden absolutamente fuera de estos sistemas hechos por y para la gente. Si me preguntas a mí, las CE son uno de los mecanismos que existen para debilitar a las grandes empresas.

2) Las personas socias tienen una participación abierta, voluntaria y autónoma. Pueden entrar o salir a voluntad, y tienen voz y voto.

3) La prioridad son los beneficios medioambientales, económicos y sociales para sus miembros y zona donde opera. No ganancias financieras. Nadie se va a hacer rico con una comunidad energética.

Dentro hilo. 👇

in reply to Marcos M. 🚲 🇵🇸

dime si quieres que cambie algo
muchas gracias!!

lectorrecolector.wordpress.com…

in reply to vic-tor-menta 🇵🇸🏳️‍🌈🍉

El título, para joderte la slug jajajajaj

Marcos M. Euklidiadas, porfi, que para algo que tengo distinto... xD

"montar-una-comunidad-energetica-por-marcos-m-euklidiadas/" si puede ser

Luego el tema de los recursos, puedes poner el enlace a cryptpad o bajártelos y resubirlos, lo que quieras.

Pero sin compromiso, vamos, que hagas como te parezca xD

"The mistake that every investor, commentator, analyst and member of the media makes about NVIDIA is believing that its sales are an expression of demand for AI compute, when it’s really more of a statement about the availability of debt from banks and private credit."

-Ed Zitron

wheresyoured.at/the-enshittifi…

In programming, we have a nice pair of opposed acronyms:

• DRY for "Don't Repeat Yourself"
• WET for its opposite, "Write Everything Twice" (or "We Enjoy Typing")

But there's an intermediate position. The benefit of DRY, other than brevity, is that if a thing is specified just once, the specifications can't get out of sync with each other. If you can't manage that, the next best thing is to make sure the compiler or test suite _checks_ that they're in sync. You have to do more typing than you'd like, but at least you've removed the risk of an accident, which is the _most_ important thing.

(For example, in Rust, if you add a new branch to an enum and forget to update one of its match statements, the compiler complains about the one you missed.)

I feel as if there ought to be a nice intermediate acronym for that state of affairs, so you can say "Weeell, it's not as DRY as I'd like, but at least it's only MOIST." Or DAMP, or HUMID or something.

"Match Or Interpreter Spots Trouble"?
"Disallow Almost-Matching Programs"?
"Holler Unless Many Instances Dovetail"?

Not sure about any of those. The last one in particular seems especially "you resorted to a thesaurus, didn't you?".

I've got enough pending accessibility-related PRs on my Godot fork such that the editor is almost pleasant to use. Made the scene tree labeled and usable, fixed tab bar navigation so it wraps and doesn't just dump focus wherever if you mistakenly arrow past a tab border, added regions/landmarks to major editor areas so you know where you are, labeled more unlabeled weirdness.

Going to spend the next week mostly hacking on this before switching back to more "productive" work. It might be about time to start working on making the tilemap and audio editors accessible.

I have this crazy idea that it might actually be easier to rewrite and finish System Fault in Godot than to keep up with the perpetual Bevy churn, along with trying to create pathfinding and other systems entirely from scratch and without seeing the results. Even if I rewrote by hand rather than leaning on gen AI, I can drop bunches of buggy pathfinding/visibility code and just focus on the gameplay itself. I'd often said that System Fault could be done already if I could have used an actual, production-ready game engine to build it. I guess soon we'll see.

And to be clear, none of this is a slam on Bevy which has been great. It's just been a huge lift maintaining bunches of code that does what other engines do out of the box, plus keeping up with the inevitable changes caused by building on third-party libraries to make my life easier, then rebuilding when those libraries go away. Bevy will get there eventually, but not on a timeline that has me finishing this thing anytime soon.