We just published a response on our blog - https://spideroak.com/articles/a-transparency-report-is-a-canary/ …. The TL;DR is that the canary is in place and was never taken down. Happy to discuss further if you have questions.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We just published a response on our blog - https://spideroak.com/articles/a-transparency-report-is-a-canary/ …. The TL;DR is that the canary is in place and was never taken down. Happy to discuss further if you have questions.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That doesn't leave a good impression at all. This basically confirms a gag order and possibly a NSL.
-
We just published a response on our blog - https://spideroak.com/articles/a-transparency-report-is-a-canary/ …. The TL;DR is that the canary is in place and was never taken down. Happy to discuss further if you have questions.
-
It does make quite a big difference as far as I am aware. 1) The transparency report is not signed by the three parties that used to verify the canary. 2) How are you supposed to report about e.g. NSL, when you can't legally disclose that you have received one?
-
The problem with a canary is how fragile it is. The EFF has recommended against canaries for some time, and other companies (like Signal) don't use them at all. This is a perfect example of the danger of using a warrant canary--we haven't been served but people now think we have.
-
That is true, but that'S also kinda is the whole point of a canary.
-
Unfortunately it's never even been proved if a warrant canary is legal. Transparency reports are the standard way to do this type of reporting now.
End of conversation
New conversation -
-
-
Open Source your client. That is the only way we can trust you. You always said you planned to, which was one reason I started using SpiderOak many years ago.
-
We just published a response on our blog - https://spideroak.com/articles/a-transparency-report-is-a-canary/ …. The TL;DR is that the canary is in place and was never taken down. Happy to discuss further if you have questions.
-
that blog post does not address the open source client issue.
-
We've addressed the open source question pretty clearly here - https://support.spideroak.com/hc/en-us/articles/115002665263-SpiderOak-ONE-Open-Source …. It's not as simple as throwing the source code up on github. That would be irresponsible.
End of conversation
New conversation -
-
-
I hope you will publicly address the concerns expressed inhttps://www.reddit.com/r/privacy/comments/94nspi/spideroak_cans_its_warrant_canary_suffers/ …
-
We just published a response on our blog - https://spideroak.com/articles/a-transparency-report-is-a-canary/ …. The TL;DR is that the canary is in place and was never taken down.
End of conversation
New conversation -
-
-
Ah yes, "replacing" the canary ;) We get you, we get you.
-
We just published a response on our blog - https://spideroak.com/articles/a-transparency-report-is-a-canary/ …. The TL;DR is that the canary is in place and was never taken down. Happy to discuss further if you have questions.
End of conversation
New conversation -
-
-
thanks for confirming you've been raepd
-
We just published a response on our blog - https://spideroak.com/articles/a-transparency-report-is-a-canary/ …. The TL;DR is that the canary is in place and was never taken down. Happy to discuss further if you have questions.
-
yes, this is exactly what a NSL receiver would say
End of conversation
New conversation -
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.