00:02:23 IanN_Away: um, what would be the benefit? 00:03:20 hrosik: just it would show as something like logbot_cc@bot/logbot_cc rather than showing IP address 00:07:41 ok, the cool factor :) 08:44:13 given that some of the pages at developer.mozilla.org have moved but remain available, I wonder if something could be changed there so that redirects actually work :-\ 08:45:17 currently one follows an old URL, it ends with a 404, if it's accessed via wayback machine for a couple years ago, it lands on a page whose address currently works 11:44:47 hrosik: just wondering why the non-standard port 8080? (Such ports often enough are blocked by firewalls/proxies etc.) 11:46:47 hrosik: Is there a risk of being a bit spammed if third-party channels also start to /invite themselves? 11:57:42 Since the logging bots only read here and never say anything, the /voice mode seems overkill for them. 11:57:50 Robots should not appear on the same list with humans... :) 11:59:57 buc just did it so it moves up in the list. Family now :) 12:01:17 To be in the family, you could also add a well-known suffix to it... ;) 12:02:50 Just to mark it is not available for a dialog right now... :) 12:04:10 buc might be an AI bot. 12:04:10 Ups. It already has a suffix (_cc). Then not needed. :) 12:05:30 For me including bot usually classifies it. 12:07:03 Well anyway, thanks to hrosik for his efforts. 12:09:47 BTW, Whether the secure connection (https) is so actual for the logbot logs? Esp. it might be not so easy to obtain a certificate for a site with non-standard port, afaik... 12:12:37 Just thought the same. Would like to add to the support page but wait till certificate issue is sorted. I think http:// would be ok here. This whole https:// everywhere is stupid for non confidential data like this here. 12:14:02 So if the cert can't be sorted quick would be ok with http only. 12:16:42 ...and the non-standard port is a little frustrating... 12:17:41 but it is better than nothing. 12:25:29 Just an url. 8080 is an alternate port for 80 so should not be blocked. 12:29:53 In general, nothing should be blocked. But in various environments and in various jurisdictions a lot of things can be blocked on practice. 12:46:50 hrosik: What http server is used as a front-end to the localhost:3001? (Just curious, since it does not look like Apache :) ) 19:37:39 tonymec: so new build with actually new code. did it during the day because was thought correctly that it would have character sets issue with Linux. 19:39:32 tonymec: so far only linux 64-bit and macOS cross compile done. 19:54:29 and now just waiting on windows builds 22:27:40 *_Away: Who performed switch to new download manager implementation -- pls. see https://bugzilla.mozilla.org/show_bug.cgi?id=1661070#c21 (with a change proposed). 22:44:24 Thunderbird can be affected as well... 22:48:16 Mostly me. The exception is supposed to be cosmetic. If I remember I added a try/catch which ported a later bug. Trying to avoid this would be preferable. Please file a new bug and add a patch. It is very hard to keep track of these code fragments in comments. 22:48:18 Btw. for Windows I was unable to reproduce the attachemnt cpu spike. Seems to work fine there. 22:53:52 cpu spike is another issue, and for gtk only. 22:56:56 njsg: Could you pls. test that removing "seems to be extra" code as proposed in https://bugzilla.mozilla.org/show_bug.cgi?id=1661070#c15 are OK in all your use cases with the old XUL picker? 23:27:46 WG9s: Whenever I see a new build I test it. No problem. Just out of bed (at 1 am my time!) I see there is a 2021-06-25 16:50, let's download it and test it. 23:54:57 WG9s: FYI: Sm 2.53.9b1pre 20210625165032 no change (cz_sasl v6 gives SASL authentication aborted; NickServ identify works OK).