Adapting “hosts” file block lists to Privoxy's way of blocking…

[Faxopita]

Hello whenever,

the script won't touch ad.goodsite.com, because shortening non-cloud-based subdomain-included addresses always leave untouched the domain and the first portion of its subdomain—a convention of mine, but free to you to modify it and keep the second portion of the subdomain as well. However, the script would compress ad.goodsite.com to .goodsite.com if goodsite.com were mistakenly included in the original hosts file as well. If the hosts file contained server1.ad.goodsite.com and server2.ad.goodsite.com, then the script would return .ad.goodsite.com, thus being rid of subdomain's portion 2; if the hosts file contained ad.goodsite.com and goodsite.com, then .goodsite.com would be the result. If you wanted to modify the script to keep the second portion of any subdomain when available, then your amended script would simply return .server1.ad.goodsite.com and .server2.ad.goodsite.com The resulting dot-prefixed entries would prevent your browser from loading any potential content such as, for example, tracking.server1.ad.goodsite.com

Thanks for your input.