@taoeffect I don't want to discourage people working on DNSChain. But, also, I don't see any benefit (but do see harm) in discouraging CT.
-
-
Replying to @BRIAN_____
@BRIAN_____ Understood. I see harm in CT: 1. Continues pay-for-insecurity 2. Supports false sense of security 3. Undermines alternatives1 reply 0 retweets 0 likes -
Replying to @taoeffect
@taoeffect 1. CT is likely to bolster free alternatives. 2. CT people aren't making false claims, AFAICT. 3. Competition is a good thing.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____ 1. Seems to give excuse to prolong charging $ 2. First sentence is false: http://www.certificate-transparency.org & rest is misleading 3. Agreed1 reply 0 retweets 0 likes -
Replying to @taoeffect
@BRIAN_____ First sentence should say: "Google's [CT] project attempts to fix several structural flaws in the SSL certificate system”.1 reply 0 retweets 0 likes -
Replying to @taoeffect
Greg Slepak @taoeffect@mstdn.io Retweeted DNSChain
Greg Slepak @taoeffect@mstdn.io added,
1 reply 0 retweets 0 likes
@taoeffect I think there may be some miscommunication there about the purpose of CT, and/or how applications are supposed to use it.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.