DPA, Efficiency, MSTS, QUIC, SQlite3, VRF
As DPO (Data Protection Officer) had to arrange DPA (Data Processing Agreement) directly related to Data Protection Directive (DPD) (@ Wikipedia) updates for all contacts. - Done - Some parties use "blanket DPA" which isn't officially what GDPR requires, it's still better than nothing. There's no mutual separately signed contract, but it's mentioned as part of service agreements and it's appendixes that these are the data protection rules we are following and using for all customer, unless agreed otherwise. This greatly simplifies things, especially for smaller / cheaper projects / operations.
SQL - There was a funny case, where one query was very inefficient, it did always whole table scan to look for values. After that was noticed, then index was added and queries utilizing those indexes were implemented. But next point is ridiculous, then for several days there was on going discussion how to optimize the very a few index lookup which remained. Potentials savings ranged from 70% to 30% in and implemented potential cons. I felt somehow amused and annoyed about this. - Classic example, first it doesn't matter, and when someone notices it, then there's over optimization and effort spent on meaningless matter. - Like when you melt freezer first time in 10 years, then you'll dry it with hair dryer, to make sure there's no any moisture left in it. Or when you empty paper shredders totally overfull bin, you'll wash it with detergent and rinse and dry several times, to be sure there's no paper dust left. Duh!
Microsoft Remote Desktop Protocol / Connection (RDP/RDC) / Microsoft Terminal Service (MSTS) Fun stuff of the day. - Windows 2025 the session resumption is broken. You can't resume existing desktop session, it simply hangs.Â
Microsoft Windows Update - Absolute garbage, as expected. It's unclear what has been installed, it's unclear if something needs to be installed and so on. - Good job! - Some people say that apt is totally broken update process, but compared to Windows update, it's still advanced as bleep.
Google Sites, never ending stream of bad code. This is quite old issue, but seems to still exist. Sometimes the on screen cursor position and the rope (?) or whatever they're using to track changes on the page, used to store the page structure gets messed up. When you'll start typing on the page the text appears somewhere else, and not at the cursor position. Good job guys again. Repositioning the text input cursor won't fix the problem. Only doing page reload does. - Expert engineers... Right. - How many bugs you can fit in a little program? - MANY!
QUIC and HTTP/3 (H3) and cURL (@ daniel.haxx.se) - A very nice post. And clear indication that things are once again being made way too complicated. Doesn't surprise me at all. And there are no signs of this long standing trend being reversed or even stopped. More complexity, more bloat, more inefficient and of course way more interesting hidden surprises ang bugs and unreliable solutions due to excess complexity and bugs. I've had a few long discussions about this topic, some agree, some don't.
Bert Hubert's very nice post about SQLite3 database BUSY problem (@ berthub.eu) - Yeah, we've been there done that. It's important that transactions are handled efficiently, avoiding unnecessary locking. As well as correctly locking stuff for updates, early enough. Otherwise you'll end you with situations like in the post, deadlocks (and in good cases automatic but possibly slow) resolution or in bad cases, actual long lasting deadlock. With every database and isolation mode, you'll need to know how to do things correctly and efficiently. Some guys have been at times annoyed, when I've built test projects to confirm that the stuff absolutely works as assumed. Sometimes it does, and in many cases not. After that you'll know exactly how it should be done, and why.
Verifiable random function (VRF) (@ Wikipedia) - Interesting, I actually found something I haven't remember reading about, even if I've covered many of the related topics. Ref: - RFC 9381 - (@ rfc-editor.org), verifiable unpredictable function (VUF)
2025-10-12