- <p>Remove reference to 'How to Report Bugs Effectively'. It was only rendered as text without URL in the
- README anyway and there's no indication that users read it ...</p>
- </li>
- <li>
- <p>Let the dok-readme target fix the location embedded into the README file. This used to be done by CVS
- but since the git migration it has to be done through other means.</p>
- </li>
- <li>
- <p>Remove 'experimental' warning for client-specific-tag-related directives. They seem to work reliably and
- there is no obvious reason why we would change the syntax in the near future.</p>
- </li>
- <li>
- <p>Describe how to check if Privoxy has been built with FEATURE_HTTPS_INSPECTION.</p>
- </li>
- <li>
- <p>Add a link to the trusted-cas-file documentation that explains how the user can create the file
- herself.</p>
- </li>
- <li>
- <p>Don't explicitly mention the license for the code coming from 'Anonymous Coders' and Junkbusters. It's
- obviously licensed under the GNU GPL like the rest of Privoxy or we wouldn't be allowed to distribute
- it.</p>
- </li>
- <li>
- <p>Update the +hide-user-agent example with uagen output.</p>
- </li>
- <li>
- <p>Slightly improve the wording of the ca-key-file documentation.</p>
- </li>
- <li>
- <p>Explicitly mention Windows 10 as supported so search engines and users looking for it can find it.</p>
- </li>
- <li>
- <p>Import a bunch of contributors from the ChangeLog.</p>
- </li>
- <li>
- <p>Remove obsolete doc/gpl.html.</p>
- </li>
- <li>
- <p>Upgrade a couple of links to https://.</p>
- </li>
- <li>
- <p>Don't prefer the SourceForge patch tracker over the privoxy-devel mailing list. While at it, link to the
- SourceForge patch tracker.</p>
- </li>
- <li>
- <p>Mention http-inspection in the 'my browser warns me about unauthenticated content' FAQ entry.</p>
- </li>
- <li>
- <p>Simplify the 'Is there is a license or fee?' FAQ entry.</p>
- </li>
- <li>
- <p>Add another +redirect{} example.</p>
- </li>
- <li>
- <p>Explicitly mention that interested sponsors should include the link target in their first mail.</p>
- </li>
- <li>
- <p>Clarify that only Privoxy team members can object to new sponsors and link to the list of current team
- members.</p>
- </li>
- <li>
- <p>Note that sponsor URLs may not contain keyword spam.</p>