Recensiones de Link Status Redux
Link Status Redux per Juha Aatrokoski
Responsa per Juha Aatrokoski
Responsa de disveloppator
publicate 4 napjaI have also noticed this annoyance and agree that such functionality would be useful, but unfortunately it is "not possible" within the context and scope of LSR.
The first problem is that as it is entirely up to the website which search parameters are significant wrt. the page content ("v") and which are not ("pp"), you cannot just blindly ignore/remove parameters; you need to have a database matching websites to safe-to-remove (tracking) parameters, *and* you have to keep it up-to-date. This maintenance of its own database, or reliance on an external one, is out of scope for LSR.
The second problem is that the browser history API does not have good support for partial URL matching (when querying whether a a link is visited or not), and even if it did, things could get complicated (removing parameters from the middle, reordering of parameters, etc.). This is not an issue if all browsing is "sanitized" by stripping tracking parameters from both web page links and every request made (as clicking a link is not the only way that requests can happen). In such case partial matching is not needed as both pages and history lack tracking parameters.
The solution is to use a separate anti-tracking extension that does the full sanitization i.e. strips tracking parts from both page links and all requests. I have not looked into this at all, but I am pretty sure these add-ons do exist. However, some (if not all) of them *may* strip tracking info only from requests made, not from page links, in which case it does not help with LSR (in fact it could make it worse wrt. LSR). Let me know if you find a suitable one.
The first problem is that as it is entirely up to the website which search parameters are significant wrt. the page content ("v") and which are not ("pp"), you cannot just blindly ignore/remove parameters; you need to have a database matching websites to safe-to-remove (tracking) parameters, *and* you have to keep it up-to-date. This maintenance of its own database, or reliance on an external one, is out of scope for LSR.
The second problem is that the browser history API does not have good support for partial URL matching (when querying whether a a link is visited or not), and even if it did, things could get complicated (removing parameters from the middle, reordering of parameters, etc.). This is not an issue if all browsing is "sanitized" by stripping tracking parameters from both web page links and every request made (as clicking a link is not the only way that requests can happen). In such case partial matching is not needed as both pages and history lack tracking parameters.
The solution is to use a separate anti-tracking extension that does the full sanitization i.e. strips tracking parts from both page links and all requests. I have not looked into this at all, but I am pretty sure these add-ons do exist. However, some (if not all) of them *may* strip tracking info only from requests made, not from page links, in which case it does not help with LSR (in fact it could make it worse wrt. LSR). Let me know if you find a suitable one.