01:33:06 <tomman> Is Libera channel listing broken?
01:33:28 <tomman> Tried to refresh my channel list today on ChatZilla and always end with an empty list
02:45:24 <franstam> nope, works fine on hexchat here
10:16:36 <merinos> Hello everyone,
10:16:37 <merinos> a small question: how to easily communicate with Mozilla to report a bug in the display of extended certificate (TLS)? same problem with SeaMonkey... for example: www.postfinance.ch ...
10:16:39 <merinos> thanks in advance!
10:25:36 <merinos> the certification authority SwissSign ( www.swisssign.com ) says that it is Firefox that has a problem...
10:37:27 <merinos> ... ?
10:39:27 <njsg> merinos: wait some time, somebody might have good information on how to proceed
10:40:03 <merinos> ok... thank you  :)
10:40:50 <njsg> I haven't checked that site, but if there's no other workflow, it could be reported in bugzilla (but it's probably good to wait for some comments first, might also have been reported already, just not with that example/case?)
10:46:03 <merinos> it's complicated to explain...
10:48:34 <merinos> e-mail from PostFinance (original in french, translate with DeepL):
10:48:36 <merinos> We have been contacted by bringing the certificate which is not displayed immediately in Firefox. Only by clicking on "show certificate" one gets the details.
10:48:37 <merinos> In a small test we saw, the same problem for the websites of Raiffeisen, ZKB and Cler.
10:48:39 <merinos> In the meantime we have made a ticket to SwissSign. SwissSign delivers certificates according to the instructions of the trust store provider and the CA/Browser Forums standardization committee. SwissSign closed our ticket saying that they too do not know why the certificate is not displayed in Firefox.
10:48:40 <merinos> Since this is a technical problem in the Firefox browser, SwissSign and PostFinance do not have the possibility to solve it or to provide additional information. The only option left is to contact Mozilla technical support: https://support.mozilla.org/fr/products/firefox
10:48:42 <merinos> We are very sorry that we cannot offer you a solution for your needs at the moment.
10:48:43 <merinos> With our best regards
10:48:45 <merinos> xxx xxx
10:48:46 <merinos> PostFinance AG
10:48:48 <merinos> Customer Center
10:51:36 <merinos> now I see that I have the same problem with Chromium...
11:00:01 <merinos> I'm sorry to have disturbed you...
11:00:11 <merinos> bye
20:21:17 <Sousacycle> Does anybody here have experience with extensions on SeaMonkey?
20:30:41 <therube> Sousacycle:  if you toggle the Pref, dom.enable_performance_navigation_timing, to 'false', that should get Google Translate working
20:30:42 <therube> - BUT, it was mentioned here, that doing so may affect other sites (negatively), so maybe toggle, translate, then toggle back...
20:30:44 <therube> what about extensions?
20:32:33 <therube> and speaking of extensions, did someone mention that palefill was no longer "supported" in SeaMonkey?
20:32:45 <therube> cause the current 1.25 instealled just fine.
22:47:20 <njsg> therube: resistFingerprinting would work as a workaround too. But, if noscript is installed, it might be better to try to use a surrogate
22:49:09 <njsg> therube: from what I recall reading, it'd not work at least with some sites, with errors from javascript execution, so it probably installs fine and the problems are only visible when you visit these sites and need some of the polyfills