rojoroboto

7 ms·

31.
by rojoroboto 8y ago
yep. this falls in line with my design thinking on this.
32.
by rojoroboto 8y ago
This is a valid concern and why I'd encourage running multiple instance (geographically distributed) of the publisher.
33.
by rojoroboto 8y ago
Solid feedback. Killcord is designed to let the public know that a killcord project exists, where to find the encrypted payload, and how to check the status of the killcord project. Unpublished secrets are currently stored on the owner and
34.
by rojoroboto 8y ago
These are valid points and anyone thinking about using killcord should be aware of these. As for the second attack vector, the publisher is built with idempotence, so it is important that a killcord owner configures n-number of publishers i
35.
by rojoroboto 8y ago
Killcord treats ethereum as a project backend API. The smart contract is pretty simple in construction by design. Writes are restricted to one of two accounts (the owner account and the publisher account) and the publisher account is furthe
36.
by rojoroboto 8y ago
Hey Gang. Author of killcord here. I'm honored and humbled this was submitted to HN and I'll be reading through the comments to answer questions and respond to feedback. I started this project after a thought experiment in using n
37.
Killcord: a censorship resistant deadman's switch for whistleblowers (alpha)(killcord.io)
4 points by rojoroboto 9y ago|0 comments
38.
EFF, TrustyCon, and The Day We Fight Back(soundcloud.com)
2 points by rojoroboto 13y ago|0 comments
39.
Kickstarter Project for Cloud Revolution Manifesto(kickstarter.com)
3 points by rojoroboto 14y ago|1 comments