tyzoid

Are you factoring in fixed costs to that estimate? That may be partially misleading if so.

I suspect the TOS say google can remove or deny apps for any reason. If in the EU, there might be a DMA claim though.

No - this is a false equivalence. Transaction processing companies for the most part handle the in-and-out flows as a single transaction. Insurance companies hold on to the premium pool ("float") for long enough that they have time to realize gains from investing portions of it - the inflow and outflow are very separate.

Isn't most of this already in xlibre?

Out of curiousity, how does this apply to nightmares ending in certain death or grevious injury (driving off a bridge, falling down a well, being chased by zombies and unable to move, etc.)?

Harness refers to the tooling that allows you to interact with an LLM. Web chat interface is a harness, CLI coding tools (claude code, codex, opencode, pi, etc.) are harnesses, agent systems (openclaw, hermes, etc.) are harnesses. They present different capabilities to the underlying LLM. Codex, for example, is more likely to write code if you say "I want to build an app" than ChatGPT on web will.

Why qwen 2.5 everywhere? Why not 3.5?

How does this work on pages that require JavaScript in order to render?

I'll sometimes use agent swarms for triaging quickly through a number of possible issues. For example, a single request for a code review to uncover all possible issues, followed by an agent swarm to dig deep into each issue to confirm or mark false positive.

Domo Says No Mo' to AI FOMO

Hey, fancy seeing you up here on HN! Fun article

You can use something like flyway on top of your existing git/cicd stack. Write the query as a migration, have it reviewed using your git code review process, and merge to run the migration.

It doesn't even need to be a third party. Documents you make for yourself but never send to a third party could still be seized in a criminal context or subject to discovery in a civil one.

Attorney-client privilege is a special carve out because the courts have recognized that clients need to be open and honest with their attorneys to get proper counsel and representation.

This ruling is the court declining to extend that special carve out to non-lawyer AI tooling, and keeping the status quo of contemporaneous documents made by someone discoverable, whether or not shared with a third party. The judge draws from the TOS as an admonishment, effectively saying (my words, not the judge) the TOS should have put you on notice that you have no expectation this data is confidential.

Pretty much any legacy system can have a modern reverse proxy in front of it. If the legacy application can't handler certs sanely, use the reverse proxy for terminating TLS.