Perhaps you were just ordered to start... and plugging in that little black box from the G-Men somehow, umm, killed the canary process. Somehow.
It's more likely (and I'm just grossly speculating now) that the business weighed the relatively small chance of us being ordered to give the virtually zero amount of data we have on everyone with the chance that something will go wrong updating the canary and there will be a bunch of bad publicity again.
Keep in mind that, while one may think "you're just uploading a text file, how hard can it be", it's much more resource-intensive than that. You need multiple redundant people to make sure the world doesn't freak out because your CSO was on vacation, you need them to coordinate about updating, you need them to (crucially) know how to store the PGP keys securely, you need to keep that number low to make sure the key isn't stolen from one of them, you need good tooling to minimize the chance that there's a mistake while uploading, you need to keep the machines that host it running even after a move, the DNS entries up, monitoring to tell you if the canary is stale, etc.
It's a lot of things to get right and a lot of things that can go wrong, and the failure case for that is "your stock goes down", which is a heavy price. I think the mistake here was that there wasn't a bigger, more explicit and pre-emptive announcement (something like "we'll take the canary down in X weeks because Y"), which I think would have more successfully assuaged fears.
As soon as you said "I work for that company", you speak for them, whether you like it or not and no amount of disclaiming changes that in the mind of the reader. Additionally, you went on to explain things that only someone that works there would know, so you are explicitly speaking for the company. I'd normally recommend that an employee delete such a post, perhaps explaining the error. Given that it involves an NSL, I recommend this action more strongly than I might normally. Ask yourself, "what do I and the company have to gain from such a post, other than getting to sound like an 'insider' on HN?", and then ask "what's my worst possible outcome of posting such a thing?" Weigh the two, choose a winner.
As a warning to others, one should always ask themselves if they are posting outside their wheelhouse for an ego boost, or if it truly helpful information to others and to the company. Useful advice in the general case, IMO, but especially if you're posting in reply to "my company's in the news". I generally just shut the hell up and let the PR people handle it. Especially when you're an IC or middle-manager, 'cuz odds are that you don't have the full story.
Sorry you took it that way. Myself, I'd hate to see our desire for gossip overrule wishing to avoid folks having a difficult conversation with their manager. Maybe not in this case, but if enough people from various companies start posting out of turn on public forums when they as individuals don't know the whole story, someone's going to wake up to a bad day. It's one thing to comment on "MSFT Announces new, cool widget thingy": "I worked on that, and what a long road we've travelled!" Quite another when the headline is "Google writes down $4 billion on stupid acquisition", and "I work Google, but I only speak for myself, and I think..." Any whiff of controversy and I'd say just stay out of it.
But it's just advice, do what you like with it, including ignore it.
Perhaps more people should have difficult conversations with their managers. Or perhaps his management supports, or at least actively doesn't care about, these sorts of posts? We have no idea.
Surely as an adult, he can decide that for himself, without being subject to sermonizy advice meant to take care of his own interests for him because he's deemed incapable of doing it himself.
If they got a NSL and he lied about it, no harm will come to him. Or if he's telling the truth, obviously.
At which point we are talking civil disobedience, so worrying about whether that will land them in trouble with management is missing the point by a mile and a half.
Yea, there's a chance it will backfire. But I think that if everyone speaks openly it's much better for the community. I think one of the things you're also overlooking is the teacher effect - talking about something and teaching it provides a better insight and understanding of it to yourself. I've had great insights into things I've been working on because I discussed things surrounding them on reddit or HN. Community feedback is always valuable.
As far as I know (and, sure, I may not know, although if someone wanted something from the server I'm one of a few guys that could get it), we haven't received any letters. What makes me even more confident, though, is the fact that there really isn't much data to give. All we have is some ciphertexts for attachments, and messages aren't retained, even encrypted (why would they)?
We don't even log IPs or other personal information, so I'm not sure what usefulness an NSL would serve.
Anyway, this is not an official company stance, I just wanted to comment about my personal experience because I see some speculation here.