So to sum up what happened: 1) I was about to sign up to new hosting service, saw that TOS had a "jeopardize NatSec" issue.
-
-
Replying to @emptywheel
So I asked. I said, "I write about Snowden documents and lawyers the CIA pretends are secret but aren't. Does THAT jeopardize NatSec?"
1 reply 6 retweets 4 likes -
Replying to @emptywheel
Chat person said, "I spoke with a member of leadership and they do have concerns that it would violate our TOS."
1 reply 3 retweets 2 likes -
Replying to @emptywheel
So he was going to set up an email between me and TPTB. I said, You might tell them a journo has already asked me abt this story.
1 reply 1 retweet 7 likes -
Replying to @emptywheel
I also assured him I could have people vouch for me. They decided they didn't need to talk anymore. It was prolly press, not babysitters
1 reply 1 retweet 3 likes -
Replying to @emptywheel
So I should have a new hosting service shortly and maybe emptywheel will be back and running more secure than before.
2 replies 5 retweets 6 likes -
Replying to @emptywheel
Then I can write abt how the FBI wants to get things like log files from NatSec jeopardizing websites like mine w/just an NSL.
4 replies 9 retweets 11 likes -
Replying to @emptywheel
Has anyone (excluding the chat-assistant you led on at your new hosting) ever actually said your website "jeopardizes NatSec"?
1 reply 0 retweets 0 likes -
-
Replying to @emptywheel
But nobody who's actually ever read your blog, or knows anything at all about natsec?
1 reply 0 retweets 0 likes
Not to my face, nope.
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.