I remember when Facebook had this function to auto-upload all photos, in private, so that you could then easily publish them from your desktop.

Of course, this was before I was smart enough to know they didn't do this out of the good of their hearts...

Claude has passkey support.

It's useless though. One passkey max. And login still requires email and there's no button on login page for passkey login. And it can't be f*ing removed. It's a joke. A trillion dollar company, lol.

Same with CVS. Once enrolled, no way to reset it.

Enforced through GitHub Actions that is :)

It's interesting. First banks, now airlines.

What are airlines they really afraid of? That people get an advantage by comparing prices?

And for banks, for years US banks have managed to keep data internally, only exposing it through Plaid, and thus getting paid for it. API like the PSD2 in Europe allow me to connect my software to pull in the transactions for free. In the US you have to hand over money to say Monarch.

Airline margins are incredibly thin.

They want a person to go through the checkout flow because people might click on the high margin ad-ons they offer. United has a bunch.

One could write an action that executes a shell script that does docker pull abc:latest.

As the consumer of an action that becomes really hard to find out unless I take the whole codebase apart.

> As the consumer of an action that becomes really hard to find out unless I take the whole codebase apart.

Maybe it's just me, but I only use (public) Actions I'm able to review in an hour or less, meaning less than 5K LOC or so. Not sure how people are able to just "consume" 3rd party GitHub Actions and not even review what exactly they do, how are people comfortable with the risks this opens up? It's literally supply-chain wild west, but seemingly people continue like it's 2010.

I remember asking this to one of the evangelists when AWS first came out, how do I run this locally. This was during the times where we actually tried to get all the .NET and C/C++ docs locally.

Now doing the math I feel old.

There was an offline help system in Visual Studio Community 2012 that would cheerfully download all the help files as a pseudo-.zip file, and for sure included both .NET and C++, along with SQL Server and it's my _recollection_ it included Office's OpenXML documentation, too

I visit https://status.github.com it is the second suggestion, after https://github.com/ itself.

But their auto generated API clients don't have the invariant baked into them, which makes them very rough to use in say Rust.

They'll have something like this:

    MySchema:
      type: object
      properties:
        enum_member:   { enum: [foo, bar] }
        enum_member_2: { enum: [quz, qux] }
      if:   { properties: { enum_member: { const: bar } } }
      then: { required: [enum_member_2] }

Except, this is not defined in schemas, this is merely defined in prose around the documentation.

So your Rust API is full of Option, and it gets really annoying when you're testing things like say Bedrock, which takes 10 minutes, and then fails because what you submitted 10 minutes before doesn't match their schema.

I understand this can be fixed by reading the documentation in more detail, but it has gotten so verbose, and sometimes you just want to start something.

The documentation is not detailed enough, you need to call the service for detailed correctness.

I find it weird that it's okay for a city to pay someone to come around to collect the coins, at no additional cost to the customer, but swiping/tapping? Absolutely not, that must be passed through to the customer.

I'm sure for the city tap to pay is cheaper for them than collecting the $, even without a fee.

In most countries debit/credit fees are far less than the fees to deposit cash in a bank.

The main purpose for taking cash is tax evasion, which outweighs the increased cost of cash handling.

Cities have plenty of employees without much to do.

Coins, being cash, are simple, require no apps, smartphones, batteries, tracking, ads, or privacy violations.

GitHub itself has support for it through dynamic workflows, but us mortal humans are not allowed to create those.