Differences between revisions 5 and 6
Revision 5 as of 2012-11-10 22:50:28
Size: 2284
Editor: ?NickDaly
Comment: added problem explanation.
Revision 6 as of 2012-12-03 03:00:58
Size: 515
Editor: ?NickDaly
Comment: Removed page.
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
It's important to stress that being fully and truly anonymous is nearly impossible. Everything communication you make proves *that communication happened* between people. The only thing that changes is how easy it is for others to identify the message's source and destiation or its contents. NickDaly removed this page:
Line 6: Line 6:
While anonymous contribution to the project is not recommended, it may be possible in some circumstances.  * Without guidance from the TAC, I'm unclear whether they even want anonymous contributions of code.
 * It's unlikely that code contributions would be able to remain sufficiently anonymous to keep the contributor safe.
Line 8: Line 9:
## If your page gets really long, uncomment this Table of Contents
## <<TableOfContents(2)>>

To remain more anonymous, please keep traceable, electronic, communication to a minimum. If possible, please meet with a member of the project in person to discuss your concerns and to allow them to champion your contributions. If electronic communications are necessary (when personal meetings or other out-of-band communications are impossible or overly difficult), options include:

 IRC :: Connect to the #freedombox channel on irc://irc.oftc.net over Tor and use a pseudonym to introduce yourself there.

 Email :: Send a project member an email that's encrypted to their PGP key. Email never encrypts headers or subject lines, so the e-mail should not reveal information in its subject line and will always expose your email address and the fact that a communication took place between the two parties. Email attachments are generally not encrypted, so files should be pasted into the email, not attached.
       :: See (Basic Email Safety)[http://flossmanuals.net/basic-internet-security/ch022_introduction-to-email-safety] and (Basic Email Encryption)[http://flossmanuals.net/basic-internet-security/ch027_mail-encryption-gpg] for details.

 TODO :: Add more detailed instructions.

The fundamental problem is that communicating always shows that a communication happened, among other details. The question is how easy it is for an observer to identify what was said or who said (or heard) it. Different communication methods make it easier or more difficult to figure out different details.

## You can add other _helpful_ links here.
##== See also ==

----
## If this page belongs to an existing Category, add it below.
## CategorySomething | CategoryAnother
If you need to be anonymous to be able to contribute to this project safely, then please do not put yourself at risk by trying to contribute code to the project anonymously.

Translation(s): none


?NickDaly removed this page:

  • Without guidance from the TAC, I'm unclear whether they even want anonymous contributions of code.
  • It's unlikely that code contributions would be able to remain sufficiently anonymous to keep the contributor safe.

If you need to be anonymous to be able to contribute to this project safely, then please do not put yourself at risk by trying to contribute code to the project anonymously.