11:06:20 <njsg> KianNH is really not productive at all, and it's hard not to see these posts as trying to stick the blame on "not here" in any way possible.
11:06:52 <njsg> The issue is apparently that Pale Moon is reporting it's something it's not... wait, haven't UAs included additional names for ages now?
11:07:13 <njsg> I'm quite sure Trident isn't the Mozilla Suite, after all
11:08:03 <njsg> these posts are utterly useless, on one hand blame is on the UA for impersonating "something else", on the other hand, the blame is on the UA for being that something else
11:08:08 <njsg> tautology club, here we go...
11:09:02 <njsg> "your browsers don't support X/Y/Z which we decided we will be requiring" would be much more productive than all that mess, it really sounds that is somebody who has no idea of what the issue is trying to disregard the issue
11:16:17 <njsg> Internet can cater all browsers, that's not Cloudfare's choice to make. A shame KianH seems to demand productive comments but is unable to do so in their own comments... maybe if instead of repeatedly listing browser versions that do work they indicated what is or might be missing...
11:28:54 <njsg> it should also perhaps be noted that getting some browsers into an endless loop should be seen as a problem
11:29:24 <njsg> they don't want to support some browsers? sure. But they could at least show a message and stop there.
11:29:37 <njsg> instead of making these browsers DDoS cloudflare
17:58:02 <jonadab> I still want a setting that lets javascript run when key events happen (page load, click, arrival of AJAX response from server, etc.) but stops it if it goes for more than a second or two.
17:58:23 <jonadab> And only in the foreground tab.  js should NEVER run in background tabs for ANY reason.