+144) Allow Privoxy admins to pre-define tags that are be set for
+ clients that previously opted-in through the CGI interface.
+
+ This would be useful in multi-user setups where admins may
+ want to allow users to disable certain actions and filters
+ for themselves without affecting others.
+
+ Even in single-user setups this could be useful to allow
+ more fine-grained toggling. For example to disable request
+ blocking while still crunching cookies, or to disable
+ experimental filters only.
+
+ Interested donors: 1.
+
+145) Once #144 is implemented, allow clients to opt-in to the
+ tagging for a limited amount of time (or number of requests).
+
+ Interested donors: 1.
+
+146) Once #144 is implemented, optionally allow to save the opt-in
+ status to disk.
+
+147) Improve "Building from Source" section in the user manual.
+ A common problem seems to be that it's not obvious to non-technical
+ users how the listed dependencies can be installed on the commonly
+ used platforms. Adding a couple of examples should also be useful for
+ technical users (like Privoxy developers) who want to install or test
+ Privoxy on platforms they are not familiar with.
+