Yeah, I noticed that a bit, too. I originally meant the megathread post itself. I try not to read too many comments in such threads on Reddit; regardless of the topic ;)
Said family member mentioned in the parent thread keeps a handheld radio (I don't know the exact tech specs, sorry) for such occasions. That said, they mostly use it to just listen for any logging trucks calling out checkpoints so they can avoid getting in their way when travelling to their remote campsites.
Coupled with a Garmin inReach w/ backcountry maps installed, it gives us peace of mind in case something goes wrong out in the bush.
They frequently go camping with their family in the interior of BC so they always have one for emergencies. I agree they can be pricey, but it obviously paid for itself just in this situation alone :)
One of my family members has been stuck just east of Hope, British Columbia[1] for almost two days now. There is currently no cell service, but luckily they have a Garmin inReach so we can communicate via its SMS feature.
For anybody with friends/family in the area, the BC subreddit megathread[2] on this is a good starting place to get information on evacuations, power outage status, road closures, official relevant Twitter accounts, etc.
Each AWS partition can have its own browser support SLA. China's AWS console has its own [1], although it almost overlaps completely with the "classic" AWS console [2].
For the government/secret partition, I have no clue what their SLA is, but it wouldn't be a leap to assume they may something different.
Another nice add-on to this format within my department is that we utilize an internal retro tool for people to post their questions for discussion.
After the 20ish or minutes of silent reading, we give people ~5min to post their questions for all others to see in real-time. We then give people a set number of votes and the presenter goes through the list answering the questions in descending order of votes.
I was hesitant at first when they introduced this (since it felt like more red tape), but I've found it helps focus the discussion on the most important feedback while avoiding one person bikeshedding the discussion time right at the beginning.
I especially do not envy the UX designer & copywriting staff that may have to address this across of all AWS' consoles/public documentation.
I've worked with UX/UI designers across multiple companies for over a decade, and the simpler something seems (i.e. making a new logo) the more time & resources it usually takes to do properly.
If this truly comes to pass, then I couldn't imagine the difficulty of having to re-brand AWS in China that'll make both the CCP and AWS' leadership happy.