ifelsehow
Why aren't co-ops everywhere?
The Language of Command
Why Dream?
Attacker and Defender
What Cybersecurity Is and Why You Should Make It Your Life
Why I've Been Offline
Mondragon: Lessons for DAO DAO
Interchain
The Internet during world war
What (and why) is DAO DAO?
Fight for control threatens to destabilize and fragment the internet
Strength and vulnerability in the network of submarine Internet cables
The threat of ransomware is that it makes life unpredictable
Machine Politics: The rise of the internet and a new age of authoritarianism
Bezos Parents May Be Worth Billions
Putin's Rasputin (2011)
Common Garden develops open source agriculture
I'm American. What does k * * b refer to?
[1]: https://www.wordfence.com/blog/2017/01/gmail-phishing-data-u...
Defend against the new data URI link attack
In retrospect, I have experienced this phenomenon everyday, but never thought much about it.
You can run your own private Signal service with OpenWhisperSystems' tools [1].
It's also worth noting that Signal - as a protocol - could easily be federated. (As others have mentioned, Moxie has chimed in on why the app is centralized [2]).
If confederated messaging is important, why not use the existing Signal protocol implementations, (including the X3DH key exchange, ratcheting protocol, etc), which is all F/LOSS, and has already been widely reviewed (as the article mentions)?
[1] https://github.com/WhisperSystems/libsignal-service-java
[2] https://whispersystems.org/blog/the-ecosystem-is-moving/
> window.crypto.getRandomValues
// getRandomValues() { [native code] }
> window.crypto.getRandomValues = function () { return "aloha" }
> window.crypto.getRandomValues()
// "aloha"
Not sure if this is the case in all browsers. `window.crypto` certainly should be read-only.
The Signal protocol for Node and browsers
> ....point your machine or router's DNS to use opendns resolvers instead of your regular ones: 208.67.222.222 and 208.67.220.220