I mean, honesty is a human trait. The humans who built that particular AI system biased the set of mysterious numbers (through reinforcement, filtering, etc.) so it assembles tokens in a way that conveys information about the properties and limitations of the system they built.

That's all.

Metrics are increasingly employed as trust deteriorates. Recommended reading ⬇️

#monktoberfest

a.co/d/im8AStV

Ref: Edgar H. Schein sloanreview.mit.edu/article/comi...

#monktoberfest

“Organizational culture is the pattern of basic assumptions that a given group has invented, discovered, or developed in learning to cope with its problems […], and that has worked well enough to be considered valid, and, therefore, to be taught to new members.”
The stories we tell are how we teach.

"apparently web traffic is down because Google is giving you an answer already in the results, and you no longer have the need to visit a website"

I mean, this has been a complaint for a while, even before AI entered the timeline? Who needs to go to a music lyrics website when it's in the Info Box?

"Piracy lost, but it was always going to lose. Streaming won."

But did the reader / listener / viewer win?

And did the content creators win?

🤔

I am happily paying Nabu Casa for Home Assistant Cloud.

And in the words of @booch.com “Every line of code represents a moral decision"

It’s really hard for OSS projects too. Imagine a leaked GH access token from a project maintainer who is not responding, and who is not an employee because OSS isn’t a company. How do you the project get that token revoked? You can’t. You have to de-list the maintainer from your GH org.

Tricky thing is when people have built their own automation (predating Actions), using CI/CD tools and services, making for something other than a “pure GitHub” implementation. 😬

That said: prevention > detection, as always

Also, speaking for myself, hurray for watchful, diligent security folks detecting things before vandals could fix their syntax error.

Later in 2023 GitHub changed the default permissions for access tokens.

Unfortunately this leaves older projects, organizations, and enterprises with an unsafe default.
github.blog/changelog/20...

“All this to prove one thing: that vulnerable workflows can’t keep a secret.”

This was true in 2023 as it is now. You have to make sure you scope down GitHub access tokens.

Here is a blog post that describes a similar problem as reported in CodeBuild in the context of GitHub Actions workers back in early 2023.
karimrahal.com/2023/01/05/g...

You can see what's on the menu of legal services when you set up a project here... LF Projects LLC is generally for software projects, Joint Development Foundation Projects, LLC is generally for standards development...
docs.linuxfoundation.org/lfx/project-...

It's a corporate holding structure of the Linux Foundation, used as the owner of intellectual property, etc.

A committed community of maintainers doesn't have a LLC registered in Delaware that can hold trademarks... This is infrastructure Linux Foundation provides.

lfprojects.org

Valkey is maintained by the Valkey maintainers, not by a neutral foundation. Linux Foundation provides the tent, but without committed maintainers the tent is empty.

The thing that keeps the power of any one company in check isn't the Linux foundation, it's a committed community of mutual interest.