Not an issue.

My core email is still postfix and dovecot and has been for a long time now. There is extra stuff to support dkim, spf, mta-sts, cert renewals, spam, abuse etc. We use native imap clients. No webmail or calendaring or integration with office/document stuff. Run a totally separate system for end to end encrypted messaging, group chat etc. Not really big into the self hosting thing except as a means to an end. Less is more for me but mail isn't much of a hassle in return for a lot of control.

Sent emails this morning using my extremely reliable self hosted system then remembered the recipients and the rest of Australia use Ronald McDonald cheeseburger emails. Not my problem.

Got no valuable secrets but if anyone wants to hire me and pay me a few million a year, stock etc I'm fine with keeping my dick in my pants. Its really not that difficult if you take your marriage and job seriously.

You can buy a serious amount of focus, discipline and keeping dick in pants for a fraction of what these CEOs take home.

I am currently running a shell built with quickshell, which is built with QtQuick with a language called QML which is like a declarative javascript for UI which can also include javascript. There is no escape. Not sure young people know how to write native UI anymore and the native desktop UI got neglected for years as all the money went into web and mobile.

There is a difference between writing a whole application in a scripting language and using it as intended for customizing the behavior.

Imagine him in a Ford Ranger. Probably disqualified.

The premieres brother and sister work for SANTOS. Obviously not a conflict of interest and I wouldn't suggest it was.

Robert Malinauskas is head of government affairs at SANTOS. Some jokers might say his brother Peter is head of SANTOS affairs in the government but I wouldn't as Peter is clearly an honorable person and I wouldn't say or imply anything defamatory about him.

Obey the road rules everyone including legal e-bikes and helmets. Rules might be fucking stupid sometimes (stop signs for bikes) but consistency is important. If a driver expects a certain behaviour, don't confuse them.

Australia is a bit behind in a lot of ways. Even in the US many states have a stop sign as yield for cyclists: https://en.wikipedia.org/wiki/Stop-as-yield but this country is going backwards in so many ways its ridiculous. It isn't just housing affordability and cost of living. They are just a symptom of nobody giving a fuck and everyone being scared to stick their neck out.

Bicycles and pedestrians both travel slow enough that they don't need lights or signs for safety. Eye contact will usually do the trick. In some places in the Netherlands they have managed to reduce car volume enough they have totally done away with signs and lights at some intersections. You move through at cycling pace and respect other people. Also some have intersections with lights for drivers only not bikes. Ofcourse we won't have any of that here ever as all our political leaders and elites are fucking useless and corrupt.

For profit ones, no, they are all bad. Local community run child and aged care is the only way to go.

But apparently not smarter than CEOs or these con artists would all fuck off.

I ran sid in serious production when I was younger and more foolish. The trick with unstable distributions is to test before you deploy and know the incompatibilities and have the fixes ready in advance. The problem is you are basically taking a snapshot approach and doing the work of the debian release system yourself and doing it half-arsed. An urgent security update comes out and you can't rush to deploy it without risking a dependency being pulled in that breaks under your config. For servers it ends up being a huge amount of work for no gain and you can actually miss out on security updates.

BTW this approach is why Valve can release Steam OS based on Arch or Google can base ChromeOS on Gentoo and release them to millions of consumers safely. They freeze updates to create a release candidate and test it and they deploy a limited subset of packages.

At home I update one arch desktop machine to work out what breaks, how to fix it and seed the package cache on our server before I do the rest and break everyone's systems. I could do the same with Sid but Arch, despite being unstable intentionally isn't all that unreliable compared with Sid though my experience with Sid is dated.

I only ever deploy and develop on Debian. Community run distros all the way. I had bad experiences with Redhat decades ago and do everything I can to avoid it or its siblings.

Debian has faults but it is often a taste thing. I like systems that give me upstream with minimal patches, like Arch. I moved to Arch on all desktops/laptops. The Debian devs repeatedly doing dumb shit with ssh patches was part of that. Arch is not unreliable but it is unstable. All that means is that software updates which aren't backwards compatible sometimes require intervention . To be clear that is not a fault with Arch but it does make it much less suitable for long hassle free server deployments. Also Arch doesn't have the Debian security announce list or maintain a stable production environment for years with backported security fixes and unnattended security updates.