Mozilla foundation is a bunch of scumbags corrupt to the core

Today, I was asked to look into the reason why a user's Thunderbird did not receive any new emails, and here is what I found.

The user experienced DNS outage of their provider, and they changed server names to their IP addresses, in their email profiles, so as not to depend on the flaky DNS server. Thunderbird allowed that and did not make a fuss. Not a warning, not an error, not a pip squeak. But it stopped receiving any new emails.

Having realized that, I restarted it. When TB came back on, it asked for a password to the POP3 server. Huh? It was remembered in the profile settings. Not good enough for TB! It wants a new password even though the profile is still the same. Apparently, it saves a password for a server, not for a profile. Geniuses!

So, I feed it the password, it takes it, and receives emails under that one account but not under any more. Huh?

So, I restart the TB once more. It asks for two more passwords. And so, it gradually asked for all of them, for the user who has multiple accounts. Little by little, one account here, a couple more there. Eventually, we entered all of them. And it made no fuss whatsoever about not having any passwords whatsoever as if it was perfectly normal to have no password to the account and not get any emails. It just sat quietly and did nothing.

Dudes at Mozilla: if that is the quality of your releases, then you should shoot yourself in the temples. You likely can't because you have no guns, so please just jump out of the window because you suck as programmers. Exception handling anyone? Error dialog windows anyone? No, cool dudes do not notify users of error conditions.

Posted by: LinuxLies at 01:16 PM | No Comments | Add Comment
Post contains 324 words, total size 2 kb.

Another Linux lie: we have virtual machines

While Linus blabbers about politics, the mounting of VirtualBox shared folders has not worked, for nearly a decade. This trivial thing that should just work OOB does not, and no one gives a flying fuck. Google 'VB shared folders do not work' and you will find extensive discussions about all sorts of black magic that is required to make them work, similarly to xrdp that is supposed to work but does not.

More politics, dude! We need more politics. Who cares about stuff not working?

Posted by: LinuxLies at 03:17 PM | No Comments | Add Comment
Post contains 99 words, total size 1 kb.

Getting TREMENDOUS amounts of spam from googleusercontent.*

Apparently, Google either stopped monitoring their subscribers' activities or never has. They rent out their VMs to spammers who bombard me with emails.

You are going to tell me to report them to abuse@google.com, are you not? Of course, you are! I have. I have reported them profusely but got nowhere: the deluge never stops. So, there is a simple solution to that: block them on the firewall. The whole damn thing: googleusercontent.* domains by their /20 or whatever networks. And suddenly, silence.

Piss off, you unethical, unscrupulous global monopoly that stomps over the rest of the world.

Posted by: LinuxLies at 07:16 PM | No Comments | Add Comment
Post contains 112 words, total size 1 kb.

Debian 12 to 13 upgrade brings nothing but problems

Linus, you potty-mouthed troll. Every bloody upgrade brings problems and nothing new in return. Fix. Your. Shit. And then you will be qualified to crap on others.

Posted by: LinuxLies at 06:14 PM | No Comments | Add Comment
Post contains 45 words, total size 1 kb.

Found a bug in Linux network stack

It binds to a wrong IP address if multiple addresses are assigned to an interface. The binding obviously is done by the 1st byte of IPv4 whereas it has to be done by the complete netmask.

Linus, keep your house in order instead of blabbering on the interwebs. This is frigging 2024, and you have glaring bugs in the kernel. So much for your publicity stunt.

Posted by: LinuxLies at 04:00 PM | No Comments | Add Comment
Post contains 80 words, total size 1 kb.

Linux Torvalds opens his mouth, and my brain explodes

Ask me, and I will be the first to tell you: we have to be very careful with hostile country nationals working in our IT or contributing code to FOSS. But Linus's comment on banning Russians developers from KML are fucking insane.

Dude, if after all of the hoopla that ran circles in the West about diversity, inclusivity, multiculturalism, and other sorts of putrid shit, we begin to ban certain nation, then all of those lies have been nothing but lies.

If you are being forced, by way of legal pressure, to remove someone's authority to contribute code, then remove the code that they had been submitting. Otherwise you are making as much sense as lipstick on a pig. You've been happily committing their code to git, for decades, but now they are deemed a risk, and you not only delete them from your git but also badmouth them while still using their code. What is this if not an admission of lack of oversight over the code that goes into the kernel? I am becoming MORE concerned after your demarche than I had been before it.

If they write bad code with backdoors or landmines, then ditch that code.

If they write fine code, then ban them for the sake of compliance but be a man and do not crap on them.

Next, you allude to Finnish-Russian history. Dude, where do you draw the line? Swedes and Norsemen have been oppressing, massacring, and selling Finns to slavery, for millennia. Are they suddenly forgiven because of a few decades of political strife? Give me a break. You only proved yourself to be a pompous moron that I have been writing about, all along. Puke on you, turd!

I will repeat the permanent topic of this blog that does not and will not change: we collectively, in the West, have been behaving irresponsibly, as regards to our IT, by being too credulous towards hostile countries, and by doing so we have exposed our belly to stabs by our enemies that we witness daily. But Linus' demarche and his public statement about it are MORONIC.

Posted by: LinuxLies at 09:41 AM | No Comments | Add Comment
Post contains 371 words, total size 2 kb.

How about something positive, for a change?

VirtualBox sucks in performance. Hyper V sucks in features and user interface. But if you marry them, then you get the best of both worlds. Here's how.

Since somewhere about v. 6+ of VB, you can use Hyper V API as its back end. It supposedly automatically detects its presence and switches to it. What's in it to you?

VirtualBox guest OSs perform at about 50% rate of that on Hyper V. A VM running on VB is about half the speed of the same VM on Hyper V.

The mere presence of a Hyper V (or its role, if server OS) on Windows slows it down by about 10% in memory access and about as much in CPU computational power. Do not get me wrong! You do not slow down your PC by 20% by installing Hyper V! It only slows down by about 10% across the board.

So, by installing the new version of VB and Hyper V and by running your guest OSs in VB but on Hyper V back end, you gain about 40% performance vs. running them on VB's own back end.

Posted by: LinuxLies at 11:45 AM | No Comments | Add Comment
Post contains 201 words, total size 1 kb.

Genius degenerates rule our world

This will be my shortest post ever: Alex "The Great" Atkin UK. Nuff said.

Posted by: LinuxLies at 12:00 PM | No Comments | Add Comment
Post contains 24 words, total size 1 kb.