European Federalist 🇪🇺 Working on Keycloak at Red Hat. On a mission to deflate your node_modules 🎈
Upgrading An Old Espresso Machine
Recently, [Samuel Leeuwenburg] got his paws on a Francis! Francis! X1 (yes, that’s the name) espresso machine. This is the espresso machine that is mostly famous for having been in …read more
#hacking #projects
https://hackaday.com/2025/06/14/upgrading-an-old-espresso-machine/
Sovereignty-washing
https://blog.xot.nl/2025/06/18/sovereignty-washing/index.html
The solo maintainer for libxml2 is no longer accepting embargoed vulnerability reports, citing the unsustainable burden as an unpaid volunteer. Security issues will be treated like any other bug report moving forward.
https://socket.dev/blog/libxml2-maintainer-ends-embargoed-vulnerability-reports #opensource #cybersecurity h/t @joshbressers
@laurensdassen ik ben het vaak met je eens Laurens, en ik ben geen voorstander van Israël en zijn activiteiten tegen Palestina. Maar dit moest gewoon gebeuren, Iran wil nucleaire wapens, en op dit moment is een directe aanval op hun infrastructuur de beste oplossing.
Het regime in Iran onderdrukt systematisch hun bevolking, die het regime ook zat zijn, alleen hun militaire macht houd dit in stand. Alleen hun incompetentie en de wil van het volk kan een verandering tot stand brengen.
About a year ago I modded my espresso machine but I finally managed to write a post about it!
This summer we're asking the question: What if we just started using GNOME OS as our primary OS?
It's still early days for GNOME OS, but it's finally ready for wider testing by developers and early adopters, on real hardware. Join us for a 3-month challenge from today until September 1st, file and fix some issues, and win a a OnePlus 6 with Linux Mobile or a limited-edition shirt 🌈👕
https://blogs.gnome.org/tbernard/2025/06/01/summer-of-gnome-os
We're making the final preparations for the 2025 Web Engines Hackfest. This year is the biggest by far, with 150 people attending to discuss the web platform over 3 days.
Big thanks to our sponsors @igalia, @mullvadnet, Huawei & Arm who have made this event possible! 🙏
https://webengineshackfest.org/
Finally! @leaflet, the venerable lightweight JS tilemap display library, is gearing up for a 2.0.0 release! 🎉
It is 7 AM CEST. The EU citizen initiative calling for a ban on "conversion therapy" (here meaning, pseudoscientific attempts to "cure" LGBTQs) is less than 250,000 votes from success. This is astounding, the votes have like, *tripled* in a week.
The page says voting ends "May 17", and I wish I knew if that meant "at midnight tonight" or "midnight tomorrow" or what. Uh. Do you know
Germany is ~6,000 local votes from endorsing it. Are there 6,000 Germans on this website
@sima we must do our duty and write a much shitty public code as possible to train the LLMs on!
1/ Transpiling #TypeScript—which approach do you choose?
• "rootDir": "." = proj/src/lib.ts → proj/dist/src/lib.js
• "rootDir": "src" = proj/src/lib.ts → proj/dist/lib.js
@jensimmons The fact that Safari updates are tied to the operating system, and users that tend to not upgrade their systems. This makes the matrix too wide, and it is hard to test older versions of Safari when you upgrade.
@jensimmons Thanks so much for the continuation of these excellent write-ups, Jen. Keep them coming!
Join our discussion for this blog post on GitHub: https://github.com/keycloak/keycloak/discussions/39160
Observability in Keycloak 26.2 - are you doing well?
When running a central single sign on service like #Keycloak in production, you need to to understand how well the system performs and whether there is a service degradation.
In the latest Keycloak release 26.2, is is more straightforward and works without additional extensions. Read more in our latest blog post about #ServiceLevelIndicators and #Observability as well as metrics, traces, logs and dashboards.
In which I claim that a few annoying #Fediverse problems (and ATproto too) could be solved by using URI schemes the way they’re designed to be used: https://www.tbray.org/ongoing/When/202x/2025/04/16/Decentralized-Schemes
🚢 #Keycloak shipped release 26.2 today (Friday afternoon)! 🚢
Pimp your #SingleSignOn with a lot of new features. And it became even simpler to host it yourself!
* Least-privileged delegated access without service desk tickets.
* Enhanced token-exchange for accurate and narrowly scoped tokens for #zerotrust architectures.
* Pre-defined #Grafana dashboard to monitor service level indicators.
* Simplified update and configuration to increase availability.
US gov asks european suppliers to guarantee they don't do DEI.
Next: we ask US to guarantee they do fair pay, 5 weeks paid annual vacation and 1 year paid maternity leave.
The reason I get so annoyed about people pitching LLMs as a way to 'democratise programming' or as end-user programming tools is that they solve the wrong problem.
The hard part of programming is not writing code. It's unambiguously expressing your problem and desired solution. Imagine if LLMs were perfect programmers. All you have to do is write a requirements document and they turn it into a working program. Amazing, right? Well, not if you've ever seen what most people write in a requirements document or seen the output when a team of good programmers works from a requirements document.
The most popular end-user programming language in the world (and, by extension, the most popular programming language), with over a billion users, is the Calc language that is embedded in Excel. It is not popular because it's a good language. Calc is a terrible programming language by pretty much any metric. It's popular because Excel (which is also a terrible spreadsheet, but that's a different rant) is basically a visual debugger and a reactive programming environment. Every temporary value in an Excel program is inspectable and it's trivial to write additional debug expressions that are automatically updated when the values that they're observing change.
Much as I detest it as a spreadsheet, Excel is probably the best debugger that I have ever used, including Lisp and Smalltalk.
The thing that makes end-user programming easy in Excel is not that it's easy to write code, it's that it's easy to see what the code is doing and understand why it's doing the wrong thing. If you replace this with an LLM that generates Python, and the Python program is wrong, how does a normal non-Python-programming human debug it? They try asking the LLM, but it doesn't actually understand the Python so it will often send them down odd rabbit holes. In contrast, every intermediate step in an Excel / Calc program is visible. Every single intermediate value is introspectable. Adding extra sanity checks (such as 'does money leaving the account equal the money paid to suppliers?') is trivial.
If you want to democratise programming, build better debuggers, don't build tools that rapidly generate code that's hard to debug.
