Time flies!! Celebrating 10 years of Nitrokey! 🎉 Open-source security hardware made in Germany 💪 Thanks a lot to everyone who's supporting us along the journey! 🙏 We've prepared some goodies for you 😎 Check it out here:
https://www.nitrokey.com/news/2025/10-years-nitrokey%E2%80%93-decade-digital-security
Finally! Somebody solved the puzzle in full:
https://github.com/harfbuzz/harfbuzz/issues/5535#issuecomment-3491967077
After 3.5 years I have ordered a mainboard and memory upgrade for my college-aged son's #Framework 13 laptop. I was really excited by the promise of both repair and hardware upgrade support when I purchased the original Framework 13. In this regard I am very pleased with the options. We were early adopters of the 11th gen #Intel laptops and I had multiple generations of mainboard upgrades to consider at different price points.
The two downsides so far:
1) Higher cost to performance ratio. You pay a premium for the longer term hardware support. This was a known cost to buying in.
2) We did have some early adopter bugs (DP module caused display stuttering, and bios battery had a flaw causing it to not charge and eventually need a replacement). Framework support has always been helpful when needed.
Overall worth it!
Louvre robbery: Could a 50-year-old maths problem have kept the museum safe?
An audacious heist at the Louvre saw thieves make off with priceless crown jewels in broad daylight – here is how a decades-old geometry problem can help museums boost their security.
By Kit Yates
Random tip for comparing the performance of Rust and C programs that use stdout:
Rust stdout is line-buffered, even when redirecting to a file.
Glibc (and most C libraries I know of) are smarter than this, and will switch to a more aggressive buffering scheme if they aren't writing to a terminal.
Running the program _under hyperfine_ is enough to trigger this behavior, because hyperfine takes over the stdout stream. Glibc senses that this is not a terminal and turns on a 4096-byte buffer; Rust continues making one syscall per line.
So if a Rust program that prints stuff seems to lose a performance advantage over a C counterpart when run under hyperfine, it's worth stracing to check.
(There's continuing talk of fixing this default in Rust, but it's not fixed yet.)
#Google trips over its own words, when they sell you #Android it's the best computing device in the world that does everything. After you bought it Google doesn't let you do anything *you* want to.
#Sideload is a made-up term. Putting software on your computer is simply called “installing”, regardless of whether that computer is in your pocket or on your desk.
What Do You Talk About When You Talk About Sideloading?
What does Google?
Here's #FDroid: https://f-droid.org/2025/10/28/sideloading.html
OpenAI is connecting all company secrets to ChatGPT - all your work data and apps are now open | TechRadar
Can't see this going wrong...
Today in the Fonts and AI conference Nadine asked me if AI could be used for master compatibility. On reflection here is a better answer:
We're currently in a moment where tech companies have an incentive to brand everything as AI. If a big tech company made a path compatibility tool I'm sure it would have a diamond icon and sparkles and "powered by AI". I'm equally sure it would use a standard path walking algorithm underneath. 1/2
Type-X is back! This Google Chrome extension makes it easy and efficient to test local fonts on any website.
This was originally published about 5 years ago, but stopped working due to browser evolution. But recently, @googlefonts generously had @simoncozens get things working again (better than ever), and then me and @pixelambacht pitched in to do some final UX polish.
Some people dislike #RustLang macros because they think that those "paper over language deficiencies".
They're probably right, but that's ok, because macros offer us an easy way to try out extending the language before we invent new syntax.
For example, I don't think we would have the question mark postfix operator if not for the surprisingly successful `try!` macro.
So apart from the simple fact that macros *are* part of the language, they enable us to do more experimentation than a Rust-without-macros or a Rust-with-less-powerful-macros would afford us. And more experimentation means better chances to land somewhere truly amazing in the design space of new features. That's worth their complexity cost many times over.
Nitrokey
behdad
Daniel Fisher
Project Gutenberg
cliffle
F-Droid
Dave nλ=2dsinθ
Simon Cozens
Stephen Nixon
llogiq