15:50:09 <therube> unsupported.  https://cash.app/  while it didn't work "right", at least it worked.  now, assuming i did my UA override correctly, still rolling over to "unsupported".
15:51:10 <therube> wonder if it might (now, since UA change be a cookie issue?) - problem there is... what is the un/pw ;-)
15:58:40 <therube> cleared cookies, no help
17:09:01 <frg_Away> therube site displays. Problem with login?
17:13:56 <therube> heh. i'm not sure.  i have to see if i can come up with the login/pw to pursue this further ;-)
17:13:57 <therube> though... yesterday all was fine, today it just rolled over to https://cash.app/unsupported-browser
17:13:59 <therube> so while i can load a page like, https://cash.app/account/money, & it does ask for login, at this point, since i don't know the login, i can't tell if (having now cleared cookies) a UA change will be effective or not.  (it was not simply by adding the override.)
17:35:17 <frg_Away> therube btw. fixed the crash from yesterday just to run into the next one. Just takes a bit longer and sometimes a few reloads. crap site for sure but all shadow dom related.
17:47:47 <therube> frg_Away:  with UA (&, heh, now with login data), i can log in successfully, but then it automatically rolls over to https://cash.app/unsupported-browser.   sucks.
17:49:26 <therube> & soon, gmail is going to force me from its' "basic" email to its glorified crap UI.  i'm going to luv that!
17:49:37 <frg_Away> might be another case of if not chrome then unsupported.
17:50:35 <frg_Away> Usually it is bigint, dynamic imports and private class files these days. I am on it but call me a broken record here stating this. Slow progress.
17:51:02 <njsg> given how google operates, I'm going with «there's an usability issue somewhere and somebody internally escalated a bug and the solution found was to axe "simple html"»
17:51:23 <njsg> I might be too cynical on this, though. (re: gmail web ui)
18:01:00 <frg_Away> well they might need it to protect privacy google style with the privacy sandbox among other things :)
18:19:46 <a-865> will support for discourse forums ever happen in SM?
18:22:54 <tomman> a-865: no, as per Discourse policy
18:23:12 <tomman> Jeff and folks will keep jumping into the latest shinies ASAP
18:24:13 <tomman> I would try to convince forum operators to switch away from Discourse (or to never switch to it in first place, as it is a terrible tech hellstew, for both users and sysadmins), but... I'm afraid that ship sailed, sinked, and got hit by a falling Boeing plane
18:53:08 <a-865> tomman: could it happen for a particular discourse forum that stops upgrading from its current incarnation?
18:53:35 <tomman> a-865: difficult, as most Discourse instances are not self-hosted
18:53:54 <tomman> the "official" supported deployment way is by hiring with their partner, Digital Ocean
18:54:02 <tomman> and IIRC that stuff autoupdates (or close to it)
18:54:22 <tomman> or at least it was like that when The Daily WTF had the displeasure of using (and breaking) Discourse for their forums
18:54:58 <tomman> and selfhosting Discourse is complicated as the only other supported deployment way involves Docker
18:55:23 <tomman> it's not just "unzip this tarball somewhere in your wwwroot and run this script"
19:01:24 <a-865> # grep disc /etc/hosts
19:01:25 <a-865> 0.0.0.0 discourse.org
19:03:29 <a-865> Seems like ought to be able to work at least enough to login with an appropriate UA string, once actual support for such process exists
19:53:24 <therube> ah, just crashed. i think i loaded a MS page, or was about to, from a google search.
19:53:26 <therube> now that is certainly weird.
19:54:11 <therube> heh, that's funny.  so i have to fire up SeaMonkey to pull down a more recent build.
19:55:17 <therube> i'm on 20240104220119 currently
20:01:50 <therube> i'll have to keep an eye out for SeaMonkey RAM / memory usage (in case there might be something there) [& it's nothing anything that has been an issue, in ages, much less an actual crash, aside from yesterday, & now, today]
20:04:58 <therube> now, 20240110220002.  otherwise i'm pretty much static - in what i do, extensions & whatnot (other then i did disable Pale Fill, probably when i put in the previous build)
20:30:46 <a-865> tomman: I did try to dissuade forums.opensuse.org maintainers not to switch to discourse, but not hard enough. I had only a popgun for ammo.
20:31:21 <tomman> a-865: at least they DID something, by partially undoing Jeff's sabotage when it detects a browser not fitting The Vision™
20:31:27 <tomman> I do appreciate that, at least
20:36:49 <njsg> a-865: didn't SuSE at one point had a system that was also offering a network news interface?
20:36:56 <njsg> (or maybe it was here that I read about that?)
21:56:52 <a-865> njsg: The openSUSE forums did have NNTP interface, but I never tried to use it.