02:52:57 WG9s: https://cdn.discordapp.com/attachments/1091572226748321833/1212229912946282538/b9b48ba481c41ff8ae010aad8d7ee7ba4016c0a81762668554395582464.png 07:32:27 and... https://i.postimg.cc/hPZqKbvR/image.png 07:32:33 good night seamonkey 11:46:57 Tobin: hi - saw the screenshot you posted. shat version of seamonkey was this? 11:53:30 What version 12:05:50 if 2.53 then best to ask IanN_Away he has been working on devtools dhanges for 2.53.19 12:07:06 if central, then still best to ask IanN_Away in the course of backporting mozilla-central changes to 2.53 he has encountered issues that reuired changes to 2.53 comm-release and most likely ran into this one and will now shat patch to apply to comm-central to avoid this issue. 12:09:07 * WG9s notices he keeps typing shat (which hi thinks is that past tense of shit) instead of what ;-) 13:05:35 https://vmst.io/@SuperSelena64/111223411210626069 oh boy, another Mastodumb instance that absolutely relies on fancy Chromeisms! 13:05:47 TypeError: Object.hasOwn is not a function emoji_utils.js:138:15 13:05:51 > emoji_utils.JS 13:05:53 WAT 13:06:37 https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/hasOwn 13:06:42 CR93+, FF92+ 14:32:29 WG9s: central 14:33:29 OK so dentral is really not expected to work only guatnteed to build that was wjat I was charged with doing. 14:34:45 but still IanN balported devtools things form central to 2.53 and had to mae adjustemnts in comm-central so he might knw how to fis your issue and pehaps will suggest a comm patch that i can bakport and add to the central gitlab patch sueue 14:34:54 off to dentist now 14:36:59 uhh.. but the thing is.. this can happen because of the few patches to make the platform open to any application, and I adapted thunderbird devtools code to operate and be able to launch any arbitrary chrome url from cli 14:37:55 i am not asking nor expecting anything to function cause I know it is all busted, I am just doing what I said I was gonna experiment with. 14:49:52 central is busted now anyway cause openpgp is required to be built for mailnews now 14:50:02 buildwise 14:51:42 basically mailnews code now depends on mail code existing specifically the enigmail component 14:51:51 and its binary deps 15:34:34 tomman: it'd help if the Mastodon official web app at least met... certain levels of quality 15:34:46 tomman: but the thing seems to be a pile of usability problems, on top of being heavy 15:34:59 All the requests for a Nitter-esque Mastodon client or frontend have been denied so far 15:35:00 it's looking like the main design goal was "twitter lookalike" 15:35:12 the closest thing I've seen is Brutaldon, which does not require JS at all 15:35:22 ...but requires having a Mastodon account, which for me is a non-starter 15:35:46 there are things like saying "gif" for what's not a gif that can be annoying but are really minimal compared to breaking the back button, having "close" buttons to cancel replies in the wrong spot 15:35:58 and they apparently broke support for news: URLs 15:37:34 tomman: my ideal approach to this would be a news-like client that'd get posts, give me the concept of read and unread, give me proper threading, and expandable and collapsable threads; now I'd use this with my account, but it should also be usable without one - unless they decided the API shouldn't make that easy, of course... 15:38:04 tomman: if you do get an account at an instance that does not require more selective JS features, that should at least enable you to load remote posts 15:38:25 (I just opened the one you linked that way) 15:38:37 A terrible replacement for Xitter, except that it's even less usable, more fragmented, with 3000 client choices (but none of them is Nitter), and of course its userbase is... special. 15:41:02 it's a shame, I think some versions ago mastodon instances actually allowed this without an account 15:41:14 it's not even tied to the remote post not being on that instance 15:41:40 mastodon.social has that post, but still insists on redirecting, even if you can see it in the endlessscroll™ view of the remote user 15:42:11 sigh, the whole thing can make a lot of interesting content available but has a heck of a... substandard official web interface. 15:50:45 tomman: that's a fancy instance, it won't let me get the post as json because "Request not signed" 15:51:25 it also does not have the patch to provide text/plain 15:51:38 I have zero interest into participating in the community, all I need is to read actual posts that people like linking to on those things because folks are too lazy these days to host a blog, much less a website 15:52:11 of course javaScript vomit makes that proposition unfeasible 15:52:41 again, Brutaldon would serve me if they had an "anonymous" mode, instead it's meant as a "barebones brutalist client" for thsoe that actually care about engaging 15:53:04 (I filed a feature request on their Giggitylab, still unanswered so far) 15:54:19 https://gitlab.com/brutaldon/brutaldon/-/issues/36 15:54:28 it seems the whole bugtracker is largely a ghost town 15:55:14 ...no wonder why: the last repo commit was 1 year ago! 15:55:23 the project looks effectively abandoned 15:56:35 something that parses json could normally work with .json at the end of the URL 15:56:38 but not with that instance. 16:00:56 also: I think mastodon 3 was perfectly capable of serving content... 16:02:38 that is not mentioned here but I think you might still find 3.x versions that just work out there: https://news.ycombinator.com/item?id=34010877 16:03:01 also, the .rss thing isn't as helpful as .json, because the latter, even if it requires something to parse, works for single posts 16:03:10 .rss only works for tags and accounts 16:04:11 (which is a neat way to follow posts on a given tag without having an account at the server you get the feed from, sadly one thing that I think also isn't available is the ability to optionally get only local posts for a given tag) 16:04:59 e.g. https://mastodon.social/tags/xul.rss 16:06:19 ... although the missing.png media attachments are a bit "uh" 17:41:58 hi 18:00:05 WG9s: hope your appointment went well 18:08:16 was just a cleaning 18:08:42 but a periodontal cleaning 18:10:31 WG9s: https://storage.binaryoutcast.com/pub/artifacts/smoverlay.tar.xz 18:11:05 basically missing parts and my reconstruction component plus a patch to m-c which should apply 18:11:30 nothing cleaned up just something to play with if you wanna slot it in 18:12:02 but does provide alt --devtools and --chrome url commandline handling 18:12:03 so 19:20:30 Greetin-- 19:20:32 k 21:01:09 tomman are you usin 2.53.19 with mastrodon? Should have hasOwn() since mid January. 21:02:54 frg_Away: https://i.postimg.cc/15z6cdtn/image.png 21:05:09 Tobin happy top review patches against central and can put them in the central queue for later or in the repo then depending on content. 21:10:40 Well you know what frg_Away now that i know it is more than theoretically possible.. 21:11:26 The other stuff in the los is probably removed or changed apis. playes description stuff and others. 21:12:06 Also e10s only so lots of changes in the frontend needed. 21:12:20 well I been thinking about that 21:12:49 and that is only if you subscribe to in-content being for both chrome and content.. 21:13:02 SeaMonkey is MOSTLY multi-window not content == ui 21:14:06 so how much e10s is gonna affect it is gonna be how closely u'd aline to current design where remoteness aside from being accounted for isn't nearly is bothersome vs say firefox or thunderbird using browsers inside of browsers inside of browsers until html iframe can do the same jorb 21:14:17 least that is how it seems right now 21:15:57 I really need 1 windows per component ctrl+1 to +5 and download manager library. Haveing these only in tabs would s*cks. I donÄt need 10 mail windows or so. But ymmv and IanN_Away is the owner. 21:16:46 inclding navigator? 21:18:33 yeah. I usually use tabs there. Each tab in a window would clutter the screen pretty fast. 21:18:57 i just dunno if Mozilla will remove the ability to spawn top level chrome windows 21:19:15 that is the ONLY thing I can think of when it comes to this everything in-content thing 21:19:20 but that would be silly 21:19:39 yes. Now and then I use open in new windows too 21:22:03 also prefs in a tab s*ck 21:22:11 indeed 21:25:14 Well my general vauge stratgy is this and it is split betwen my stuff/other modern mozilla stuff anyway.. Wire in this modified devtools loader that also provides --chrome (removing it from suite glue) then ifdef the components into smaller chunks to fix navigator, composer, and mailnews, other bits. Fix suiteglue and browser content handler then start fixing navigator.xhtml 21:26:44 but starting with some fixups like providing toolkit expected strings that the application has to provide for some reason 21:27:14 and the modified devtools loader helps greatly 21:28:22 reeeeal mixed messages when someone fixes stuff and people vanish 22:33:58 ha, time to update my nightly then 22:34:01 been lazy :P