01:17:47 yay, my web hosting provider customer portal now suddenly works with SeaMonkey 01:17:57 ...and refuses to login from vanilla Firefox. WTF. 01:18:17 ...nevermind 01:18:28 the payment portal is on another webapp that does NOT work on SM 01:18:37 > SyntaxError: import declarations may only appear at top level of a module 01:18:54 > import{T as m,M as f,V as h,u as C,i as g,_ as o,p as b,c as w}from"./MainContentHeader-da3c99a6.js" 01:18:57 what the hell is this noise 01:19:10 since when JavaScript became Python?! 03:27:58 wtf is this obfuscated js nonsense. who can even read that shit? 08:36:41 nobody 08:36:52 it's a sad ongoing trend 08:37:12 you push a bunch of code that doesn't fit in a floppy, then there are probably things pointed as reasons to do this 08:37:19 be it taking less space, parsing faster 08:37:24 or, where is it 08:41:21 https://www.jwz.org/blog/2024/04/this-is-a-god-damned-war-crime/ https://cdn.jwz.org/images/2024/grab-20240404_115223.jpg 08:42:24 the reality is that obfuscated and minifed js make it much harder to support a site that uses that, at least with readable code people can see where is it failing and what needs to be done 08:43:01 I still think the world was nicer when most of this madness was also ECMAscript but as in ActionScript and the javascript for the browser was kept under check for MSIE6 compatibility 08:43:56 (but I guess I should name my JS variables _0xc0ffee?) 08:44:42 this is not a problem just with JS: many many years ago when I was trying this thing called Google+, one of the main problems was that they autogenerated it, so the CSS class names kept changing, you couldn't just have and keep CSS hacks 08:45:13 (On top of they ruining it more over time, one of the reasons why I stopped using it was probably it being resource-intensive. I guess Mastodon's web UI is the new Google+.) 08:46:28 (At least that one is more or less customizable, and has human-readable names. Sadly, they don't really care about compatibility and have broken things on at least two occasions. But to be fair the whole project would need to shift from the "let's mirror twitter" mindset, anyway...) 09:43:37 njsg, are they scared of people reverse engineering their shit and making addons like betterfacebook or socialfixer or whatever its called 09:50:25 in both cases of google+ and mastodon's web ui, probably not 09:50:52 google+ was probably just because of how it was generated, probably something resembling Google Web Toolkit where the final thing is autogenerated 09:51:17 there was surely a flaw in that the generation did not guarantee stable names, but it probably just happened to be that way because that's how the generation does it 09:51:36 same goes for mastodon in another way, they're just using bloated ways to do things, and they're more focused in "let's be like twitter" 09:52:47 there really isn't a worry about compatibility, they'll use incompatible syntax because it looks cleaner, but then the whole thing is a heavy monster that requires a lot of RAM and CPU. But it doesn't lock people out of Mastodon because it allows other clients. It's just that the official web-based client is a mess. 09:53:29 the thing is full of usability issues, and it doesn't even try to cater for tabbed browsing 09:54:19 buttons that don't look like actionable UI items at all, buttons that look like links but aren't (oh you wanted to open in a new tab!?) 09:55:25 (what's worse, I think (but I'd have to check) that some might actually react to middle click by replacing the current view, which is wonderful in a UI that goes with "endless scroll" instead of paginated views 09:55:30 ) 09:56:42 Hello all 10:00:05 njsg: is there anyone here that understands in newsgroups using seamonkey 19:36:07 just mentioning, not concerned, but a page like, https://github.com/BtbN eats SeaMonkey CPU & presumably ever increasing Mem