Use the init_arg attribute configuration (see "Constructor parameters" in Moose::Manual::Attributes):

package SOD::KuuAnalyze::ProdId;
use Moose;

has 'users' => (
    isa => 'ArrayRef[Str]', is => "ro",
    init_arg => undef,    # do not allow in constructor
);
1;

An easier, quicker, and much less privacy-invading way to make and share events

More and more websites use like-buttons from Facebook, Google+ and Twitter. However, these buttons send information to these social networks even if the user doesn't click them, but even if they are just present on a webpage. This way these networks are able to track which websites users are visiting and are able to build fairly complete browser histories of their users. Because this is neither what a user might expect nor what many website operators that embed like-buttons want, this alternative way of using these social services was developed.

The concept is fairly easy. Per default only a gray mockup image of a like-button is embedded. Only if a user clicks this button the real like-button is loaded and information sent to the social network. With a second click the user can then like the webpage (or tweet it etc.).
All buttons can be permanently enabled.

The first click basically means that the user agrees that information is sent to the social network in question. But only for the page that embeds like-button and only for the selected social network. If the user visits the same page again the button is at first again deactivated. This way one can prevent, that social network owners can build complete surf profiles of their users.

If users don't care about their privacy and rather want the like-buttons to be always enabled they can do so in the settings menu, accessed via the gear icon. Per default this is done via cookies and on a domain basis, but this feature is extensible so that this information can be stored anywhere (e.g. via AJAX on a webserver or in the browsers HTML5 local storage).

Comment ça marche ?

La Brique Internet est un simple boîtier VPN couplé à un serveur.

Un VPN sert à relier un ordinateur à un autre, de façon sécurisée, de façon à ce qu'aucun intermédiaire sur Internet ne puisse lire le contenu des communications qui transitent. Pour que la Brique fonctionne, il faut lui configurer un accès VPN, qui lui permettra de créer un tunnel jusqu'à un autre ordinateur sur Internet. En vous connectant simplement en WiFi sur la Brique, vous pourrez aller sur Internet, en passant automatiquement au travers de ce tunnel chiffré. De cette façon, votre Fournisseur d'Accès à Internet (FAI) ne peut plus ni vous espionner, ni vous brider ni vous filtrer. C'est le même mécanisme qui permet à la Brique d'être un serveur nomade.

Élimination de la surveillance, de la part du FAI et des fournisseurs de services :
Schéma

L'ordinateur auquel vous vous reliez par le VPN doit être géré par des gens de confiance (e.g. une association rattachée à la FFDN). C'est pour cette raison qu'il est souhaitable de choisir une association pour laquelle vous avez déjà rencontré les adhérents. Certaines associations vous fourniront directement le boîtier clé en main, avec votre accès VPN préconfiguré.

There has been a guide to Tor hidden services for a long while now. It was about time for an I2P guide. For reference, here's the latest Tor Guide for Hidden Service (V. 4.0) http://pastebin.com/zRLGDRCM

Ricochet is a different approach to instant messaging that doesn’t trust anyone in protecting your privacy.

- Eliminate metadata. Nobody knows who you are, who you talk to, or what you say.
- Stay anonymous. Share what you want, without sharing your identity and location.
- Nobody in the middle. There are no servers to monitor, censor, or hack.
Safe by default. Security isn’t secure until it’s automatic and easy to use.