I don't really understand that problem, exactly. I'm not aware of any restrictions for using AWS Identity Center (SSO) with an email address that happens to be a root email for another AWS account.
I checked the documentation but I couldn't find anything to show this to be a problem other than that the practice is discouraged.
I create "job function" DLs. "Company-Region-IT Manager". Then give that DL it's own SMTP address. Then use that.
It's really nice when you have to hire someone new for the position. You add them to the DL and they're automatically in control of all those accounts.
Or you don't have employees using their personal email to open corporate accounts.
Still on Amazon to clearly tell people it is this way so they can properly plan for it, but employee's email addresses really shouldn't be used for the root account.
That’s not what’s being described here. What OP described is the much more common situation where employees use a personal phone for MFA. Sure, some places issue hardware dongles and disallow authenticator apps on your personal phone, but IME most places default to just having people use their phone.
Some tax forms like NY State fill-in forms have some scripted functionality that requires Adobe Acrobat to work, and they block rendering from other PDF programs. Even worse, once you've filled in the form, their PDF then blocks Acrobat from exporting to a normal PDF (the way you can save a print preview to a PDF for later) and so the only way you can get a real PDF of it is to print it directly and then scan it back to your computer.
Aerc lets you do this, although it doesn't automatically fill it in based on the recipient in a reply. So you have to remember to adjust the sender for each email that you send.
I think the parent was correct in the use of the word "Risk"; it's different than your definition, which appears to be closer to "likelihood".
Risk is a combination of likelihood and impact. If "risk" were just equivalent to "likelihood" then leaving without an umbrella on a cloudy day would be a "high-risk situation".
A rational person needs to weigh both the likelihood and impact of a threat in order to properly evaluate its risk. In many cases, the impact is high enough that even a low likelihood needs to be addressed.
Thanks. This focuses on the most common daily need, with really clean design and display of information, and live updates as a flourish. Definitely sparks joy.
The third book is incredible. I actually started with that one accidentally but don't regret it at all; it gets more interesting much more quickly than the first book.
It's definitely the case that the characters are just a vehicle for exploring these science fiction concepts, but the ideas are so clever and imaginative that I can forgive it most of the time.
I agree, The story in a story in an attempt to talk over the heads of the Trisolarans is hilarious. Too bad they never learned to paint in non western perspective.
When Obsidian launched, there was already a lot of hype building in the note-taking community around Zettelkasten and Roam Research. With Roam, basically any word in your note could immediately link to another note, and you could see backlinks in your notes prominently.
However, Roam was both expensive and online-only, so when Obsidian came out and it was: a) polished, b) provided most of the functionality of Roam, and c) was offline and plain-text (also unlike Notion), it was an immediate hit.
The other special feature Obsidian offered was easy and powerful customization. The major settings are actually core plugins that can be enabled or disabled (like daily journal, tagging, or slideshows). Plugins and themes are easily discovered and installed from inside the app, which has led to a vibrant and popular plugin community. All you need is one plugin to be indispensable for users to never leave.
