06:33:07 <tomman> good news everybody: Danbooru is unbroken!
06:33:14 <tomman> https://danbooru.donmai.us/forum_posts/206814
06:33:24 <tomman> "Should be working again, although unhiding hidden comments will still be broken on these browsers. Danbooru only officially supports mainstream browsers (Firefox/Chrome/Safari) released in the last 5 years. Other browsers usually work but are not officially supported. Please spare me the lectures about muh modern webdev bad, muh Chrome monoculture bad; I use Firefox myself and I already go...
06:33:26 <tomman> ...out of my way to support older browsers."
06:33:43 <tomman> > old browser
06:33:47 <tomman> will that myth ever die!?
06:35:01 <tomman> well, at least the jQuery flakyness is gone - I still get the bad method definition BS but at least I can now read translations again, among other usual things
06:36:06 <tomman> still, I don't get why implement newer stuff just for the sake of new, "your non-mainstream browser is old despite having already installed the latest update right now", etc
06:36:29 <tomman> at least we got the usual lecture... and a fix, instead of a CLOSED WORKSFORME WONTFIX USECHROME
06:37:56 <tomman> https://github.com/danbooru/danbooru/commit/68c92b45363bb7a267d869dc57682bf27b9822f8
06:38:43 <tomman> > The @alpinejs/morph library uses public instance fields, which is ES2022 syntax not supported in older browsers.
08:48:49 <njsg> tomman: honestly, that's a big problem in itself. people who think all but those are "old browsers" and that not supporting it = being old and outdated
08:49:59 <njsg> if anything, people using said code should really be aware that, yes, it will break or be unusable for some UAs and that, no, it doesn't mean these UAs are outdated
08:50:37 <njsg> not understanding that might be not understanding the web and web clients. and I still think it also runs counter to the purpose of the web
09:05:29 <ewong> tomman  yeah... but Stackoverflow is now broken  at least on 2.53.11)   stupid optional-chaining
09:05:39 <njsg> there's a thread in the group about attachments. The unfortunate idea of having attachments only on one part of the multipart/alternative... makes me wonder if there's an extension to explore the MIME "tree"...
09:06:14 <njsg> didn't thunderbird at least at some point *produce* such messages as well? perhaps that's when dragging-and-dropping?
18:32:42 <therube> thank you :-)
20:13:54 <WG9s> i will just comment it out so if things gor squrelly I can piut them back