07:30:27 Sompi: still doesn't work. huh. I wonder what's going on 07:45:36 njsg: Their HTTP response says "server: LiteSpeed" 07:45:46 So it's not F5 this time 07:47:17 let me see if I can try via FCCN 07:48:06 https://www.litespeedtech.com/products/litespeed-web-server seems to support all chromeisms 07:49:32 also some discordism, they have a "Open Source" page there but that LiteSpeed is not actually open source 07:50:44 just to discard DNS as a possibility, is this resolving to 94.237.117.184 there too? 07:51:09 (not that it sounds incorrect, it's part of a block registered to a company with an address at Aleksanterinkatu 07:52:18 doesn't work via FCCN either, so it's also not ISP-specific 07:52:53 sorry for the off-topic, it's puzzling that it does not work, but probably completely SM-unrelated 07:53:03 Yes, it resolves to that same IP address 07:53:46 maybe they're geo-blocking, but geo-blocking a site about public transit in PKS doesn't sound like a logical move 07:54:29 pushing things forward is not about making logical moves 07:59:42 I'm curious about this, I'll see if I can test other browsers and connections here and maybe then also ask UpCloud and/or the city of Helsinki (if there's a contact for that) 08:00:11 (ha, whois only lists contacts at Elisa) 08:11:52 heh, even got an error page from the proxy I was using to try to connect 08:13:33 literally every public sector organization is breaking their websites on purpose, and they say that it is because "otherwise russians attack our sites" 08:13:46 I don't really believe the official reasoning 08:35:29 while HSL's page can be used with SeaMonkey, I'm appalled that without JS I get, what, *one* piece, apparently one of the "newsitems" in the page. nothing else? 08:36:17 some links are there, though; looking at the source, it seems to have some of the content in json? 08:37:07 reminds me when the "new" reittiopas launched, replacing the old one which IIRC worked without js, or at least was lighter (I don't recall exactly anymore), and also supported more names for places and stops 08:54:59 The new normal is that almost nothing works, even with JavaScript enabled and when using Windows and Chrome 08:55:57 kaupunkiliikenne.fi seems to work for me, for now 08:56:37 It seems to have some code that detects when the browser console is open, and everything on the page stops working 08:56:46 But when the console is closed, things start working again 08:57:20 More and more pages are becoming like that 09:01:58 why does a website for a public utility and what I think is also a public company (owned by Helsinki and Vantaa?) do *that*... 09:03:05 because some tax-funded committee somewhere has decided that it is a good thing to do 09:04:01 (that ownership info is based on fiwiki, but makes me wonder why isn't Espoo in it too? Or is the Espoo part under Länsimetro Oy?) 09:10:27 also that kaupunkiliikenne.fi website is crap 09:10:49 horizontal scrolling is restricted (probably by some CSS property) and the page does not fit on my screen 09:12:21 this is also something that is becoming very common 09:20:09 it must mean it's smartphone-ready! 09:21:12 sad how much of this could be different if just some people at specific companies did do things a bit differently and then it'd catch on and be implemented in "frameworks" and so on 09:22:01 be it graceful degradation for lack of chromeisms, or supporting non-big and non-small and/or non-high-resolution displays, or showing content without javascript 09:22:45 it seems that thanks to google there is now a push to try to "game" google's ranking in ways that make javascript-based rendering or delayed content injection a "must" 13:41:00 help 13:48:30 skejg: I am not the help you requested but I may be the help you need. What's up? 13:51:14 frg_Away: the latest patch queue do you have some specific areas you would like thrashed? 13:51:54 in testing 14:06:39 MattATobin: sorry, that was a typo :) 14:12:49 okay lol 14:23:41 MattATobin have a bigger update but not ready yet. 14:24:07 I think testing can wait till this goes in. SpiderMonkey till end of 64a1 14:32:32 well I am free to build on demand now assuming I am not otherwise occupied lol 14:34:58 what happens when sm is functionally eq to esr68? 14:36:04 should be easier to put later stuff in then 14:36:46 is 68 really a milestone in that regard, I haven't looked recently so I don't remember 14:37:58 not really. 14:38:09 oh yeah frg_Away does sm-gecko have prefers-color-scheme in? 14:38:10 But need to overcome the reformat in 65 14:38:22 I don't think so 14:38:42 ah .. what is the plugin situation? 14:39:39 is npapi important to SM? 14:40:00 npapi is 200% gone. Nothing left. 14:40:08 oh you killed it 14:40:15 murderer 14:40:17 lol 14:40:53 yeah with pleasure. This and binary add-ons are the only removals I fully concur with mozilla. 14:41:08 i disagree about binary xpcom 14:41:12 but I would 14:41:34 besides once you get static components binary xpcom kinda becomes a pain in the ass 14:42:12 does mean calendar MUST be an integrated component not loaded by extension-means tho 14:42:18 I see it more as a security risk. 14:42:50 Calendar binary components are in since 2.49. Otherwise still an add-on. 14:43:12 i see it as a security risk too cause its all still being called extensions when that term doesn't even mean what we mean it to mean.. the term mod/modification would be more apt and convey the increased sense of responsibility in the user and not on the project 14:46:46 and I would still put XUL Extensions and XPCOM security record up against activex and modern chromium bs any day 14:47:48 once most system locations for autopickup and the actually ask if this should be enabled crap happened.. the danger for bad actors with xul tech is an ecosystem problem NOT a technology problem 14:47:58 yes. things like the clipboard and new file apis are something I really don't want in. 14:49:02 and what did Mozilla do towards the end of the xul ecosystem.. allow it to become a wildwest flooded with junk jetpack extensions and always broken service-dependant extensions 14:51:09 buuut that was then.. most people forgot what they had in concept if not in practicality.. time to remind em I think 14:52:46 You do know frg_Away the closer you get to an ESR the more feasable it is to wholesale slap spidermonkey on top the codebase it gets 14:54:24 xpcom changes would break most add-on I suspect. So need to be selective 14:55:41 this would be so much easier if spidermonkey was still a seperate project 14:55:48 yes 14:57:42 damn it I am gonna need cpp skills.. ugh .. basically just write a jsapi shim that forwards to spidermonkey as a lib and the shim provides missing functionality 14:58:18 That is quite a response 14:58:24 lol 14:58:43 well something to keep on the back burner if i aquire such skills