Notices where this attachment appears
-
I saw someone mention #Bitmessage. “Bitmessage”:{https://wiki.bitmessage.org/Main_Page} was interestingly different when I tried some years ago. I should take another look. It seemed to use a lot of bandwidth and CPU to sustain the network, even when it was days or weeks between actual incoming messages for me / outgoing messages from me.
Also: #Twister. “Twister”:{http://twister.net.co/} is a #P2P microblogging tool. Twister seemed a little complicated to get running, but once I did, it was cool.
Bitmessage seemed to be:
1. Mostly for person-to-person messages, but I don’t recall reading its security & privacy specifics.
2. A little tech-specific, as in not appealing to people who are not into the technology involved
3. Slow to develop ... I’m sure the note about using the updated patched version has been on the website for years.
Twister seemed to be:
1. Mostly for public microblog type posts.
2. I wasn’t really sure whether “following” did much.
3. At the time, it felt like things were actively moving, but I do remember a months-long thread about censorship resistance features that resulted in some contacts abandoning it.
-
Don’t know when this happened, but #BitMessage had a remote code execution bug that may have been exploited. https://wiki.bitmessage.org/Main_Page
I’ve been wanting to get BitMessage running again ... put the program on a small device that runs little else and just have it running.