You're a star!

I don't really know about scope too much - just so long as you show the basics people can ask if they get lost/stuck, right?

Steve

I think it would be best if the article would be task-oriented, rather than feature-oriented. What I mean is there are already vast amounts of information about programs like Tor, or I2P online; however, the problem is that a potential reader ( like me ) always starts with some itch he needs to be scratched, and then he has to read vast amounts of info to even figure out which application/technology is able to scratch his itch and if yes, how.

Why dont we start with a list of common privacy-related itches instead, and proceed to description of potential solutions, like this:

- Mr. A works in an evil company that logs all chatting. Mr. X wants to set up some kind of chatting proxy on his home server, tunnel his chatting soft to his home proxy by, let's say, ssh, and this way hide his chatting activities.

- Mr. B takes part in an anti-scamming initiative www.419eater.com and would like to make it hard for the scammers to trace his IP while he's exchanging emails with them.

- Mr. C would like to blog about his company while making sure it cannot discover his identity later on.

- etc etc ...

The point is, I kinda don't like articles titled 'How to set up and use technology X' . Those articles start up with a solution, while we dont have a problem yet. While reading them, I always find myself thinking, 'well, that's all fine and dandy, but how can I use that to scratch my itch?' Let's start up with a clear definition of the problem and only then propose a solution!