10:40:34 <WG9s> captai
10:40:43 <WG9s> hmm wronk key
12:02:41 <teruna> Hello! Just a short question, what is the current status regarding Python 3.12 support for building SeaMonkey on Linux?
12:03:18 <frg_Away> teruna the gentoo maintainer is on it I think. No ETA
12:03:43 <WG9s> teruna: let me see hat pythong version i am usin
12:03:57 <frg_Away> Not 3.12 I bet
12:08:18 <WG9s> seems i am runnign 4.7.5
12:08:23 <WG9s> 2.7.4
12:08:29 <WG9s> 3.7.5
12:08:38 <WG9s> hand positioning issues
12:11:44 <teruna> frg_Away: Thanks for the info!
12:57:16 <CaptainTobin> ...
12:58:15 <nsITobin> Good morning!
12:59:41 <frg_Away> nsITobin
12:59:58 <nsITobin> Hi frg_Away did you rest well?
13:03:09 <nsITobin> also Good morning WG9s
13:05:44 <frg_Away> nsITobin more or less :)
13:10:18 <njsg> Was there a way to list certificate exceptions in the UI?
13:10:18 <WG9s> nsITobin: so Ifigured out my issue with you patches.  a coupld of tem had DOS line endings
13:12:42 <WG9s> so 1 patch weemed to have more fuzz than hg wanted to allow on an hg import and 2 of them having indorrect line endings for Linux
13:14:41 <WG9s> frg_Away: so in a patch CRLF line endings should be allowed on lines being deleted and lines being added and in context but not anywhere elsewhere in the patch file
13:14:54 <WG9s> wrong channel
13:17:28 <njsg> I'm surprised the issues are usually only with three different endings, no system is using \n\r?
13:19:43 <nsITobin> that.. shouldn't be happening
13:19:59 <nsITobin> i always use lf
13:20:04 <njsg> since when has that prevented things from happening? :-P
13:20:48 <frg_Away> nsITobin if you mail them then will end up with crlf.
13:20:57 <nsITobin> wait.. does the comm patches repo have the gitattributes set so it doesn't do line ending conversion bs?
13:20:59 <frg_Away> Maybe that caused it.
13:21:10 <nsITobin> i may not have set that globally in my vm which is why I always add it to each repo
13:21:15 <njsg> I think I use \n/LF mostly, even though I understand the semantic meaning of \r\n/CRLF. I have dealt with \r files, but perhaps only once
13:21:47 <nsITobin> https://code.binaryoutcast.com/thereisonlyxul/brineshrimp-dev/src/TRUNK/.gitattributes
13:21:59 <nsITobin> i use that
13:22:08 <nsITobin> to avoid this mess in case global setting isn't set
13:22:12 <frg_Away> In git it is 	autocrlf = false I think
13:22:39 <nsITobin> i think so
13:23:00 <nsITobin> I add the .gitattributes so others don't have to deal with it either .. so bad assumption sorry
13:23:41 <nsITobin> I do not use windows line endings except in batch files
13:49:58 <Sompi> Yle's news articles have now been completely broken on Seamonkey for some time
13:50:10 <Sompi> Pictures don't load and the console is full of javascript errors
13:50:38 <Sompi> Seems that the site just doesn't work without JavaScript
14:09:22 <njsg> no taas?
14:10:14 <njsg> Sompi: when you say it doesn't work without javascript do you mean it doesn't work when javascript is disabled or do you mean it fails because of the errors?
14:10:46 <njsg> Sompi: also, can you share a link that fails for you? https://yle.fi/a/74-20106903 loads for me, but I may have something set up for images, besides having noscript
14:11:50 <njsg> also funny that the random article I picked happens to mention liiken^Wväylävirasto, is their "customer self-service" still broken?
14:15:21 <Sompi> some articles seem to work, but some don't load pictures
14:15:34 <Sompi> njsg: everything is still broken and only becomes more broken
14:19:21 <njsg> so that one does not show the text?
14:20:42 <Sompi> at least most articles show text correctly
18:51:48 <nsITobin> So had a tech out.. well not a real tech a dumb ass contractor who was really pissed to be .. awake today.. got a REAL spectrum employee coming out around 4
18:52:04 <nsITobin> upped the service to gig speed and the upstream is STILL 2-5 megabits
18:52:12 <nsITobin> supposed to be 30
18:53:50 <nsITobin> they can say oh its your stuff or network conditions when its at 60 or even 40% capcity but now its at single digit percents they MUST respond .. and again this contractor had me do every possible combination until he said "well it doesn't seem to be an issue inside but I am not qualified to do anything outside so .. bye"
18:54:42 <nsITobin> now we had the guy just across the way say he had the same things.. so I am gonna blow this up until I get every last .. reasonable .. megabit across multiple tests
18:55:39 <nsITobin> been dealing with stuff for 3 days
18:56:32 <nsITobin> yeah I shall get this resolved to an acceptable degree one way or another.. this is 2 days of work spectrum has cost me and its even worse now than it was yesterday
18:57:54 <nsITobin> I am so sorry this has impacted you guys especially WG9s
19:01:34 <tomman> another day, another dance of devtools and threats with Clownflare
19:23:59 <nsITobin> https://ibb.co/DGG7RLy
19:25:26 <nsITobin> but from test to test it can be barely 20kibs to 30 megabits connections are somewhat unsteady ... packet loss .. long ping times..
19:25:36 <nsITobin> right now its steadyish
19:25:39 <nsITobin> but
19:26:02 <nsITobin> 3mb with stalls and discons is about average
19:27:35 <nsITobin> might even be related to my issues with heptapod
19:27:43 <nsITobin> cloning
19:29:06 <nsITobin> on the bright side I bought some candy corn I am enjoying
19:32:15 <nsITobin> the autum mix actually has the pumkins and the yellow bottom and brown bottom candycorn.. and that just sounds wrong somehow
19:32:42 <nsITobin> made with real honey
21:46:20 <njsg> sigh, I'm not happy about how some ISPs will go to lengths to make sure it's hard to get issues addressed
21:48:15 <njsg> always reminds me of having to convey the very simple information "astonishingly low SNR" to them, that indicated a problem on their side (ADSL over POTS). they wanted to know the modem model.
21:49:03 <njsg> that was hardly the only issue I had with that one.
22:28:29 <Sompi> https://www.iltalehti.fi/kotimaa/a/29e0ed4e-115a-4fd9-acd0-69cedf2d467e
22:28:34 <Sompi> errors in console
22:58:20 <nsITobin> HEY GOOD NEWS... they decided the problem was on their end
22:58:37 <nsITobin> 2-3 business days and it should be fixed if not call back...
22:59:46 <nsITobin> what an aweful experience.. a dozen people and 2 techs and only 2 reps and this second tech didn't treat me like I was stupid or a liar
23:00:32 <nsITobin> njsg: yeah I had dsl once
23:00:39 <nsITobin> it was around IPv6 test day
23:01:02 <nsITobin> the comcast dns cache was poisoned and i contracted a piddly piece of malware that was easy to clean up but still..
23:01:28 <nsITobin> sorry att
23:01:35 <nsITobin> comcast is a whole DIFFERENT topic
23:01:36 <nsITobin> lol
23:02:11 <nsITobin> idc if i have to update the patch queue by USB stick in the post.. nothing shall stop me from contributing