lkurtz

I believe it is because it includes a suite of enterprise management features in addition to Gmail-related features. (Search for "google basic mobile device management" for more info.)

Cryptography is a tool that turns arbitrary problems into key management problems. It doesn't solve problems, but it constrains them in useful ways.

There are certainly valid, conflicting opinions around signing/notarization requirements for software. But notarization does provide end users with some safety guarantees that legitimately make running the software less risky. The scariness of "are you sure you want to run this" prompts is fairly grounded in real risk assumed by the end user.

There are a couple of legitimate reasons, namely the expense/KYC process of an Apple Developer Program membership and/or the complexity of integrating signing + notarization into existing build pipelines (but XCode does makes it pretty straightforward to cut an ad-hoc release that is signed and notarized).

In my opinion at least, the most likely reason is that Apple is refusing to notarize the software. If this is the case, people really should not be running it.

Recommending (and running) `xattr -c` can be extremely dangerous. I would suggest withholding Mac releases until they can be distributed/run safely.

In your example, replacing bulky self-checkout machines (analogous to removing road/surface parking real estate) offers a significant benefit to everyone. More room for what everyone actually wants most: books. The preference for self-checkout machines forces a cost on everyone for the benefit of a few.

I don’t think this analogy is quite correct. Driving on a particular route is not a driver’s objective like reading a particular book is a reader’s objective. The driver’s objective is arriving at a destination. The objective in driving is not a finite resource, but the multiple route options to the objective can be, which differs substantially from a library queue.

Injinji is the best I've tried so far

See also https://openfga.dev/, Auth0's open-source ReBAC solution

1p has some native support for hardware keys (https://support.1password.com/security-key/), but you can always use Yubico Authenticator for any applications that force you to use TOTP.

Only if they’re used. There are no DMARC records in place for harvard.edu or subdomains, which is kinda shocking.

Wow, very surprised to see no DMARC records in place for harvard.edu or their various subdomains. It may be possible that a single DNS record could have prevented this whole madness.

Passwords crack at a rate of 5000/second on my 3 year old, super bad GPU laptop :-/

FINALLY.

The whole thing is a splash page. :rimshot:

Whenever you go out to sea... well... just don't go out to sea.

You mean Goldman calling up a friend at the FBI doesn't count as probable cause??

My favorite part is how it skips at random to arbitrary points of other episodes when playing Podcasts.

Shenzhen?

$10 cash or $15 of Red Bull product.

The Google Spreadsheet example is admittedly a reach. It's mostly just a demonstration of how flexible Sprig can be with data formats.

That's a very interesting idea to use YAML's self-reference syntax. Although a lot of the value of this gem comes from the seed organization across different record-type-specific files, and I think YAML's self-referential syntax might make cross-file referencing a bit more difficult for the user. Good thing to keep in mind for the future though, especially once everyone is on board the YAML train.

Do you have another place/system for persisting that you've success with in the past? I've always felt that seeds are designed to be the place to persist record data in the repo.