Ggwave, Cloud, FCS, 1st Principle, TLS, XY Problem, Coolify

1. Gibberlink Protocol (ggwave) (@ Wikipedia) - Multi-frequency encoding with 96 distinct frequencies - For fun: Cassette Data Formats vs. GGwave - Ref: Frequency Shift Keying (FSK), Kansas City Standard (KCS) - Simple binary encoding (typically 2-level FSK)

2. Cloud Services - "'The cloud' is not just servers. 'Going to the cloud' could also mean locking into a forever sub-contractor" (@ berthub.eu) - Why don't we think in modern terms. Yet, EU's long term goals do mention "digital decade", "digital sovereignty", "strategic autonomy" and "chips act", which obviously included whole digital domain, including: the cloud and artificial intelligence (AI) services.

3. Of course there must be: Fungible Cloud Service (FCS) and Non-Fungible Cloud Service (NFCS) - FCS can be deployed to many / most of providers or self-hosted trivially and practically without any changes. And NFCS are the junk many companies are pushing, which forces you to pay them forever.

4. First Principle (@ Wikipedia) - Yeah. I'm big fan of it . Whenever I do something, I'll try to reduce it down to the basics, what's actually necessary and how to achieve it using sane amount of resources so it works reliably avoiding bloat.

5. When programmers learn to clean up their mess? - Never? - "Apache Guacamole does not have a built-in mechanism to automatically prune log data or access history from the database. This means that the database will grow indefinitely unless you implement separate cleanup processes to manage the size of these tables" - If you PUT something somewhere, you should also always ask the basic data retention questions. When and how the data gets deleted. - Duh!

6. TLS Certificates - Got sick'n'tired about TLS blah blah, discussion. 6 weeks, no progress, just blah... Nobody even seems to know, what they actually want. Only thing that's clear, is that TLS Certificates cause serious problem with delivery, trust, updates, etc. But next entry is very interesting. 

7. TLS + PAKE as PHA - I started to investigate this concept, that would it be possible to implement. I didn't even know about the RFC. But that's exactly what I was going to propose / suggest. Why no password for HTTPS? This would solve all the certificate problems I complained about above. Awesome! kw: certificate management, password, mutual server and client authentication. - Yes, I'm also aware about mTLS and TLS-PSK.

8. XY problem (@ Wikiepdia) - I can't believe I haven't linked this before. This is the root of many problem analysis cases. What's even the problem, and if we're trying to solve completely wrong problem and usually in wrong way. This is also very important to remember when working in helpdesk or asking something from AI. Should I even solve "this" problem, I'm presenting, or not. Or take one (or even more!) steps back to the root problem.

9. Coolify - Yet another orchestrator, yet I don't really have any need for it. I have small volumes, and I like doing stuff manually to maintain maximum versatility. But automatic wrapping of Python programs with Buildpacks is very nice feature. Coolify would fit very well with my normal "stack" if I would feel need for it. - Also: Dokploy, Dokku - Tested Coolify for Python + Flask + Nginx + PostgreSQL setups, seems to be very nice platform. Initial basic testing and setup done just to support future tasks, if necessary.

10. PostgreSQL (PSQL, Postgres) new async io using io_uring (@ pganalyze.com) - Absolutely awesome post. It seems that they're taking the solution one step forward from using the POSIX_FADVICE which I actually posted a few weeks ago.

11. Updated PowerShell (pwsh) to PowerShell 7.5.1 version on all key systems.

2025-02-01