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.
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.
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.
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.
They also have 1Password Connect, which allows you to bridge an API into your data for automation workflows, Terraform, syncing with Kubernetes, HashiCorp Vault, etc.
Your browser can still be fingerprinted without cookies. The site just needs enough unique information (user agent, timezone, screen size, IP, operating system, country, etc.) to form a trackable identity.
> My current solution is to share my ~/aws/config with everyone so we all have the same profile names and scripts can work for everyone.
If you're on Mac/Linux you could have everyone use direnv. Add a .envrc file in each git repo (or your script's subdirectory) with `export AWS_PROFILE=profilename`. Now everyone is working with the same profile names without having to pass around config files.
What happens when you have two projects that use two different versions of the same dependency?
With Nix, you can "install" many different versions of the same program side by side in the store, and then "activate" the one you need at runtime (or with direnv).
They may not qualify as AAA, but Hearthstone, League of Legends: Wild Rift, Kerbal Space Program, Cuphead, Gwent, Genshin Impact, ReCore, Ori 1 and 2, Hollow Knight, Fall Guys, Pillars of Eternity, Call of Duty Mobile, Subnautica, Firewatch, and Valheim are pretty big games; some indie hits but many are produced by major studios.
For one thing, I think the "powered by Unity" branding is a problem, because you only see it on games that couldn't afford to actually pay for Unity and therefore have a larger chance of being poorly polished.
The problem is that "inducing demand" for people who would otherwise take public transit doesn't actually increase efficiency. Putting more cars on the road is not necessarily a net benefit.
In the article they claim the package is literally stealing the IAM role credentials from the EC2’s metadata URL. So it’s presumed that the code is already running on your EC2.
Of course, just because it takes the credentials doesn’t mean it does anything else with them, but it could have done anything.
I checked the documentation but I couldn't find anything to show this to be a problem other than that the practice is discouraged.