jzebedee

I just watched him present it at Cloudflare Connect. He's quite serious.

It was a bit sad. Old man talks about existential risks of AI, gets scared, leans hard into "we'll use AI to save ourselves" as a gambit for hope.

Relevant change:

   Security bug fixes

    PR: Critical: fix: prevent template expansion from interfering with git repo initialization. When generating a new repository from a template repository, Forgejo clones the template repository, removes the .git folder, performs variable template expansion on files listed in .forgejo/template, and initializes a new git repository. During this process, variable template expansion could be misused in order to create a new .git folder, which git would adopt and incorporate during its initialization of a new git repository. A malicious template repository could be used to read arbitrary data from the Forgejo host, and to execute arbitrary processes on the Forgejo host, as a remote code execution attack. To address this issue, after variable expansion is completed, any existing .git folder is removed from the directory before the git repository is initialized.

I'm always curious where these moments of serendipity get their start. How'd you come to read Omar Khayyám's 11th-century poetry?

> Then that crazy bastard started taking photos of people's menus.

I don't get the reference. Is this a startup origin story?

The whole article is satire, parodying the overwrought ad copy designed to sell a simple appliance (electric kettle) to different marketing segments.

I think you can realize how ludicrous it is to invoke 80 year old copyrights for a product whose main use case is coding. How much code from 1946 was it lawfully ingesting?

No, of course not. They have zero domestic police authority for US citizens.

I was interested in the approach as a way to reduce DOM bloat, but it's clearly Claude's writing and visualizations.

Which is a competitive success story. It's much more profitable to avoid competition with abusive dynamic pricing and punish users for price-shopping.

It's a good reminder, because in the auth landscape I wish I had just picked up Keycloak and stuck with it. Commercial auth is a bad value proposition and not the kind of infrastructure where you want to have acquisition churn happening often.

The self-hosted space is another headache. I wasted so much time trying to make smaller self-hosted auth solutions work, since Keycloak has a reputation for being heavyweight.

I looked into the Ory stack extensively trying to actually use it as advertised for self-hosted / open-source auth. It's aggressively gimped and its SSO features are emphatically _not_ open-source and are gated behind licensing, with no way to find out until you're actually running it.

It's also just unfinished. Their "stack" is a lot of cobbled-together Go mixed with incompletely rebranded acquisitions like SAML Jackson (now "Polis"), which they managed to gut so completely it went from a best-in-class OSS library to unusable.