noahmasur

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.

You can always use plus-addressing if your email provider supports that. AWS considers plus-addressed root emails to be unique.

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.

Basically the last third of the book is a bibliography. It's filled with tons of scientific references.

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.

> What is it that people love about Obsidian?

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.

Usually it’s caching build artifacts between runs, or uploading packages or container images for private deployment.

That’s why it’s only on transactions over $10.

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.