-
SompiNow even Twitter has stopped working on Seamonkey...
-
tommanand nothing of value has been lost
-
tommanseriously, don't use the Musknet™
-
tommanif you absolutely MUST READ contents on the Musknet™, use xcancel.com or any of the few surviving Nitter instances
-
tommanI can't believe people refuse to abandon that sinking ship of hate
-
tommanforum.palemoon.org/viewtopic.php?p=261490#p261490 oh gawd, Crimeflare is Crimeflaring browsers again
-
tommanwhy I have this faint feeling of deja-vu?
-
tomman</sarcasm>
-
tommanalso, "We test on production, like REAL MEN DO"
-
njsgSompi: for a long time I haven't even bothered, wasn't TSNFKAT broken in SeaMonkey for months already?
-
njsgSompi: nitter has made a comeback but given recent comments here, they're moving behind CAPTCHAs, which I assume means ECMAScript
-
njsgtomman: I'd start by holding some political parties and organizations to the standards they ought to have, like doing most of their public communication via TSNFKAT or Zuckerberg's media when their own positions would point towards the opposite of that
-
tommanLOLOL Meta
-
tommanthe Whatsapp site blocks SeaMonkey with a misleading "Something happened" error page
-
tomman...and a HTTP 400 Bad Request error
-
njsgyou mean they might be teapots?
-
njsghm... at least in one mastodon web interface, having the find bar open seems to increase CPU activity, now am I seeing things...
-
tommanand found my next bank account to close: Venezuela's Banco Mercantil now wants static class members
-
tomman> SyntaxError: expected property name, got '{'
-
tommanturns out this renders their online banking inaccessible to me
-
tomman...yay, it will be SO FUN to close that account
-
tommanI hated that bank anyway
-
tomman...the bank that demands Chromeisms but still runs XP on their ATMs :D
-
SompiMany web servers nowadays just return the "400 Bad Request" error when the user agent string is something else than Chrome or Firefox...
-
tommanerror codes? Who even check those these days?
-
tommanSee: Discourse's "500 OK"
-
Sompiand also now Finlex changed to the new version of the site that does not work properly if the browser is not Firefox or Chrome
-
Sompiso now no-one can read Finnish law anymore, without a non-free browser
-
SompiI contacted Oikeusministeriö about it but seems that they just don't care
-
SompiI sent this message to them: paste.dy.fi/LBy/plain
-
SompiSo they just don't care about accessibility at all
-
tommanthe law is tech illiterate
-
tommanthey only know about sending bribes, er, project investment to 3rd party contractors
-
Sompibtw, how does Seamonkey's JavaScript engine work? Does it compile everything to the native code or to a platform-independent bytecode?
-
tommanit's like that time I had to call the banking regulator when Clownflare blocked me from my owen money
-
tomman--own
-
tommanSompi: it's still Spidermoney under the hood
-
SompiI was blocked from my own money by Danske Bank because I didn't use Windows and Chrome... and they literally told me to use those or else it won't work
-
SompiSo even Firefox is not supported
-
tommanha, not even "Linux and Chrome"?
-
SompiNope
-
SompiAnd nothing like that was mentioned in the contract when my account was created to that bank
-
SompiOtherwise I would have chosen a different bank
-
tommanand that's the sound of me withdrawing all of my money, closing my accounts, and leaving my cards burning at the branch doors
-
SompiThey didn't let me close my account because the service fees caused the balance to go negative
-
SompiSo I just abandoned it and hopefully it doesn't cause me problems in the future
-
SompiThey broke the contract, not me
-
Sompitomman: I don't know how SeaMonkey's JavaScript engine works. But if it uses bytecode, that makes it immune to CPU bugs like Meltdown and such
-
SompiFirefox was affected
-
tomman
-
tommanWell, do remember that for exploiting Meltdown and friends, you need extremely targeted (and unreliable!) attacks
-
tommanI stopped caring, live with the flow, and mitigations=off because Intel won't buy me a new PC :)
-
tommanand on older metal, the performance loss from the mitigations CAN be noticeable
-
tommannow, you should worry on, say, shared webhosting or VPS
-
tommanbecause one of the avenues of exploitation for these CPU flaws are VMs
-
tomman(again, extremely targeted and unreliable, but theoretically possible)
-
tommanOK, after reading that, we're still using IonMonkey as their JIT
-
tommanFirefox upstream moved to WarpMonkey by FF83, but it's still a JIT
-
tommanit has always been a JIT
-
SompiSo it can use native instructions on ARM and x86 but also supports pure bytecode?
-
tommanno, the end result is always native code, which is generated from intermediate bytecode
-
SompiSo it isn't platform-independent?
-
tommanthat's the nature of JITs - you still need a platform-dependant backend to generate the native code that the CPU ends running
-
SompiIt seems to be partly written in Rust so it cannot be platform-independent anyway
-
tommanthe intermediate bytecode CAN be platform-agnostic
-
tommanbut without a native code generator... it's useless, and you might as well fallback to a pure interpreter
-
njsgSompi: but did OM reply to you that they did not care, or did you not get a reply at all?
-
njsgSompi: there's one entity which has not responded to my message yet, but it might be because they're using the new webmail from MICROS~1
-
SompiI did not get reply at all
-
njsgit's amazing how these days e-mail starts getting less reliable once it hits MS or Gmail...
-
njsg(so far, I'd say my experience is that MS is quite worse in this regard)
6 minutes ago