05:54:41 how do we find which mozilla-release/esr commit hash is targeted/used by a given seamonkey version ? 05:57:37 about:config points at the seamonkey git url for platform version, but since the repo is 126Mb i know it doesnt bundle mozilla.. 05:57:40 err about:buildconfig 05:58:43 ah,, i guess it's the hash in .gecko_rev.yml 06:00:45 so https://foss.heptapod.net/seamonkey/mozilla-release/-/commits/branch/default shows that there's been no commits to mozilla-release used in .16 compared to .15 so i have to figure out which of the commits in seamonkey-2.53-comm repo breaks for me 07:55:36 well, cant explain why; but setting SK_JUMPER_USE_ASSEMBLY to 0 in gfx/skia/moz.build gives me a working 2.53.16 on OpenBSD/amd64 07:58:19 ah, fscking, now i know. 09:19:57 wonderful times when now setting the UA to IE6 instead of hopefully showing a more compatible website or at least showing the same mess shows a cloudflare "you've been blocked" page... 10:27:50 gaston heptapod master is the base which is updated now and then with a new level. Patches are in https://gitlab.com/frg/seamonkey-253-patches/ which are pushed to a gitlab branch for the releases. Pretty much forked up but allows us the be flexible and fix up older things plus adding new ones fast. Not your normal software repos with a branch or two. 10:41:15 frg_Away: i've found out what was causing the issue, everything is working now 10:41:47 frg_Away: but thanks for the details, now i konw where to look the code and the git logs :) 10:43:20 gaston I saw in the log. Just did some updates already yesterday to get to a later skia but not there yet. Code is gone since around 65a1. Updated angle and few other libs to really recent levels but skia is so entangled with the source it needs special treatment. 10:45:58 gaston yeah handling the patches this way is flexible and saves much time but messy. Everything suite specific goes into central too but this will stay broken for some time or forever. Upstream mozilla source is ever changing now and I don't think for the better. 13:06:09 https://csswizardry.com/2023/01/why-not-document-write/ "because it's slow" 13:06:30 "What makes scripts slow?" 13:06:43 the whole document missed the REAL answer: JavaScript 13:11:29 https://crisal.io/words/2023/03/30/xul-layout-is-gone.html also, in other news from The Death Of XUL... 13:36:33 tomman they should have kept xul for chrome and add-on ui stuff. The current solution is just bad web crap and every add-on using its own ui. 13:40:13 Proprietary, poorly documented technology: Yeah lets use something reinventing the wheel every year. 14:07:44 butbutbut webshat everywhere™! 16:42:49 https://en.wikipedia.org/wiki/HTTP/3 does Seamonkey supports this junk? 18:37:28 tomman no http/2 support yet. If it would be me it whould vanish from this earth. All new protocols seem to be designed to not being able to block content. 18:38:52 ^http/3 21:16:03 https://news.ycombinator.com/item?id=35407420 and yet Hackernews has a hateboner on anything that isn't the latest protocols with a layer of certificate authority crapshow on top 21:16:37 they're hellbent on the death of plain HTTP and self-signed sites, because "it's only for LAN usage" and "freedom from Google" aren't valid excuses for them 21:17:00 awesome, I now need a CA to issue a cert to my router so I can manage it 21:17:11 and one to my network-connected printer 22:15:51 quic -> barf 23:05:58 WordPress.com decided not to let SeaMonkey log in. 23:06:08 Must be some Chrome stuff. idk 23:07:01 I suppose eventually HTTP/3 will be the end of text browsing too. 23:07:34 Not viewing ads, JS, autoplay garbage = BAD for GULAG profits. 23:12:36 there are many things that will lead me to quit computers forever 23:12:38 and Google is one