-
hrosik
IanN_Away: um, what would be the benefit?
-
IanN_Away
hrosik: just it would show as something like logbot_cc@bot/logbot_cc rather than showing IP address
-
hrosik
ok, the cool factor :)
-
njsg
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 :-\
-
njsg
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
-
buc
hrosik: just wondering why the non-standard port 8080? (Such ports often enough are blocked by firewalls/proxies etc.)
-
buc
hrosik: Is there a risk of being a bit spammed if third-party channels also start to /invite themselves?
-
buc
Since the logging bots only read here and never say anything, the /voice mode seems overkill for them.
-
buc
Robots should not appear on the same list with humans... :)
-
frg_Away
buc just did it so it moves up in the list. Family now :)
-
buc
To be in the family, you could also add a well-known suffix to it... ;)
-
buc
Just to mark it is not available for a dialog right now... :)
-
frg_Away
buc might be an AI bot.
-
buc
Ups. It already has a suffix (_cc). Then not needed. :)
-
frg_Away
For me including bot usually classifies it.
-
buc
Well anyway, thanks to hrosik for his efforts.
-
buc
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...
-
frg_Away
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.
-
frg_Away
So if the cert can't be sorted quick would be ok with http only.
-
buc
...and the non-standard port is a little frustrating...
-
buc
but it is better than nothing.
-
frg_Away
Just an url. 8080 is an alternate port for 80 so should not be blocked.
-
buc
In general, nothing should be blocked. But in various environments and in various jurisdictions a lot of things can be blocked on practice.
-
buc
hrosik: What http server is used as a front-end to the localhost:3001? (Just curious, since it does not look like Apache :) )
-
WG9s
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.
-
WG9s
tonymec: so far only linux 64-bit and macOS cross compile done.
-
WG9s
and now just waiting on windows builds
-
buc
*_Away: Who performed switch to new download manager implementation -- pls. see
bugzilla.mozilla.org/1661070#c21 (with a change proposed).
-
buc
Thunderbird can be affected as well...
-
frg_Away
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.
-
frg_Away
Btw. for Windows I was unable to reproduce the attachemnt cpu spike. Seems to work fine there.
-
buc
cpu spike is another issue, and for gtk only.
-
buc
njsg: Could you pls. test that removing "seems to be extra" code as proposed in
bugzilla.mozilla.org/1661070#c15 are OK in all your use cases with the old XUL picker?
-
tonymec
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.
-
tonymec
WG9s: FYI: Sm 2.53.9b1pre 20210625165032 no change (cz_sasl v6 gives SASL authentication aborted; NickServ identify works OK).