With the approaching end of the summer season and reduced Covid restrictions (replaced by empty warnings that no one is following) we suddenly have an abundance of certain group of people, who are doing whatever the fuck they please, one of those things being intentionally over the top loud when it comes to driving their vehicles. By the vague description you may have guessed that I'm speaking about motorbikers, or how I've come to call them from now on: "faggits on wheels". But how do you deal with these huggers without going Mad Max on them? Fling sticky pepper spray pellets at them? High dB directional speakers? Water canon?

For some reason this triggered me more than it would any other day: "We value your privacy" a blatten huggin' lie is what it is - if you have two shits about privacy of your visitors, you wouldn't have turkey-stuffed the website with adware and trackers to balloon the transferred data to consist 60-70% of said adware and tracker scripts. Jesus, sometimes I feel like people shouldn't have improved internet connection speeds beyond DSL ... maybe then the internet infrastructure wouldn't be drowning in artificially inflated garbage traffic. The age of streaming isn't overloading the web - unnecessarily bloated code is.

FUCK mailing lists! Fuck them to death.

They're a barely structured, convoluted, piece of shit! I fucking hate them!

Oh look! 10 search results from a mailing list "archive" with the vague error message I'm receiving! Oh look! All of them are the same question that repeats as the email got quoted on the replies! Oh look! No information was exchanged just the equivalent of "hurr-durr did you try turning it off and on again?"... no wonder the communication abruptly stops - the author probably realized how God damn dense you have to be to use a mailing list post-2000.

Admittedly I haven't upgraded my App in a while but aren't those suppose to be "Report" buttons?

By far the most annoying and disturbing thing is being constantly peppered with phonecalls and SMS by the same person over and over again, all the while working on the problem that you're being bugged about.

Anywhere... BUT home. Honestly, every time I come home it's like I leave all that out by the gardenpost.

rm -rf "specific versions of dependencies that have not been documented anywhere".tar.gz && make clean all

*Tries to build the .deb with the new versions of dependencies*

Result: get told to kindly fuck off.

... It was a fun weekend trying to hunt down the specific combination of versions to successfully build it.

Was wondering if there are any open source or free for non-commercial (would like to tinker with it / learn about it as my weekend adventure first) use projects (or approaches how to solve this) that I might not have heard of, related to what I'm about to describe....

Usually, when you got 'n' ammount of machines (be it VM's, baremetal or just a bunch of Raspberry Pis) the usual approach is to either:
1)Run them as independent machines, each serving it's own purpose;
2)Run them as independent machines but "tied together" with software configured in a cluster and featuring some sort of replication;
3)Pool them together into a "swarm"/resource pool and provision VM's across them, with resources spread across the machines;

But I here's where I started wondering: What if I had 3 identical desktop PCs with relatively decent computing power and resources allocated to each... stay with me here - I can already feel some of you writing this off completely or already preparing to answer how impossible this is... what if I was ready to sacrifice portion of the combined I/O or computing power so I could set these 3 computers up in some form of "grid computing" (2-3 machines working as one)? Are there any solutions out there that could take care of the related problems (I/O error/fault handling, fragmentation, CPU governing, timing, synchronization.... all the stuff that sane and normal people don't have to worry about because it's already been taken care of on the lowest levels of programming/computing)?

I'm also thinking about the average consumer grade x86/x86_64 and ARM architecture here, not some exclusive spacegrade architectures normally used in supercomputers.

Rant @ myself:

I should probably start creating backups of my Manjaro and just rollback when I inevitably break something again, instead of just reinstalling everything. I'm using XFS, btrfs and LVM2 for pete's sake - it's just a couple of clicks/commands!

!= rant

As my weekend adventure I decided to go ahead to shoot myself in the foot. I purged Windows 10 in favor of Fedora 28...

Up till now everything that I ran as an experiment on CentOS7 on another PC (my old, now retired, PC) seemed to work without much issues. Now that I've commited my main desktop to this, minor annoyances have grown into fairly big drawbacks that I underestimated before.

So reaching out a question to all the greybeards out there - gaming on Linux (not distro specific) ... how do you do it and/or what has been your experience with it so far? As far as I've read into it - it's possible, granted, the performance will suffer for obvious reasons of running stuff inside Wine (some people, as I've heard have mentioned the opposite acually - running in Wine has blessed them with better performance due to lower overhead) and I can accept that not everything will run on it (in exchange for the linux goodies it brings me).

That moment when you just want to say: "Just get a Mac - You're too stupid and clearly incapable of using a Windows OS". Someone who's been using Windows for years, should grasp the basic know-how to EXTRACT the god damn archive when the software specifically ASKS you to.

Whan you leave for work in the morning but halfway there remember you've left your laptop charger.

!rant Idea for malware: it launches vim in fullscreen and demands bitcoin in exchange to exit it.

Can we please stop it with the blockchains and crypto currency cow manure? It was funny as a joke at first but it's not any longer.

Assemble my own aerial drone with AI co-pilot flight asisstance (or simply just pre-defined failsafes and in-flight routines).