3 ms·

"it's really not related" https://bugs.chromium.org/p/project-zero/issues/detail?id=1139#c23 https://bugs.chromium.org/p/project-zero/issues/detail?id=11...

mirimir 10y ago
Well, he said that it wasn't. But then refused to say more, and disabled comments. Strange.
- kelnage 10y ago
  I would imagine that was because the comments are intended for discussion about that particular issue, not for random users to jump in with wild conjecture on its impacts. Honestly not that strange.
- bestnameever 10y ago
  > But then refused to say more What more is there to say?
  - askvictor 10y ago
    A link to an announcement on the issue?
    - darklajid 10y ago
      Not in a random unrelated bug that people hijacked to discuss a different problem, no. I think there's nothing special about refusing to discuss stuff there and disabling comments.
      - mirimir 10y ago
        That's true, if it is "a random unrelated bug". I suspect that there will be many such reports in coming weeks. And lots of denial, and refusal to comment.
    - mirimir 10y ago
      That would have been the best outcome. As it is, I'm left with concerns. Maybe it is related, but he's been instructed to not comment. Maybe it's a National Security Letter. Or whatever. And yes, maybe he was just stressed out, and didn't want to be pestered with conspiracy theory ;)
- DannyBee 10y ago
  It's not strange at all? Imagine you walked into a group of people, talking about one thing. You started talking about something completely random and different. They want to continue their conversation, you keep interjecting with questions about your random thing. If they could, they'd probably turn you off so you couldn't talk, or go to another place to talk about it. That's precisely what happened here.
- notatoad 10y ago
  he was nice enough to answer the off-topic question, and the person who asked decided not to believe him and continued to take the discussion further off topic. The only good way to handle that sort of thing is to lock the thread.

mirimir 10y ago

Well, he said that it wasn't. But then refused to say more, and disabled comments. Strange.

kelnage 10y ago
I would imagine that was because the comments are intended for discussion about that particular issue, not for random users to jump in with wild conjecture on its impacts. Honestly not that strange.
bestnameever 10y ago
> But then refused to say more What more is there to say?
- askvictor 10y ago
  A link to an announcement on the issue?
  - darklajid 10y ago
    Not in a random unrelated bug that people hijacked to discuss a different problem, no. I think there's nothing special about refusing to discuss stuff there and disabling comments.
    - mirimir 10y ago
      That's true, if it is "a random unrelated bug". I suspect that there will be many such reports in coming weeks. And lots of denial, and refusal to comment.
  - mirimir 10y ago
    That would have been the best outcome. As it is, I'm left with concerns. Maybe it is related, but he's been instructed to not comment. Maybe it's a National Security Letter. Or whatever. And yes, maybe he was just stressed out, and didn't want to be pestered with conspiracy theory ;)
DannyBee 10y ago
It's not strange at all? Imagine you walked into a group of people, talking about one thing. You started talking about something completely random and different. They want to continue their conversation, you keep interjecting with questions about your random thing. If they could, they'd probably turn you off so you couldn't talk, or go to another place to talk about it. That's precisely what happened here.
notatoad 10y ago
he was nice enough to answer the off-topic question, and the person who asked decided not to believe him and continued to take the discussion further off topic. The only good way to handle that sort of thing is to lock the thread.