cobbal

- The Sydney on the left must always lie

- The Sydnet on the right must always tell the truth

There are few miseries I deal with regularly that compare to SIP or the hardened runtime telling me I may not debug processes on a computer where I have root. If anything is going to make me abandon macOS (I've been using it since I was a child) it's the "security and privacy" features.

From the DMCA (emphasis added):

> A statement that the information in the notification is accurate, and under penalty of *perjury*, that the complaining party is authorized to act on behalf of the owner of an exclusive right that is allegedly in-fringed.

Though this may not refer to the falsehood here. See stackexchange (where I copy/pasted the above from): https://law.stackexchange.com/questions/51541/has-anyone-bee...

In a world where it's probably also saving a lot of lives. Ambulance sirens probably cause a couple extra accidents as drivers try to get out of the way. Doesn't mean we should stop trying; it means we should keep trying to improve.

That's one way to compile exceptions. There are other methods with different tradeoffs for different cases.

> On macOS, the Google Chrome executable is called `open -a "Google Chrome"`

This inaccuracy, in particular, feels more like mad-libs than reason

Pretty easy to convert humans into aqueous goo; I don't see the problem here.

Fail if someone checks the signature, but chatGPT would definitely pass the xkcd test: https://m.xkcd.com/1181/

When it comes to financial transactions, KYC laws mean that privacy is, in fact, illegal.

And one of the root keys in a GitHub action is "on" which will get turned into True by a compliant parser if unquoted

How much will you be charging for the adversarial network to allow someone to get any PR approved? ;)

I agree with you on swift. The evolution process seems to favor adding more "features" instead of unifying, simplifying concepts. For instance, we have special syntax for optionals, exceptions, asynchrony, coroutines (mostly hidden), and any other effects they decide to add in the future. Whereas in haskell, all you get is `do` syntax for describing these things. The trade off is that in haskell it's harder to learn the first thing, but then easy to pick up the rest. In swift, you have to learn how all these special effects interact.

I do a very similar thing. Sometimes when I describe my height, I'm "five and a half foot, nine"

Not to mention that poker is a game that rewards you for not getting caught lying. Fine for a game, but a problem if you're trying to draw life lessons from it.

Right. If you think about it as a function of the state itself, the 2 definitions agree. If the function is `f(x, state) -> (y, state')`, then f is "imperitively idempotent" when `g(state) = f(fixedX, state).state'` is "mathematically idempotent"

But even if you hit the "don't recommend" button on every "mix" playlist you see for months, don't expect YT to get the hint. I do wish the algorithm was a bit more tunable, but that's not really the Google way.

Because it's fun. Lots other good reasons, but to me this is the most important.

As a mac user, I was going to provide a flippant answer, but I decided to look into it instead. Personally, I use zsh or a custom built shell scripting library inside swift. Always like to see improvements to shells though. Googled for it and got a dozen guides on how to install it in mac, but none that actually explained how to use it. (One video result looked like it might have some info, but to me that doesn't count as documentation). All the documentation on powershell is targeted at windows devs, and it's just a very different culture.

Flippant answer: the CapitalizationConvention-ShouldScare-EveryoneAway

Sure, banks are also to blame for it. But I also don't think that excuses Plaid at all.

The reason I hate plaid is that they are training people to hand over bank passwords/2fa tokens to 3rd parties. And sometimes there are no alternatives available to the consumer.

U+1F4A8

That's wonderful. I'll leave the semantics of nucleons to the physicists though.

I see at least two compilers: zip and cat. :)

Baffles me too. By the same logic, Apple should not be able to sell phone cases without including a free phone in them.

If you break Apple Pay on your device, you can essentially get... your own credit card number. If you break open an e-$100 bill you get as many copies of that hundred dollars as you can spend before getting caught.

"verify funds locally via a dedicated or trusted computing environment located on the device itself"

This probably can't go wrong, and certainly wouldn't motivate groundbreaking research into breaking TPMs.

Unless your password manager displays a popup to be unlocked. Then that's spoofable too. Which is why I paranoidly move the popup to overlap the URL bar before unlocking.

Even better would be to link to the hash of the password, then there would be no way to guess.