Existe aussi en tant que service caché Tor : http://imgbifwwqoixh7te.onion + en ligne de commande + via Node.js + via un module Firefox
et bien sûr dans le web traditionnel : https://img.bi (connexion chiffrée via TLS).

Besoin de Javascript pour le chiffrement et déchiffrement dans le navigateur.

Un projet de moyen de communication sécurisé et asynchrone, distinct de Bitmessage.

Via https://twitter.com/kheops2713/status/367604408085127168

Le service Hushmail de courriel electronique propose en option gratuite un formulaire web pour les internautes qui ne peuvent pas ou ne veulent pas donner ou envoyer via leur adresse email. Une alternative à la PrivacyBox ? (Qui semblait lié aux gouvernement allemand).

La société Hushmail est basée au Canada, serveurs au Canada, mais elle appartient à 100% à une société du Delaware, donc des EUA.

This link leads to the compressed file for this favorites-sharing web software, version 0.0.40 beta. I just upgraded this system to this new version.

News (in English):
[Version francophone : http://mpr.soup.io/post/282829761/ .]

I also want to tell you that from now, this web space will be accessible in HTTPS. It means the ENCRYPTED form of it. Actually, I will try to make all of it reachable ONLY in HTTPS.

HTTPS also means more privacy: your Internet Service Provider can not decrypt nor understand any https:// URLs. Warning: this has nothing to do with the browsing history or the cookies. An HTTPS connection does NOT prevent the URLs from being saved in the history of your web browser (Mozilla Firefox, Opera Software Opera...), nor prevent the 3 cookies (of this Shaarli) to be saved on your harddrive.

Most pages and internal links + all forms of this Shaarli works in HTTPS,
but there are cases in which you may browse this directory /shaarli/ "in clear" (= in HTTP):
* direct access to an HTTP page (that's why I currently ban all search engines to index this Shaarli),
* I didn't prevent the images from loading only in HTTPS,
* RSS & ATOM feeds are reachable only in HTTP, it seems they can't be read/parsed in HTTPS,
** but permalinks in ATOM & RSS feeds leads to the HTTPS URL,
* QR codes genrated via invx.com are not yet encrypted,
* websockets only work in HTTP (you can't really browse them, but your ISP sees it).

Honnestly i'm not proud of my work, because it's done manually, by adding https://lienspersos.accessibilisation.net/shaarli/ at many places in the code... But at least, it WORKS.

I know a website can be set up/configured so that any page is viewable ONLY in HTTPS, with PHP and/or .htaccess file and stuff like it, but my technical skills are currently too low to do it.
Your browser may ask you or talk about some certificate... I didn't understand everything about it, I just know it's needed for an HTTPS connection. Sorry.