01:16:00 Hello does Ublock Origin Classic work on SeaMonkey 2.53.10? 01:33:10 yes 01:46:54 0123456789abcdef 14:57:37 hi 14:57:53 youtube stopped working for me 14:58:10 can still watch videos directly by going to a video but not via homepage 14:58:24 the ui just does not work, except for the player 15:03:04 downgrading my version worked 15:09:23 there have been reports that logging in changes the outcome, that using a different UA string may solve or cause it and that going via the homepage would avoid some of the problems, and somebody also mentioned there may have been an additional problem on google's side 15:10:38 but if downgrading works, maybe it's worth setting an UA override for youtube.com with the UA string of the version that works 16:31:53 Toi 16:32:43 guess he is gone was going to say if this fixes itthen comlain to youtube not to here 18:18:05 !LIST 18:18:18 guide 18:18:23 hallo 18:18:29 So... Ever since that last Seamonkey update, videos on Bitchute refuse to play. Might just be coincidence. 18:20:23 il cattivo poeta 18:23:17 TheSHADOW: have you checked the error console? 18:23:27 I can already smell the Chromeisms, but still, worth checking 18:25:03 Where's the error console? Is it "console" on the window w/ the inspector, etc? It's empty. 18:25:19 hit F12, then check the console tab 18:25:30 Okay. 18:25:53 open the console, reload the page, and check 18:26:26 Seeing a few errors. "Unreachable code after return statement", "Invalid regex group", and some connection refused messages. 18:26:43 Using the wss protocol? 18:27:16 TypeError: window.Plyr is not a constructor. 18:27:44 > invalid regex group 18:28:12 most likely named capture groups OR emoji crap :/ 18:28:31 Can someone verify this? https://www.bitchute.com/video/hstR1BEeUEc/ 18:28:52 Using 2.53.10 on Win7/64 (yeah, yeah, I know) 18:30:05 can reproduce here, 2.53.10 on Debian 10/amd64 18:30:18 not sure about the wss:// URIs 18:30:39 Anyone have an older version installed they can try with, to see if it's the update that broke it? 18:31:49 ah, WebSockets 18:32:28 my only older setup is a 2.49.5 on XP (yes, lulz) 18:32:50 the refused Websockets connection error is weird 18:33:29 tried pinging the failed server: "thefastestguninthewest.bitchute.com" 18:33:36 ...and it doesn't even resolve to an actual IP! 18:33:44 Interesting. 18:33:47 maybe the service is actually down 18:34:51 https://pastebin.com/PuKeQmkE the address doesn't resolve to a valid IP 18:35:01 tomman: seems that way! 18:35:10 the regex stuff error might be a red herring 18:35:24 const t=e.match(/^.*(?:vimeo.com\/|video\/)(?:\d+)(?:\?.*&*h=|\/)+(?[\d,a-f]+)/);return t?t.groups.hash:null 18:35:28 that's the failing regex 18:36:16 this happes some times with some dns load balancers when all the possible targets are down 18:36:22 or more precisely: /^.*(?:vimeo.com\/|video\/)(?:\d+)(?:\?.*&*h=|\/)+(?[\d,a-f]+)/ 18:36:34 ...what the hell is !? 18:37:38 ah, a named capture group 18:37:46 which is not yet supported on SeaMonkey 18:39:51 video/95601?param=foo&h=12345 matches the regex 18:40:18 so it uses the regex to extract an specific parameter from a video URI, in this case, a hash 18:40:31 tomman: so perhaps we need a fallback for we don't support this? 18:40:57 Regex stuff can't be polyfilled, right? 18:41:08 it's the second time I find a site breaking due to named capture groups 18:42:59 so seems like the named capture gorups crap needs ot have a defined error for this feature is not supported and then we need to fallback without it. 18:43:05 Anyway, with the websocket target host that is not resolving to anything, it may or may not be a reason 18:45:22 but f the host does not esolve thn a better error would be nice 18:45:29 unfortunately the named capture groups are getting more and more popular, and I can see why: it's far more readable code to refer to groups.somegroupname instead of groups(2) 18:45:45 WG9s: I bet they never tested their error handlers 18:45:58 sounds like you are correct 18:45:59 after all, network never goes down on development... or Silicon Valley 18:46:14 needs to do something better if it fails 18:46:57 https://caniuse.com/mdn-javascript_builtins_regexp_named_capture_groups 18:47:02 > Firefox 78 18:47:04 :/ 18:47:28 IE 11 doesn't support those either 18:48:10 but then, you're very unlikely to find some long-forgotten IE-only enterprisey legacy crapp using language additions from the last decade 18:48:38 Original Edge didn't supported those either, but unsurpisingly, Chredge does 18:53:55 Is there a portable seamonkey build I can use to test if the version change is what did it? 19:00:58 OK, the video actually WORKS on FF78ESR 19:01:07 the websocket connection errors are still there 19:01:11 but the video loads and plays fine 19:02:04 Interesting. 19:02:11 and FWIW, mpv+youtube-dl can also play/download the video 19:02:40 I get more or less the same warnings on Firefox and SeaMonkey, aside of the regex error 19:03:37 TheSHADOW: it was working for you on 2.53.9, right? 19:03:43 Yes. 19:03:52 and stopped working around the same time you upgraded to .10, right? 19:03:55 * TheSHADOW nods 19:03:58 sounds like a unfortunate coincidence to me: they deployed named capture groups on their regexes more or less at the same time SeaMonkey shipped .10 19:04:30 Or that's a fallback that never worked, and their server fell over. 19:04:49 Weird. 19:05:06 There is no fallback for bad regexes 19:05:17 --bad/unsupported 19:05:27 either the regex works, or you get a syntax error 19:05:49 of course, modern webdevs only "test" on latest Chrome/Firefox versions, and that's all 19:05:59 screw those of us using non-mainstream browsers 19:07:05 I hope frg_Away finds two or three clones to advance the Javascript regex stuff implementation 19:07:17 as much as I hate JS, named capture groups CAN be handy 19:12:52 * TheSHADOW tweeted at Bitchute... and may have lied a little 19:21:39 In any case, I don't watch videos on a browser if I can avoid it :) 19:22:04 mpv+youtube-dl (or these days, yt-dlp) solves the problem nicely with much better (read: less Javascript) experience 19:22:23 Unliess you want to interact/socialize with the rest of the website, in that case, good luck... 19:23:19 there's some javascript involved, I think, but it's definitely a better interface than the webapp 19:23:29 (youtube-dl) 19:25:11 as a bonus, you don't get to deal with the... wonderful experience that can be user comments on most popular video places 19:25:22 (unless if you're a masochist, or a moderator) 20:48:51 https://www.howtogeek.com/768727/microsoft-calls-firefoxs-browser-workaround-improper-will-block-it/ Microsoft, you so silly~ 20:49:04 the '90s called, they want their browser wars back 21:04:03 I'd think trying to hardcode the shell to use their browser or making it so that their browser is quicker to use would be easily seen as a no-no following the antitrust thing... 22:10:06 hi all! could i possibly get a little troubleshooting assistance? ^^; 22:18:58 is 2.53.10 the version that restores use of ISO dates in SM Mail that has kept me from upgrading past 2.49.5? 22:28:12 AleronIves Just state your problem. 22:30:52 a-865 still only allows os or locale formatting. The patch which allows "random"user formatting didn't make it. Ran out of time and didn't port it. I think buc has it in fedora so you might want to pick it from there. 22:32:59 ok, thanks. i updated from 2.49.5 to 2.53.9 on windows, and a few things didn't work right. the "recently closed tabs" and "recently closed windows" options no longer work - when i mouse over them, a single grey pixel pops up, as though the list is always empty. "restore previous session" no longer works, either. it's always greyed out 22:34:31 i updated from 2.53.9 to 2.53.10, and now my home page also no longer works. when i open the browser, i always get a blank page. i tried changing the settings to "blank page", closing seamonkey, opening it again, changing it back to showing the home page, and restarted again, but it still ignores the setting and uses about:blank instead of the home page 22:39:34 sounds like a damaged profile? 22:39:48 AleronIves: did you take a backup of your 2.49.5 profile prior to updating to 2.53.9? 22:43:09 yes, i did 22:44:01 in theory i could reinstall 2.49.5 and then replace the profile folder to get back to where i started, but i don't know how to update without breaking things again 22:47:38 any noteworthy addon you've got installed? 22:47:57 the broken homepage is indeed weird 22:48:30 and it wasn't broken in 2.53.9 22:48:59 hmmm, i've been using xpfe classic theme... perhaps it's incompatible? 22:50:30 AleronIves: there are changes that might have broken some themes between 2.53.9 and 2.53.10 22:51:25 LOL i think that was it. i used view -> apply theme to go back to seamonkey default. it restarted, and suddenly it opened up to a page i viewed a long time ago (restore previous session was in limbo?) 22:51:45 closed the browser and opened it again, and about:mozilla is back as my homepage 22:53:16 recently closed tabs and restore previous session are working again, too :D 22:54:35 broken theme is it then 22:54:50 thanks, i've gotten so used to looking at seamonkey in the netscape theme i forgot that browser updates can render themes unusable 22:54:53 ...still, why would a theme break session management? 22:56:44 my guess is it has to do with the menu itself. the go menu looks different in the default theme. perhaps the code for making the text black when an option is usable vs grey when it's disabled is to blame? or code related to skinning the popout menu for the list of closed tabs? 23:00:41 i flipped back to xpfe classic, and all the bugs came back, so it does seem to be unrelated to profile migration, thankfully. i was not looking forward to having to roll back ^^; 23:02:37 reminds me when GNOMERunner broke a bunch of stuff here too 23:02:56 sadly those platform themes are not receiving any love these days, and are dying of bitrot :/ 23:05:11 yeah i was sad when seamonkey dropped the classic theme in iirc 2.0 days 23:05:30 and the most popular classic theme for firefox doesn't work on seamonkey ._. 23:29:06 There were many changes in gecko which needed theme adjustments. Also woe moved stuff around and fixed things. It all looks mostly the same but heavily updated. Only some them authors still update SeaMonkey themes. Frank Lions thems and the pinball theme are still up to date. Others are mostly broken. 23:30:50 One of the real reasons Mozilla kicked out full themes I suspect. They didn't want to deal with the support issues any longer. Of course officially it was all for the good of mankind... The current so called themes are nothing but window dressing. 23:33:08 it's a pity seamonkey still has the "modern" netscape theme but not the classic one. i guess the demand for that look is just too low now to justify the maintenance cost 23:53:46 frg_Away: does that mean LC_TIME=en_DK still won't do the job?