đŸ Archived View for gemlog.blue âș users âș BaronHK âș 1692943024.gmi captured on 2024-08-18 at 17:37:13. Gemini links have been rewritten to link to archived content
âŹ ïž Previous capture (2023-09-08)
-=-=-=-=-=-=-
I Just Call It âDiarrhea Codeâ When I Encounter a Website That Wonât Work in SeaMonkey and WASMs.
(Originally posted on Wordpress.com on August 12th, 2023)
I Just Call It âDiarrhea Codeâ When I Encounter a Website That Wonât Work in SeaMonkey.
When youâre not nice to idiots who make âModernâ stuff, like âDiarrhea Codeâ, they pretty much just ban you from everything.
Itâs âbadâ to be opposed to bloated Web sites that stick out a sign saying youâre not welcome here because theyâve made a mess and it only works in Firefox and Chromium.
The reason I call code meant for Chromium âDiarrhea Codeâ is because it reminds me of what happens to a toilet bowl after you had too much Taco Bell and Mountain Dew. Stuff goes flying everywhere, itâs nasty, it makes the paint peel off the walls. It makes the buttons melt off your shirt. And you canât wait to get rid of it.
20 years ago people began to push for what the Web is now. Binary blobs that run untrustworthy applications in your browser, too much JavaScript, HTML files that are several MB long and impossible to read that call out to this.
And they criticized people like me for writing clean, readable, markup, which was parsed, displayed, and presented to the user, over dial up modems, in a matter of seconds.
In 1999, you could right-click on my site and read the entire source code of the page. You didnât have to take my word as to what was in there. I couldnât have hidden much in there if I wanted to. HTML 3 and 4 were clean and readable by humans.
People said the situation where browsers would âforgiveâ slightly bogus tag use or the occasional typo (which I checked for) was âunacceptableâ and now you have Microsoft Azure pumping in stuff thatâs barely even code when you try to pay your electric bill with ComEd, and Chrome, Firefox, and Edge happily try to make sense of tens of megabytes of that.
Today in the GNOME room I was somewhat horrified to learn that you can make a Firefox .desktop that can handle mailto: with a Webmail âproviderâ.
I responded,
"Webmail *barf*
They all have different interfaces. Piles of JavaScript, their spam filtering is not uniformly effective, and they almost always have ads and tracking scripts, or at least whitespace where the ads are supposed to go. Consider SeaMonkey Mail.
Now if you do load Outlook in Firefox, it tries to register itself to handle mailto: *rolls eyes* with a banner that pops up. Also, I have to lie to Google about my SeaMonkey UA with a pref to make it think Iâm Thunderbird, even though the underlying Mail code IS FROM THUNDERBIRD."
Jamie Zawinskiâs âLaw of Software Envelopmentâ said that all programs expand until they can read email.
Giving mail to some garbage Web browser, which is made to run âDiarrhea Codeâ is only about the worst way you could expand something to read email.
Email belongs in a reader that supports POP3 and IMAP. Email should be text-only.
Sylpheed is a good Email program, but I doubt it could even handle GMail because of the entire OAuth debacle and needing to load a Web page to handle that, which sniffs to see if youâre âon the listâ of allegedly secure âappsâ, like Thunderbird, which just rewrote the entire GUI.
Someone already wrote why WASMs are terrible for security.
They have introduced an entire unique set of CVEs (listed in the monthly Mozilla patch updates, WASMs are roughly 10% of the attack footprint of the entire Firefox browser!) that will never stop, and theyâre on by default in Tor Browser.
If you use a Web browser to handle your mail, eventually what theyâre probably going to do is just rewrite the entire âWebâ thing into a WASM blob which is so much worse than âDiarrhea Codeâ.
It wonât even be markup and scripts anymore. Just a binary program you can run it like it is, and none of your extensions (NoScript, ublock-origin, etc.) can act on the elements as they come in.
WASM is part of the Google trap to destroy the Open Web.
Widevine (Web DRMâŠI turn it off) and WASM are the warm up band for WEI.
And why wouldnât you trust some skeevy porn or bittorrent site to send a WASM your way?
After all, Windows is a *very secure* operating system because you can just trust the operating system company that already has 95% of the total malware to make sure that WASMs canât do any harm. đ
And Mozilla can *obviously* make sure they stay in the âsandboxâ. *LOL*
Even when they do stay in the browser sandbox, they can still do a lot of damage. They can spy on the user. They can mine crypto.
Crypto Miners that load in Web pages boasted that they were early adopters of WASM and they could use the victimâs phone or laptop to mine âMoneroâ at â70% of the speed of a native programâ.
Turn it off.
Security Posers talking about âthreat modelsâ and âSecure Bootâ in the firmware are just absolutely laughable in light of all of the new threats the same people, and the companies that handle them, stuff into everything.
This is worse than ActiveX and Internet Explorer. At least all you had to do to stay safe from that was find some other browser.
Now all Mozilla does is blind copy things from Google.