Open contribucious opened 2 years ago
Not the same thing, but kinda relevant since dev tools detection also relies on console
: https://greasyfork.org/en/scripts/41559-devtools-anti-detector/code
I have a question, though. Do you think it makes sense to have this as a general-purpose scriptlet or just use it when debugging?
I think that scriptlets that are supposed to be used for debugging purposes need a special prefix, something like "debug-prevent-devtools-detection".
I was having this same thought earlier when I saw the list here of some used for debug purposes, yet mixed without distinction with the "standard" ones in this global list. I support the idea of a prefix then.
Regarding your question, personally, I only consider it for my website analysis sessions, so ā¦ "debugging".
The case of prevent-console-hijack
is to be able to simply work in analysis / inspection with complete peace of mind on a specific website, for a certain period of time, without a monitoring by the latter for sure, by doing various tests in the DevTools > Console part, but also related to any source generating console.log/warn/etc. whether it comes from myself directly, a (Tampermonkey) userscript used to print some stuff for inspection with conditions, another scriptlet, etc. Knowing that we can be sure that our trial and error is not monitored / analyzed later at all, basically.
One could imagine dev-
or advanced-
or adv-
(for power users who like privacy and do little development but like privacy when testing). But that might complicate things: it's probably better to keep just debug-
though.
[ā¦] :arrow_right_hook: (moved to a dedicated issue) :heavy_check_mark:
Hello,
A lot of websites like TF1.fr hijack
window.console
ā allowing them, if necessary, to send the results ofconsole.error
, etc. to their servers.This forced me to create this userscript in Tampermonkey because of my many uses of
console.xxx
during my tests:// @grant none
must not be present (i.e. sandbox required here for this to work).:arrow_right: What about adding an equivalent in AdGuard, to be added here afterwards, as:
example.org#%#//scriptlet('prevent-console-hijack')
orexample.org#%#//scriptlet('prevent-console-hijacking')
,ā¦ to keep a name similar to
prevent-window-open
and others? š