Bitmessage is a P2P communications protocol used to send encrypted messages to another person or to many subscribers. It is decentralized and trustless, meaning that you need-not inherently trust any entities like root certificate authorities. It uses strong authentication which means that the sender of a message cannot be spoofed, and it aims to hide "non-content" data, like the sender and receiver of messages, from passive eavesdroppers like those running warrantless wiretapping programs. If Bitmessage is completely new to you, you may wish to start by reading the whitepaper https://bitmessage.org/bitmessage.pdf

Not sure how up to date it is, version 0.6.1 is dated 2016-08-21, the latest one  0.6.3.2 was released 2018-02-14
https://github.com/Bitmessage/PyBitmessage/releases/

According to https://www.reddit.com/r/bitmessage/comments/cjxk9s/current_status_of_pybitmessage/ (2019-07-30) development is on-going.
This can also be seen on github, e.g. https://github.com/Bitmessage/PyBitmessage/issues/1712#issuecomment-830636842
One of the difficulties seems to be the transition from Python2 to Python3.

Uses proof-of-work.

Found on https://karl-voit.at/2014/04/10/bitmessage/

Found on https://www.wisdomandwonder.com/article/10209/an-open-tenkeyless-keyboard. Availability is unclear, the store links to
https://kono.store which offers a variety of keybaords.

Using org-mode to store contact information, exporting to vCard.
Contacts created outside of Emacs are not handled.

From simple gates to complex sequential circuits, plot timing diagrams, automatic circuit generation, explore standard ICs, and much more

Der Energieticker NÖ zeigt live die Energieerzeugung aus erneuerbaren Energien im Vergleich zum Stromverbrauch in Niederösterreich. Man sieht, zu welchen Zeiten NÖ mehr erneuerbaren Strom erzeugt, als im Land verbraucht wird.

Nice looking website (looks a bit like the editor sam), I am wondering why the author felt the need to set the title to "Web mirror of shithub.us".

The site uses weblorg.
Other articles such as
https://muto.ca/posts/clean-password-management.html
https://muto.ca/posts/painting-in-guile-with-opengl.html
are interesting too.

Small. Sloccount counts under 2000 lines of code, small enough to allow audits. The binaries can be under 50KB, small enough for many embedded targets.
Easy to deploy. Just add monocypher.c and monocypher.h to your project. They compile as C99 or C++ and are dedicated to the public domain (CC0-1.0, alternatively 2-clause BSD).
Portable. There are no dependencies, not even on libc.
Honest. The API is small, consistent, and cannot fail on correct input.
Direct. The abstractions are minimal. A developer with experience in applied cryptography can be productive in minutes.
Fast. The primitives are fast to begin with, and performance wasn't needlessly sacrificed. Monocypher holds up pretty well against Libsodium, despite being closer in size to TweetNaCl. (More detailed benchmark)