I use aliases in my hosts/dns so even in local-dev mode I'm still using different hostnames for services in the config and natural ports so it looks close to real.
You don't go defcon 1 over the sniffles but you do go defcon 1 over an unknown virus that closely matches a highly lethal virus we encountered about ten years earlier (SARS classic).
There is nothing in china's outbreak response that suggests guilt.
I think a lot of westerners want to believe the conspiracy theories in part because it’s hard to admit how much more we could have learned from SARS. Ignoring China, the Taiwanese government doesn’t take orders from them and certainly wouldn’t help with a cover up but because of SARS all it took was Li Wenliang‘s post leaking for them to activate a comprehensive response. The key part was recent memory overriding the “it’ll be awfully inconvenient” reflex which is hard to avoid when you’ve been comfortable for many years.
It wasn't Li Wenliang's post that activated the Taiwanese response. It was the Chinese government's public alert on 30 December 2019 about a cluster of patients with "pneumonia of unknown etiology" that triggered the response.
That announcement came after top Taiwanese medical officials had seen those social media posts, realized how serious they looked, and started asking China about them.
> In the wee hours of Dec. 31, 2019, CDC deputy chief Lo Yi-chun could not sleep and was scrolling his phone when an online post shared in a CDC chat group caught his attention.
> Quoting information from Chinese websites, the post that appeared on PTT, one of Taiwan's largest internet bulletin board systems (BBS), warned about the potential danger of a SARS-like disease that was spreading in the Chinese city of Wuhan.
> "The post came out (on PTT) at 2 a.m., and at 3 a.m., I saw it being shared on a chat group by another sleepless CDC doctor," Lo said at a press conference Thursday.
> Lo said the post immediately caught his eye because unlike other unsubstantiated online messages this one included a chest CT scan, a hospital test result and what appeared to be a screenshot of messages sent by a doctor to his colleagues, warning them of a highly contagious virus.
> That announcement came after top Taiwanese medical officials had seen those social media posts, realized how serious they looked, and started asking China about them.
The first announcement from the Chinese government came on 30 December 2019, one day before the events described in your second article. ProMED-Mail sent out an alert on 30 December 2019,[1] and the next day, the outbreak was even reported on CCTV.[2] Social media posts gave additional information, but the existence of an outbreak of likely viral pneumonia was publicly declared before those posts, and people who follow emerging infectious diseases were following the story.
I think the other reason non PHP devs think we are in the dark ages is because when they google it, our documentation looks like it's from 2010. It's a bit of a joke really.
One other thing I always found iffy is the comment section. Why is the information there not reviewed and back-ported into the documentation? Sometimes, as on the page of the `DateTime` class, they actually contain crucial details!
Just so you're aware, it's a limitation within Firefox and Private mode - not Bitwarden.
```
The Bitwarden browser extension does not completely function in Firefox’s private browsing mode. This is a known issue specific only to Firefox. You will see a message indicating so when you try to open the Bitwarden popup window in a private window. We have discussed the problem with Mozilla, however, they seem unable to fix it so that extensions like Bitwarden can function entirely in private mode.
```
As I mentioned, this stopped working after Mozilla deprecated, and subsequently removed an API due to security concerns. When viewing the docs for said API, they have clearly outlined an alternative mechasmin. They have still stuck to blaming Mozilla.
An individual raised a working PR to fix this that got reviewed and some changes were requested. The individual must have abandoned the PR or something because it hasn't moved since. I would have expected Bitwarden devs to pick this up and get it merged, and address the PR changes themselves since OP isn't addressing the issues.
