Reply to thread

Message

<blockquote data-quote="HarborFront" data-source="post: 935309" data-attributes="member: 55987">Removing ClearURLs for FirefoxThe reason why this extension still exist in my FF is its ability to remove ETagsYou can remove this extension (if you want) if you have Adguard for Desktop and add the necessary &#039;Strip URLs tracking parameters&#039; to it. Its &#039;Block hyperlink auditing&#039; is now handled by FF itself because I have auditing/block CSP reports in uBO disabled and it pass the Ping Spotter test below[URL unfurl=&quot;true&quot;]https://armin.dev/apps/ping-spotter/[/URL]To pass the cookieless cookie test go to change the preference settings as belowQuote<h3><a href="https://github.com/crssi" target="_blank">crssi</a> commented <a href="https://github.com/arkenfox/user.js/issues/179#issuecomment-348952233" target="_blank">on Dec 4, 2017</a></h3>
<table style='width: 100%'><tr><td>About ETags and performace... 
To get rid of ETags, I have set: 
user_pref(&quot;browser.cache.memory.enable&quot;, false); 
user_pref(&quot;browser.cache.memory.capacity&quot;, 0); 
No ETags, but I don&#039;t see any performance issues too.</td></tr></table>Unquote[URL unfurl=&quot;true&quot;]https://github.com/arkenfox/user.js/issues/179[/URL]Notes:-1) The above same settings affect the setting of FF to RAM by settinguser_pref(&quot;browser.cache.memory.enable&quot;, true);user_pref(&quot;browser.cache.memory.capacity&quot;, -1);2) You can set a certain amount of the RAM or set -1 for dynamic allocation of RAM.3) Besides the above two settings other settings are also needed to completely set FF to RAM. So the decision lies with the user.Test it at[URL unfurl=&quot;true&quot;]https://lucb1e.com/randomprojects/cookielesscookies/[/URL]Now, I have one extension less</blockquote>

[QUOTE="HarborFront, post: 935309, member: 55987"] Removing ClearURLs for Firefox The reason why this extension still exist in my FF is its ability to remove ETags You can remove this extension (if you want) if you have Adguard for Desktop and add the necessary 'Strip URLs tracking parameters' to it. Its 'Block hyperlink auditing' is now handled by FF itself because I have auditing/block CSP reports in uBO disabled and it pass the Ping Spotter test below [URL unfurl="true"]https://armin.dev/apps/ping-spotter/[/URL] To pass the cookieless cookie test go to change the preference settings as below Quote [HEADING=2][URL='https://github.com/crssi'][B]crssi[/B][/URL][B] commented [/B][URL='https://github.com/arkenfox/user.js/issues/179#issuecomment-348952233'][B]on Dec 4, 2017[/B][/URL][/HEADING] [TABLE] [TR] [TD]About ETags and performace... To get rid of ETags, I have set: user_pref("browser.cache.memory.enable", false); user_pref("browser.cache.memory.capacity", 0); No ETags, but I don't see any performance issues too.[/TD] [/TR] [/TABLE] Unquote [URL unfurl="true"]https://github.com/arkenfox/user.js/issues/179[/URL] Notes:- 1) The above same settings affect the setting of FF to RAM by setting user_pref("browser.cache.memory.enable", true); user_pref("browser.cache.memory.capacity", -1); 2) You can set a certain amount of the RAM or set -1 for dynamic allocation of RAM. 3) Besides the above two settings other settings are also needed to completely set FF to RAM. So the decision lies with the user. Test it at [URL unfurl="true"]https://lucb1e.com/randomprojects/cookielesscookies/[/URL] Now, I have one extension less [/QUOTE]

Verification