00:58:40 nsITobin: wanted to do too much today, didn't manage to do much, might go check that magical box with moving pictures soon 00:58:58 trying to catch up with IRC backlogs now 00:59:04 radio with pictures? 00:59:08 It'll never work! 00:59:10 njsg: 01:06:35 nsITobin: MPEG over radio-like signals, will never catch on 01:06:57 let's go back to lightbulb based computers 01:07:16 too tired for that, I'll go with PAL instead 01:09:41 head's up.. I likely ain't doing anything tomorrow sm related cause I gotta get gogs going and setup another xr instance 01:09:58 and get bismuth back into working order as well.. 01:11:46 Yeah background.. Small main binoc server is iridium where i hid out for a while and runs irc.. Gallium formerly Regolith is where xr is now as well as file/storage and gogs tomorrow.. bismuth is the original BinOC server of the lot and osmium is another small server which I will be using for specific development with an environment that will radically change.. this server I am suing to develop Project Neptune. 01:12:35 that is what I have at my disposal 01:13:31 bismuth and gallium are irreplaceable because I negotiated the specs when afterburst changed from OpenVZ to KVM. 01:13:53 they are WAY overpowered vs what I pay 01:14:37 njsg: I hear PAL is much friendler format than NTSC 01:14:55 ... i am gonna get shit for that one one way or another :P 01:18:31 eh, from what I've read - never seen NTSC - that sounds likely. I've been given the impression colors are a problem with NTSC (And yes, I'm aware of the "never twice the same" expansion), and I wonder if some wanted to see analog broadcasts gone sooner because of it 01:18:52 but I guess one key advantage of PAL is twice the recording time in VHS 01:29:32 njsg: you have to understand tho that the way NTSC got compatible color both had some drawbacks and had the mandate that it MUST NOT interfear with black and white transmissions.. PAL regions had the advantage of NTSC doing it first and backwards compatibility was not as much a consern 01:30:47 on a lot of notes NTSC and PAL are very similar 01:30:53 wasn't it also backwards-compatible in PAL? 01:32:08 PAL most commonly in 50hz regions got an added advntage with pal.. you can slow that down to near movie framerate whereas ntsc has to use most commonly 3 to 2 pulldown which i am not gonna look up to remember words for explaining how it works cause this is off-topic even for me lol 01:34:05 Like NTSC, PAL uses a quadrature amplitude modulated subcarrier carrying the chrominance information added to the luma video signal to form a composite video baseband signal. The frequency of this subcarrier is 4.43361875 MHz for PAL 4.43, compared to 3.579545 MHz for NTSC 3.58. The SECAM system, on the other hand, uses a frequency modulation scheme on its two line alternate colour subcarriers 4.25000 and 4.40625 MHz. 01:34:21 from wokepedia 01:36:18 i guess it was njsg it is late I should not ever .. look into how analog tv works.. it melts your brain 01:36:20 njsg: 01:37:29 yeah no i was mixing color and the line change 01:37:51 The BBC tested their pre-war (but still broadcast until 1985) 405-line monochrome system (CCIR System A) with all three colour standards including PAL, before the decision was made to abandon 405 and transmit colour on 625/System I only. 01:38:28 that got mixed up as a pal con not just a UK standard one sorry about that 01:39:54 what it must have been like when early televisions were being developed to make what is essentually a modified blown up lightbulb display pictures 01:41:59 hell even radar must have seemed like magic 01:42:04 when it got a screen 02:20:17 greetings tonymec|away 02:20:22 hows you? 02:25:55 oh yeah status meeting is tomorrow 02:26:07 so I'll be here for that lol 03:12:11 I do have ONE request .. if there comes a time when SeaMonkey hardly takes in Mozilla patches AND is thriving I want to be able to put ALL the removed nsPrefixes from the past decade back in the codebase. ;) 03:12:17 Good night seamonkey 13:30:23 hi all - I'm here for the meeting 13:31:00 hi nsITobin Rainer_Bielefeld 13:31:31 greetings frg 13:31:40 hai WG9s :) 13:32:08 nsITobin latest media cc is in current 2.53 13:32:26 hi mrnhmath 13:33:14 frg: I wonder if that is a good thing. media files that do not play in current Firefox Nightly work fine in SeaMonkey WIP 13:34:02 nsITobin ntsc picked up the nick never the same color 13:34:05 i have forced-colors done too but .. its on winders in hg lol 13:34:21 WG9s should not affect media playback 13:34:24 that pretty much completes all the user preference media queries 13:35:08 OK was a plyback issue starts find then stalls forever under firefox nightly plays find under SeaMonkey 13:35:26 Status meeting in 25 minutes: https://wiki.mozilla.org/SeaMonkey/StatusMeetings 13:35:56 frg: I was looking at libs but I failed to upgrade any all the easy ones were already updated ;) 13:36:42 hi frg 13:37:04 there are a few not so easy ones in too but overall yes 13:38:35 nss as stated is not easy updatable this cycle 13:39:38 nss is hardly the generic sec lib it used to be.. its considered too much a malluable component by mozilla proper and the office suite that uses can't remember if it is libre or open. 13:39:53 so it gets tricky 13:39:56 in my expereince 13:41:04 Status meeting in 20 minutes https://wiki.mozilla.org/SeaMonkey/StatusMeetings 13:50:06 Status meeting in 10 minutes: https://wiki.mozilla.org/SeaMonkey/StatusMeetings 13:54:41 Status meeting in 5 minutes: https://wiki.mozilla.org/SeaMonkey/StatusMeetings 13:54:43 from ieee import ieee_1003_1.sec9_3 13:54:46 hello .* 13:56:42 WG9s: are the files local or remote? if remote, are FF and SeaMonkey served the same file? any chance it's actually two different formats? 13:58:06 I have no clue it is something I shared on my faceoobk feed last week at the time Firefox nightly played it fine. I was going to re-share to a larger group and noticed it no longer plays on today's nightly 13:59:10 This is under Linux BTW 13:59:56 rsx11m: hi 13:59:59 Status meeting time - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2024-07-28 14:00:03 hi rsx11m 14:00:12 hi WG9s IanN frg 14:00:24 hi rsx11m 14:00:28 Who's taking minutes? 14:00:41 me late again 14:00:43 hi .* again 14:00:45 frg: thanks 14:00:47 Nominees for Friends of the Fish Tank? 14:01:10 nsITobin for new logbot 2 in a row 14:01:32 ++ 14:02:03 I have to thank buc for his instructions on that 14:02:20 seconded 14:02:20 oki then lts add him too 14:02:35 lets 14:02:43 :) 14:02:50 fourthed 14:02:52 what's yhe URL? 14:03:00 s/y/t/ 14:03:04 http://logbot.thereisonlyxul.org/seamonkey 14:03:22 rsx11m on the support page too 14:03:49 works ;-) 14:04:40 Action Items? 14:05:00 should I ad that to the Topic? 14:05:00 fixed the website wrt google groups 14:05:10 I was just about to say that... 14:05:29 thanks 14:05:46 Status of the SeaMonkey Infrastructure? 14:06:01 bau 14:06:07 if olk with all i will update the topic with the logbot liknk 14:06:46 WG9s: its best I believe in libera rules .. or maybe just held over custom from oldfreenode that publicly logged channels do need to indicate as such.. tho may wanna check current policy 14:07:02 I think l10n comm is still in hg? 14:07:26 (i consider this channel infrastructure) 14:08:14 fine with me either way 14:10:10 Status of the SeaMonkey Source Tree? 14:10:50 vs2022 hasn't been refreshed yet and is still busted 14:12:10 bau. The VS2022 patvhes are a bit on the backburner from my side. too many changes needed for the second issue currently. 14:12:40 Questioning if improving clang support might be more valuage .. yeah reached that point 14:12:47 valuable* 14:14:22 GCC 13 seems to produce okay builds on more modern linux.. So there is that as long as you don't run into any python problems 14:14:27 thanks WG9s 14:14:33 nsITobin still want it fixed if possible 14:14:41 frg: totally 14:15:21 Release Train 14:16:38 wanted to do 2.52.19 final backports this weekend but something else came in between 14:16:59 otherwise bau 14:17:14 Last I knew it was considered bad form and privacy issue to have a publicly accessible log without mentioning that in the topic 14:17:29 Extensions Tracking 14:18:27 I think it doesn't need to be the topic but can also be a notice. Or, if not, I think some channels did or do that. If that's allowed, it's another way in case we run into topic length limits 14:18:41 chanserv has a greeting one can set 14:19:24 e4x for-each is gone? 14:20:11 That's right Mozilla killed it.. UXP undepercated it cause of tycho forward ports 14:22:26 i don't think there's anything new on extensions 14:22:44 doesn't Martok's palefill superseed justoff's abandoned github extension? 14:22:53 or not because they now have webcomponents 14:22:59 more or less* 14:23:02 I guess justoff's one is just on hold because of some events 14:23:11 bau e4x gone long ago 14:23:12 The War. 14:23:21 that's why he isn't around anymore 14:23:59 nsITobin both are basically broken. only for reference 14:24:33 at one time I converted the github one into a jsm with a pref lol 14:25:07 might be worth taking another look at if I can find it 14:25:21 for github, might be handy to now that one can replace blob with raw for files, add .atom at the end of lists of changes, and .diff at the end of a commit URL (just mentioning this in case someone reading doesn't know and finds it useful); at least some of this works with gitlab too 14:25:37 i didn't know about .atom 14:25:41 did know about patch 14:25:49 2.Next, Feature List, Planning & Roundtable 14:26:00 bau 14:26:09 given the lack of spacing in github's file list, I'll guess they're also using the grid feature that Mastodon's web UI started using too 14:26:32 continue with wip but need to fix one patch which takes a bit longer 14:26:55 (well for github it's .atom and removing the final slash, it seems) 14:27:28 I can look into eme for you see where you are at at least 14:27:32 some point soon 14:28:50 frg: Considering a donation feature in the UI is something I have had in the back of my mind for a while.. I have some thoughts about that. 14:28:52 nsITobin tried to get it in in local builds but plugins not downloaded. 2 years ago or so. 14:30:17 frg: well that skates close to the whole.. add-ons manager area even tho it really ain't.. so not entirely unfamilar with their server responses to queries for gmp plugins.. but no promises 14:30:38 AOB 14:30:47 bau 14:31:11 blah blah blah user preference media queries for webcompat and a touch of valueadd 14:31:17 :P 14:31:57 bau here 14:32:05 Getting closer on widdling down CF's anti-service features 14:33:09 oh rsx11m yes if you would please preserve my section across meetings :) 14:33:34 sure, didn't know your prefferences, thus used the default ;-) 14:33:49 I didn't think about it so when it came up I improved it 14:34:52 The main xulorg site will be moved back to my infra as will repos to my forge and I will likely mirror on gitlab 14:34:56 that's it for me 14:37:22 next meeting in 3 weeks then, same bat channel, same bat time 14:37:28 thanks for your time today 14:37:40 It is always fun to have everyone here 14:37:54 seconded 14:38:04 August 18th? and thirded. 14:38:13 seen you then and here :) 14:38:21 ^^ that's what my calendar says 14:38:28 I have spent the last week working on trying to fix suite issue on comm-central caused by TB Bug 18732. Teh new patch i have is building now. If it works I lad it on seamokney-central-patches in gitlab 14:39:16 talking of old bugs ... :-p 14:39:19 yes, 18th I believe 14:40:08 WG9s: while I may have some .. lingering issues building sm on linux mainly cause of spotty python i can build central pretty much any time so if you want a second pair of eyes to help I can try 14:40:27 bye for now! 14:40:32 peace rsx11m 14:40:50 rsx11m: bye, cya 14:40:53 nthis is a linux 64-bit only issue if your app uses mailnews 14:42:07 they changed how new mail nitifications work in mailnews and delted the old way but it requires using TB changed version of rust and NOT the one in mozilla-central.third_party 14:42:27 WG9s: does sm on central build thunderbird rust? 14:42:46 that is what my new patch does 14:43:07 i see 14:43:58 but they have busted such that they have a mozconfig option called --enable-thunderbird-rust that is now on by default and if you disable it then you can;t build thundirbird under 64 bit linux so trying to work around the TB folks screwup 14:43:59 may I see your current patch? 14:44:17 https://www.wg9s.com/comm-central/patches/9999999-port1860654-suite-bustage.patch 14:44:29 thunderbird rust is a requirement for mailnews due to the exchange protocol 14:44:31 being added 14:44:34 if i recall 14:44:52 that happened just before esr 14:44:54 128 14:46:07 nsITobin: so then why an option to turn it off in mozconfig 14:47:11 checking 14:47:13 but the current issue ofr linux is in gnome notfications they added doing this in rust but removed the old code so now fallback 14:47:26 yeah 14:48:04 gnome notifications is a linux 64-bit only thing either way. they never got them working in linux 32-bit either way 14:48:23 oh, so GNOME now does not support IA-32? 14:48:41 no one does 14:48:51 if $majorDistro 14:48:58 no it is TB never supported gnome notifications in IA-32 14:49:23 hasn't mozilla dropped linux32 now anyway? 14:49:24 ah ok. I wonder why, it's a curious difference 14:50:31 besides IA-32, aren't there other 32-bit arches, or is everything that sees more support already mostly 64-bit-only? 14:50:47 its been a big push across the entire industry 14:51:22 so supported with non rust code before in 64-bit only. they redid so it worked with a rust version but in doing so removed the older code yet it stil tries to support doing the notification but fails suring linking because of an undefined symbol becuase neither the old nor the new way was built 14:51:26 i have a sneaking suspicion its only because the bloated broken features simply can't fitr into a 32bit address space and seemingly confirmed with bs like bigint and other openweb features 14:52:10 I think I've already seen ppc 64-bit mentioned, and there's of course amd64, what about arm? 14:52:20 that could be but fi you disable-thunderbird-rust it should revert to the old way not fail to build 14:52:38 most arm64 processors don't even come with 32bit instruction sets anymore last I read 14:52:43 what is the point of a mozconfig option that if you alter it results in build failure 14:53:23 my guess is no one cares enough to get str8 on removing a busted configure option but this is NOTHING NEW in mozilla even before modern mozilla ;) 14:53:26 what is being linked that fails? is the exchange part disabled automatically? or is that not in yet? 14:53:35 damn, I missed the meeting... 14:53:45 tomman: it was logged don't worry ;) 14:53:53 no this is just the gnome ntoifiaction that you have new mail 14:54:01 nothing to do with exchange 14:54:12 nsITobin: oh and is intel's 64-bit arch seeing any use? or did they give up on it? 14:54:13 incomplete external linkage anyone? 14:54:29 i love incomplete external linkage! 14:54:42 mrnhmath: not possible anymore without refactoring 14:54:45 njsg: RISC-V? 14:55:08 also Intel is trying to come up with x86S, AKA "let's drop real mode for good" 14:55:29 Intel has been trying to kill x86 since they created it 14:55:45 sadly i960 and Itanic never went anywhere 14:55:50 its pretty funny actually how their only real success is their biggest issue 14:56:09 OK, Itanic got a few big iron wins, but that's it 14:56:12 itanic LOL 14:56:14 BTW the bug that was finally fixed to brak this was filed over 25 years ago when the suite was the premier project 14:56:44 WG9s: it still is the premier internet application suite.. just webcompat needs some work ;) 14:57:09 I swore you typod that low bug number 14:57:12 but nop 14:57:33 just saying a 25 year old bug on the suite is marked fised when it breaks the suite and only works in THunderbird 14:57:53 well if you didn't say it I would WG9s ;) 14:58:25 if it wouldn't generate shit I'd totally put that on the bug 14:59:20 I know seems like it woupld be the ype of thing that got me bnned from bugzilla 14:59:39 Well what's a few more bans for me as of late ;) 14:59:49 but i do need bugzilla for the moment 15:00:52 *sigh* it does require dbus. but I guess that's expected, if by "KDE and GNOME integration" it means "freedesktop integration", and freedesktop probably means dbus 15:01:15 I'm surprised files can be opened using xdg-open without dbus 15:03:52 oddly edge when it doesn't know what to do with something sends it to xdg which defaults to firefox which also doesn't know what to do with something so it offers me to download the file again 15:03:58 this is a bit ridiculous 15:04:54 WG9s: your patch looks right 15:05:05 vs what I been seeing in cc 15:05:11 the fuck 15:40:24 WG9s: any build output of worth? 15:47:27 nsITobin: linux 64-bit not yest up to where it previously failed 16:04:25 nsITobin: linux-64 build comleted so I am landing the current patch in the central gitlab aptch queue now 16:05:23 yeah your patch looked good i would have been surprised if it didn't work for at least completing the build 16:06:27 of course you can't run it with mach cause its locked to jsshell firefox and thunderbird's build directories.. plus without something standing in for glue (unless you fixed it) it will at best exit instantly cause no main window was spawned 16:09:05 WG9s: I'll find my prior research and make you 2 patches to apply that will get you a basic window and can launch devtools and a patch to unblock suite from consideration by the build system. That should expand testing capabilities.. Might even be able to rig up the test suite to it 16:09:30 tho the m-c patch would have to be done locally cause well they ain't gonna take it 16:11:12 nsa diff between things done locally and things we do in our patch queue on gitlab 16:12:11 if you have something tht you want to test I ould talk to frg and wee if he wants to add it to hiw WIP queue. if not and sems worthwhile you caoud send it to me and I could try it in my nightly builds 16:14:50 The basic aspects are this: create a new independant xhtml file to spawn, set toolkit pref, patch mach to just let anything building from comm to ./mach run after that a lot is unlocked. I just been focusing more on current seamonkey because webcompat has been a bitch lately 16:18:08 may be hard to visuallize.. monday I will go on an adventure to do those .. today I have to get more BinOC infra sorted 16:19:12 and they can be PROPER hg patches WG9s cause frg_Away taught me how ;) 16:20:05 I have a stupid command i wrote called hg-header that makes up the user and date lines 16:20:45 because i find the whole dat line thing stupid because it uses the offest in the other way than everyone else does 16:22:21 so it makes no attempt to lcalize and returns the current thime in UTC or if you give it a filename as anagrument it uses the timestamp on the file 16:23:39 funny thing is the bad user line becuase not a vlid email and not a vlid date are not really an issue with hg 16:24:20 hs to do with at release time they are running the convert patches from hg to git becuase crating a git repo barfs at 16:25:28 is it setting TZ to UTC or doing something else? 16:26:21 nit realy 16:41:50 I bet not as many as you thing get the Ghostbusters reference 17:02:38 I may have some shortcomings in that department to address. I should probably call someone. 17:05:50 njsg: who you gonna call? 17:22:26 nsITobin: style="opacity:0.5"-busters 17:30:46 njsg: ;-) 17:42:45 njsg: ! 18:05:54 peace frg 18:05:57 :P 18:07:30 bb 18:29:50 https://yle.fi/a/74-20010573/64-3-240650 seems that Yle has now also became a JavaScript-only site 18:30:01 and it even detects if the browser console is open, and stops everything on the page 18:30:37 And if I try to view the article without the console open, the page turns blank after it has been rendered 18:32:52 Why are we paying taxes for this shit 18:33:53 And also the electric grid is so unstable that I had an outage again 18:44:20 Sompi: it is bitching about prefers-color-scheme from DOM i will test in my local win build after I finish reading the js console log 18:44:40 Timestamp: 7/28/2024, 1:43:24 PM 18:44:40 Error: NotSupportedError: Animation to or from an underlying value is not yet supported. 18:44:40 Source File: https://yle.fi/uutiset/assets/js/ukko/602.3982d4737cdd3cda115e.js 18:44:40 Line: 1 18:44:52 Pale Moon did some work recently on animations 18:45:05 beyond my skillset for the moment tho 18:45:12 Timestamp: 7/28/2024, 1:43:25 PM 18:45:12 Error: NS_ERROR_NOT_INITIALIZED: 18:45:12 Source File: https://cdn.jifo.co/js/dist/embed_viewer-bee5344e4f6a5d1fd688-1-webpack.js 18:45:12 Line: 1 18:45:18 Timestamp: 7/28/2024, 1:43:25 PM 18:45:18 Error: NS_ERROR_NOT_INITIALIZED: 18:45:18 Source File: https://cdn.jifo.co/js/dist/embed_viewer-bee5344e4f6a5d1fd688-1-webpack.js 18:45:18 Line: 1 18:45:37 why they did the entire layout dependent on some animations so that it crashes and burns if they are not fully supported in the browser 18:45:52 and why did they go such great lengths to prevent debugging it 18:46:02 we are paying for that stuff with our tax money 18:46:12 also can unrelatedly confirm you're not up to snuff for ATBN which hardly matters at this point i guess tho need to check update manifest requests too 18:46:15 just popped up 18:46:34 Sompi: check with the moon browser 18:46:37 if you would 18:47:03 cause it fails for me 18:47:07 let's see what it says 18:47:33 I don't have Palemoon installed, let's see if it can be found from slackbuilds 18:47:39 same not supported error for animation and webpack bullshit 18:47:55 Sompi: its fine 18:48:18 same behavior just far less css unsupported stuff but they don't support the font face directive they are using either 18:48:19 so 18:48:47 tho I think some of the css warning spew is suppressed by a pref in uxp by default 18:49:23 this animation bs is also calling webpack 18:49:36 so this site just may not EVER be available in any so called legacy browser 18:49:53 if it is that webtech i think it is 18:51:45 no its the precurser to it 18:53:02 webpack is to MSE as https://github.com/WICG/webpackage is to EME 18:53:14 the gateway the normalizer and the general model 18:53:19 before it is tightened down 18:53:54 add wasm and you have bytecode webapps in blackbox webapp whole packages. 18:55:50 Now for the kicker that ties it all together 18:56:03 these get downloaded as a single unit and read .. sound familar 18:56:23 Sompi: power outages - storm with strong winds? the impression I've got is that the grid is too vulnerable to falling trees, but maybe that's how it has to be done. I'm no power grid engineer. 18:56:24 cause to me it sounds like the original xpinstall design for xpfe apps 18:56:37 just really really crappy and abusive 18:57:33 njsg: They dug the wires underground and the electricity transfer became 5x more expensive, and that was to reduce the amount of outages... but we have now more outages than ever 18:57:51 and it would have been cheaper to just buy some UPSies 18:58:23 and no, there haven't been any storms today 18:58:23 my substation in greentown in the 2010s would fail any time there was a lightning storm 18:59:49 also they have been building those wind farms everywhere and they also cause some instability during a windy weather 19:00:18 but today the winds have been calm 19:00:29 wind farms aren't producing anything 19:00:38 Sompi: *sigh*. not good news, if it keeps being unstable. 19:01:06 and it's strange if wind power doesn't generate input, it's usually a quite good source 19:01:23 of course it doesn't produce anything if there is no wind 19:01:45 maybe somebody mistook the instructions to go to the olkiluoto turbine and instead dismantled some wind turbine for servicing? 19:02:16 ah didn't read the part about calm, yeah, no wind no power generation then 19:02:33 Sompi: Yle in general has been working for me for reading 19:02:49 but the link you posted does not load here either 19:03:08 what is that, a part of a "live" feed? Given that https://yle.fi/a/74-20010573 loads one such feed 19:03:26 anyway Sompi luckily webpack is not webpackage just extremely similar the bad news is figuring out why webpack fails is a whole other can of worms 19:03:33 what's baffling me is that I'm having trouble finding an element with an ID for each of the live feed entries 19:04:01 am I overlooking something or is there nothing that could be targeted with an achor? 19:04:14 can you link the feed directly? 19:04:15 I mean, wouldn't it be nice if this could be solved by replacing the last slash with #something? 19:04:29 nsITobin: yeah, but then how to scroll to some text in there? https://yle.fi/a/74-20010573 19:06:48 i dunno i can't even read the site 19:07:07 but yeah css animations something about nested and webpack in general are the causes 19:07:12 more specifically i dunno 19:07:20 but that's more than you knew before Sompi 19:08:29 nsITobin: there's an english section 19:08:32 wait a moment 19:09:00 http://yle.fi/uutiset/osasto/news but apparently that redirects to https://yle.fi/news 19:10:00 palemoon refuses to compile 19:10:38 I have at least once seen a page that did not load, did not investigate further, I assumed either I had botched the URL or that there had been some error when adding to the feed on Yle's side 19:11:07 but it might have failed in the same way, at least I remember no content without javascript (while Yle articles normally show without JS) 19:11:52 I do hope yle-dl still works, given how recently there was something about requiring an account to watch even the non-geo-restricted content... 19:12:57 Yle has been infiltrated by people who want to destroy it 19:13:22 what is bugging me in that URL is where is the last part coming from: https://yle.fi/a/74-20010573/64-3-240650 - I can see from the title what it ought to be and I've located it in the feed, but all there is is the feed article ID, no that sub-id or any other ID 19:14:19 Seems that they have added a message that tells the user to download Firefox or Chrome when trying to access Yle Areena with some other browser 19:14:59 and the sound is completely broken when watching those videos with Seamonkey 19:15:18 it sounds like it goes through some type of voice transformer 19:15:37 ah and they did change something, a month or so ago someone said on mastodon that a TV had stopped working with Yle, it seems it came with something that could interact with Yle but new formats or something else broke it 19:15:51 literally nothing there works with Seamonkey anymore... 19:16:10 everything worked just fine when I used it last time 19:16:14 hm, I think last time I didn't play with sound, just subtitles, next time I do try it and get it to actually work, I'll see if I remember to test audio 19:16:55 that sound problem already existed with most Finnish news sites before 19:17:29 The sound plays but the speech sounds like it goes through a voice transformer, similar that they use in some reality TV series to anonymize the sound 19:17:50 and for some reason that only happens on browsers that are not Firefox or Chrome 19:18:24 (it again makes no sense why they are doing that) 19:18:52 the sound in Seamonkey in general is fine 19:20:08 *sigh* I'm guessing this page has the feed as JSON 19:20:16 the article is there too, and I think so are others 19:20:55 Sompi: did you ever check the formats, was it getting the same audio format as firefox and chrome, or something else? 19:21:55 How do I check that, if the site completely refuses to work if some debugging tool of the browser is open? 19:23:08 Why don't they just make things simple so that it works? We are paying Yle with our tax money... Let those corporate medias do what they want but Yle should at least be accessible without JavaScript 19:23:40 I cannot even log in to Yle Areena with Seamonkey anymore, the login prompt just fills the console with JavaScript errors and unhandled exceptions 19:24:30 I can watch those live streams of linear TV channels without logging in and the sound is broken 19:26:06 well, not now, so yeah, if now it doesn't work, it's obviously going to be impossible or very difficult 19:27:19 Sompi: well, you're right that it should work, and I think this shouldn't happen, but sadly I don't think it can be addressed by the current government. 19:27:48 They are making huge cuts to Yle's budget 19:28:38 And I don't even care about it anymore, if Yle makes its content unavailable to me anyway 19:30:35 and it's mostly war propaganda and climate propaganda :( 20:05:18 sucks Sompi sorry 20:07:32 edge is offering.. suggestions again 20:07:44 i need to find an alternative or make one 20:25:06 oh yeah https://files.thereisonlyxul.org/adhoc/patches/TOP-NOBUG-nsstyle-forced-colors.patch 20:26:22 relnotes suggestion * Added preleminary support for CSS User Preference Media Queries @ Level 5 20:41:49 CSS MediaQueries Level 5 is full of stuff that has NO business being in a desktop web browser .. features of ebooks billboards strange neich devices 20:42:29 a lot of it could surely be knocked out by just returning the approerate desktop response unless we have something to tie it to. 20:59:37 some of it is already in but I dunno if it is up to level 5's requirements 21:27:14 Sompi: besides audio codecs and formats and possibly getting different content: how often do you play video with audio outside of Finnish broadcasters' websites? I mean, is it something you do often in many other sites, or do you do that rarely and is it possible it's affecting other sites too? 21:27:22 (just trying to gather more datapoints, sorry) 21:28:03 not a bad question 21:28:10 regarding local playback, if you play through the same audio stack that SeaMonkey uses, playback is fine for different kinds of audio, say, mono, stereo, 5.1? Any custom config that may impact it? 21:28:52 was seamonkey ever able to update cubeb? 21:29:00 (I ask this because I think ALSA has a somewhat versatile configuration that may come into play, and there may be different configs for different kind of channel configs) 21:29:26 (in fact, why do I recall something about the sampling rate being relevant?) 21:29:47 njsg: At least Youtube works 21:30:02 On SeaMonkey 21:30:40 But it serves a web page that has a completely different layout than the one that is served to Firefox or Chrome 21:31:56 btw, hesari, ilta-sanomat, iltalehti, I'm assuming at least the last two have articles with videos, does audio work well there? (with this I'm wondering if the problem could be some component that's mostly used for Areena-style sites) 22:22:24 njsg: The audio is similarly distorted as it is in Yle Areena 22:24:15 and what kind of audio system do you have in place? ALSA? PulseAudio? something else? A mix of more than one? 22:24:58 I don't know what Seamonkey uses 22:28:55 check about:support 22:29:00 or whatever it is 22:35:41 about:buildconfig, check for the alsa and pulseaudio options 22:36:00 isn't alsa and pulse default 22:36:41 it has alsa 22:37:00 Sompi: ideally check both, buildconfig tells you what was built and support tells you what is in use... including format and preferred sample rate 22:38:02 if firefox has some way to get this information (does it?) I'd compare to see if anything looks off. probably not relevant if it depends on the site, but still some more information 22:38:33 nsITobin: I honestly don't know for sure, I think I recall Alsa being disabled, but I think it's listed in the old versions page 22:38:43 nsITobin: been using ALSA for too long to remember :-P 22:38:51 i believe alsa cannot be disabled cause it is required for pulse 22:39:03 but i may be thinking of a change made in UXP 22:39:05 stand by 22:39:58 https://www.seamonkey-project.org/releases/legacy 22:40:07 it's been changed 22:40:15 its all feeding off cubeb backends now 22:40:28 and the mozconfigure directives are not linked or dependant 22:40:38 oh, wait, yes, cubeb is involved somehow if pulse is used 22:40:44 hey Sompi check about:buildconfig for --enable-alsa or --enable-pulse 22:40:51 rings a faint bell, wasn't there a crash because of rust versions? 22:41:32 i dunno i do know cubeb was a bitch to gett working in UXP and they reverted it for some edge case i could never reproduce 22:41:53 Aura Runtime Environment last had updatted cubeb and the ductwork 22:41:58 https://www.seamonkey-project.org/releases/legacy lists, I think, in part, the configuration of the official builds, e.g. gtk+2 was there in 2.49, I think we did talk about this some days ago? 22:42:17 yeah gtk2 is gone 22:42:55 i could clone and patch the gfx bits in and i still may do a patchset for those who would care about it.. like my self in the future lol 22:50:33 i mean hg is pretty kinda cool njsg 23:02:19 nsITobin: There is enable-alsa 23:02:34 tell njsg :P 23:02:51 njsg: 23:03:16 k maybe we should lay off the highlights for a while that is like 3 close together pings lol 23:03:18 and then in about:support it reads 23:03:24 Audio Backendpulse-rust 23:03:49 so its pulse and alsa but the rusty version 23:04:05 your speakers are getting too much rust and not enough data? 23:04:11 it is 64-bit slackware's default build 23:04:21 their build or yours 23:04:25 their 23:04:45 and its garbled somehow? 23:04:56 it's* 23:05:07 yes 23:05:13 with some websites 23:10:35 Sompi: and the system is running ALSA only? 23:10:52 weren't there cubeb environment variables that could be used to toggle a couple things? 23:15:23 hm this one mentions a setting, so maybe it is a setting and not an environment variable? https://linuxmusicians.com/viewtopic.php?t=22774 23:15:39 found a surviving Nitter instance that engages in Clownflare-esque "secure browser verification": https://nitter.poast.org/ 23:15:48 there are two 23:15:57 ...which is ironic, considering the whole purpose of Nitter: being able to use Xitter without scripts 23:15:58 at least, and yes, they now require JS *sigh* 23:16:13 but that one *hates* SeaMonkey and redirects me to a 403 23:16:14 which, yeah, that used to be nitter's key feature 23:16:27 if it is pulse-rust currently, and given alsa is enabled, if that works, then maybe trying alsa is worth a shot 23:16:32 > You do not have access to the requested resource. Sometimes this is caused by using outdated browsers, forbidden or abusive networks or other policies. Please check your link and try again. 23:16:57 all I see is "https://nitter.poast.org/.split(" 23:18:36 of course the verification script is heavily obfuscated 23:18:52 meanwhile found a thread on Mastodon complaining about js spinning wheels for *text*, and of course I offered my kind evaluation of Mastodon's own v4. 23:19:11 CLOSED WONTFIX MOVINGECOSYSTEM USECHROME 23:19:54 I refuse to use a browser that can't even identify the OS properly! :-P 23:21:31 okay, joking, the reasons are others; but I wonder how did they screw that one up 23:21:41 "nobody runs browsers on server OSes"? 23:21:59 i should stay off archive.org 23:23:34 I don't have much patience for the current approach there, but I'd seriously like to understand the decisions that were made there 23:23:44 I just went through the progression of mozilla from 2002 to 2013 23:24:23 the archival software at the wayback machine quite often is slow and won't handle something right away, but then it fails at handling these conditions appropriately, say, by telling me "scheduled for crawling" so that I know I don't need to retry 23:24:42 the main site/archive is what it is, I'm not even sure the redirect to a noscript version ever worked for me 23:25:19 and they stopped making djvu versiosn of scanned documents available, but they're still doing the processing, they just don't include the result in the archived files 23:25:40 so there's a bunch of technical questions I'm curious about 23:27:12 well I needed to see for my self if what I remember the progression of it.. the shift around from browser being a minor project to being a big project to being the reason the corp was formed and the suite was killed how the foundation was marginalized into the annoying kiddies table until many people left and were replaced mozilla.com replaces mozilla.org www-archive is kept up for no real reason except to what.. upset people .. and then I remember 23:27:13 everything after 2013. 23:27:42 thunderbird's spin off and recapture 23:27:58 it's a lot njsg 23:31:05 I honestly thought I'd be more raging mad .. but I am just kinda sad and disappointed about it and in my self.. Why couldn't I have been doing what I do much much earlier.. I learned it in the least of ideal circumstances so what is my excuse? 23:31:43 blame Boeing 23:31:49 haha 23:31:53 Sounds good. 23:31:56 Thanks tomman 23:32:48 tomman: is Boeing using javascript in their control systems? 23:37:47 WHOOP WHOOP PULL UP TERRAIN 23:38:14 well, at least I know whatever software runs on their control units on board is still using good ol' 16-bit code :) 23:39:07 i don't think we started having nearly as many technical issues at airlines since they upgraded from windows 3.1 23:39:12 save one french airport 23:39:16 where 3.1 was the issue 23:39:46 replace since with until 23:39:50 then my statement will make sense 23:39:53 .. maybe 23:55:15 njsg: I have the new tagline for There is Only XUL 23:55:22 "I ain't afraid of no code"