12:19:55 Now even Twitter has stopped working on Seamonkey... 14:29:59 and nothing of value has been lost 14:30:06 seriously, don't use the Musknet™ 14:30:30 if you absolutely MUST READ contents on the Musknet™, use xcancel.com or any of the few surviving Nitter instances 14:30:51 I can't believe people refuse to abandon that sinking ship of hate 14:33:44 https://forum.palemoon.org/viewtopic.php?p=261490#p261490 oh gawd, Crimeflare is Crimeflaring browsers again 14:33:51 why I have this faint feeling of deja-vu? 14:34:04 14:34:31 also, "We test on production, like REAL MEN DO" 15:34:56 Sompi: for a long time I haven't even bothered, wasn't TSNFKAT broken in SeaMonkey for months already? 15:35:26 Sompi: nitter has made a comeback but given recent comments here, they're moving behind CAPTCHAs, which I assume means ECMAScript 15:37:02 tomman: 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 16:02:46 LOLOL Meta 16:03:03 the Whatsapp site blocks SeaMonkey with a misleading "Something happened" error page 16:03:09 ...and a HTTP 400 Bad Request error 16:10:22 you mean they might be teapots? 16:35:12 hm... at least in one mastodon web interface, having the find bar open seems to increase CPU activity, now am I seeing things... 16:45:56 and found my next bank account to close: Venezuela's Banco Mercantil now wants static class members 16:46:08 > SyntaxError: expected property name, got '{' 16:46:17 turns out this renders their online banking inaccessible to me 16:46:30 ...yay, it will be SO FUN to close that account 16:46:34 I hated that bank anyway 16:46:46 ...the bank that demands Chromeisms but still runs XP on their ATMs :D 17:42:49 Many web servers nowadays just return the "400 Bad Request" error when the user agent string is something else than Chrome or Firefox... 17:53:06 error codes? Who even check those these days? 17:53:12 See: Discourse's "500 OK" 18:00:31 and also now Finlex changed to the new version of the site that does not work properly if the browser is not Firefox or Chrome 18:00:48 so now no-one can read Finnish law anymore, without a non-free browser 18:01:47 I contacted Oikeusministeriö about it but seems that they just don't care 18:02:29 I sent this message to them: http://paste.dy.fi/LBy/plain 18:02:46 So they just don't care about accessibility at all 18:35:05 the law is tech illiterate 18:35:21 they only know about sending bribes, er, project investment to 3rd party contractors 18:35:52 btw, how does Seamonkey's JavaScript engine work? Does it compile everything to the native code or to a platform-independent bytecode? 18:35:56 it's like that time I had to call the banking regulator when Clownflare blocked me from my owen money 18:36:07 --own 18:36:23 Sompi: it's still Spidermoney under the hood 18:36:36 I 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 18:36:47 So even Firefox is not supported 18:36:55 ha, not even "Linux and Chrome"? 18:37:00 Nope 18:37:15 And nothing like that was mentioned in the contract when my account was created to that bank 18:37:24 Otherwise I would have chosen a different bank 18:37:37 and that's the sound of me withdrawing all of my money, closing my accounts, and leaving my cards burning at the branch doors 18:38:03 They didn't let me close my account because the service fees caused the balance to go negative 18:38:18 So I just abandoned it and hopefully it doesn't cause me problems in the future 18:38:41 They broke the contract, not me 18:39:54 tomman: 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 18:40:39 Firefox was affected 18:40:41 https://en.wikipedia.org/wiki/SpiderMonkey 18:41:03 Well, do remember that for exploiting Meltdown and friends, you need extremely targeted (and unreliable!) attacks 18:41:21 I stopped caring, live with the flow, and mitigations=off because Intel won't buy me a new PC :) 18:41:42 and on older metal, the performance loss from the mitigations CAN be noticeable 18:42:09 now, you should worry on, say, shared webhosting or VPS 18:42:26 because one of the avenues of exploitation for these CPU flaws are VMs 18:42:40 (again, extremely targeted and unreliable, but theoretically possible) 18:43:53 OK, after reading that, we're still using IonMonkey as their JIT 18:44:15 Firefox upstream moved to WarpMonkey by FF83, but it's still a JIT 18:44:19 it has always been a JIT 18:44:39 So it can use native instructions on ARM and x86 but also supports pure bytecode? 18:45:13 no, the end result is always native code, which is generated from intermediate bytecode 18:46:54 So it isn't platform-independent? 18:47:49 that's the nature of JITs - you still need a platform-dependant backend to generate the native code that the CPU ends running 18:47:54 It seems to be partly written in Rust so it cannot be platform-independent anyway 18:48:00 the intermediate bytecode CAN be platform-agnostic 18:48:19 but without a native code generator... it's useless, and you might as well fallback to a pure interpreter 22:48:11 Sompi: but did OM reply to you that they did not care, or did you not get a reply at all? 22:52:18 Sompi: 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 23:23:57 I did not get reply at all 23:29:44 it's amazing how these days e-mail starts getting less reliable once it hits MS or Gmail... 23:30:00 (so far, I'd say my experience is that MS is quite worse in this regard)