The idea that you can just fork large repos, make little feature changes, and then you're done, is _nothing but lies and advertisements_. But, I repeat myself. Software is never done and maintaining a fork is a total pain. Constantly stuck responding to changes you didn't want and security-patching the libraries and revamping to stay compatible and... No, AI doesn't help. Not anymore. It is now the problem, not the solution. It has increased the maintenance burden tenfold, by throwing the entire software ecosystem into chaos. We are just stumbling ahead of the AI-hackers, at this point, while trying to update features to stay relevant. You never know when the fork's source loses its maintainer and you are left up the creek without a repo paddle. And you never know when your AI slop is going to get hacked and the zap interface will allow someone to drain everyone's wallets. Do not listen to people who are trying to sell you their AI bullshit. Listen to the people who are out in the trenches, actually trying to use the bullshit. It is a jungle out there, kids.

I was watching some marketing podcasts and they kept repeating the point that engineers invariably reach for technical solutions, but often there are simple workflow changes that can do the same thing. And they often solve **the customer's real problem** better than the complex techy stuff. Forget about on-chain zaps. Here are payment targets integrated into the zap interface. You are welcome, Nostr. GM.

Finally getting around to de-spamming my orly relay.