Xattr, E-receipt, Olmo, Vibe Coding, Passkeys, Apps, EU
Xattr (@Wikipedia) - I had a program that generates many large files, but it has a a very few small attributes per file that are needed to be scanned for all files repeatedly. Ie expiration time. Because all of the files are hosted on ext4 / brtfs file systems, I decided to go with xattr opption user.expires which stores ctime-stamp when the file should be deleted. Of course I could have used FULL database for this and or separate .metadata file, but this is prefect example for efficient xattr and "file system as database" usage case.
E-receipt formats - Studied and checked out: UBL/PEPPOL-BIS based on the Universal Business Language (UBL) version 2.1, and it's compliant with the EU Directive 2014/55/EU and EN 16931. Yet, I haven't ever seen those used in Finland / POS business. In Finland the common e-receipt format is based on Finvoice extensions. Turning the invoice into receipt by adding a few key fields. Like extact transaction timestamp and potential card payment information according EMV standards.
Olmo 3 - Actually "open" AI models, which are fully open sourced, like Olmo 3, that's nice! Just providing "open weights model" isn't open in a sense, that everything needed to build it wasn't released and documented openly.
Vibe coding fun: File Sharing - I wrote specifications and launched my own file-sharing service because so many existing services are hard to use, nag you, have ads, impose annoying limits, or suffer from bad reputations. My solution simply saves static files and uses xattrs to store retention information. There is no need for an extra database or .metadata files—just a directory with randomly named static files, plus "share" and "cleanup" scripts. Minimalism, but functional perfectionism! It is exactly what I needed, implemented elegantly without any overhead.
X / Passkeys -Broken again. They effed it up again! X app got broken, and won't work anymore. I just can't stop loving sh17 software. Well, I'll be using X about monthly from browser, because the Android app is no screwed up. - X app seems to be quite flaky in general.
Apps - So many web aspps are trying to push their BS apps to spy more on users. I guess X goes in this category deeply. Yet this case made it hilarious, because their crappy app is so crappy, it's absolutely unusable. Mission accomplished. Needing to go through lenghty login process every time you want to use X makes sure you don't accidentially end up wasting time with such a lame service.
EU IT resilience, many national critical information systems are being moved to US Cloud subject to the US CLOUD Act and moving data outside Finland. - I'm really wondering, if nobody sees any problems with that.
EU Cloud - European Government Digitization Projects Dependent on US Hyperscalers - Did run extensive AI research report on the topic, to figuring out the tip of the iceberg of the projects. It seems that well, a lot of EU critical infrastructure / platforms are running on US Cloud. That shouldn't surprise anyone. But is that really a good idea? -
This is just minimal snippet of it summary of the summary: Critical Findings & Infrastructure Risks - Mass Exposure: 1,722+ Dutch gov sites & 9/15 ministries on Microsoft, 13M Dutch patient records (Santeon) on Azure, French/German/Italian judiciary & tax systems on AWS/Azure. - Biometric Pipeline: EU border systems (EES, ETIAS, Eurodac) aggregating 60M+ non-EU profiles are accessible to Frontex, which shares intelligence with US agencies. - Direct US Access: New "Enhanced Border Security Partnership" (2025) demands direct DHS access to EU police/biometric databases to identify "security threats." - Operational Fragility: Near-100% dependency on 3 US vendors means US sanctions or technical failure could halt EU courts, tax collection, and hospitals. - Surveillance Tools: Frontex & Europol deploy US-based Cellebrite tools to extract migrant phone data, feeding intelligence into shared US-accessible interoperable databases.
2026-05-03