Hacker News

Subscribe to Hacker News feed
Hacker News RSS
Updated: 37 min 24 sec ago

When a Platform Stops Saying "Automation" and Starts Saying "LLM"

Sat, 02/21/2026 - 3:36pm

Enforcement Risk Dossier | PlatformPolicy Risk Brief

… On January 20, 2026, eBay did not launch a feature. It revised a clause that governs access. Previous language prohibited “automated means.” Updated language (binding February 20, 2026) explicitly names: “buy-for-me agents, LLM-driven bots, or any end-to-end flow that attempts to place orders without human review…” That parenthetical is the structural shift. AI agents moved from implied coverage to explicit contractual identity. What was once broad and interpretive became specific and enforceable. When categories are named, interpretive space narrows. Narrower interpretation reduces enforcement latency. Reduced latency expands unilateral control over the access layer. … From Technical Signal to Contractual Codification December 2025: eBay robots.txt prohibited the same AI categories. Bots from named AI companies were restricted; selected integrations retained access.

Sequence: Technical constraint -> Named AI blocking -> Contractual embedding. In parallel, Amazon escalated against Perplexity’s Comet AI agent (cease-and-desist October 31; federal complaint November 4, 2025). Technical signals precede legal escalation; legal escalation precedes contractual hardening; contractual hardening precedes enforceable restriction. Specification replaces ambiguity and creates executable breach conditions. … Why Naming Changes Power Generic bans require interpretation. Explicit AI constructs reduce legal and computational uncertainty.

Explicit categorization enables: deterministic breach classification automated detection at scale faster enforcement stronger arbitration posture Machine-readable prohibition lowers cost and increases enforcement velocity. Velocity of classification becomes velocity of revenue impact. … Structural Dependency Asymmetry (SDA) The same update broadened arbitration and class waivers. Continued use constitutes binding acceptance. Substantive authority consolidated. Procedural leverage narrowed.

Structural Dependency Asymmetry: a regime where access rules may be modified unilaterally while dependent revenue remains revocable and dispute channels fragment. Under SDA, control over the access layer becomes the underwriting variable. Identical revenue lines trade at different multiples depending on who controls definitional authority. … Capital Implication For RAG pipelines, automated pricing engines, and agentic checkout flows, revenue becomes contract-contingent. Contract-contingent revenue carries structural variance. Higher variance increases discount rates and compresses valuation multiples.

Interpretation risk becomes pricing risk. … Conclusion This is not a minor automation policy revision. It is the codification of AI agency inside enforceable contract language.

What changed is the specification of agency. What it means is the repricing of dependency.

Comments URL: https://news.ycombinator.com/item?id=47104444

Points: 1

# Comments: 0

Categories: Hacker News

Ask HN: How do you test your MyBatis dynamic SQL queries?

Sat, 02/21/2026 - 2:52pm

(Full Disclosure: I am developing this plugin and drafting this post with the assistance of AI agents. It’s been an eye-opening experiment in how AI can help "scratch an itch" faster than ever.)

I’m currently working on a project using MyBatis, and one of the biggest friction points for me is verifying dynamic SQL. Whenever I have a complex query with , , or OGNL expressions, the feedback loop is painfully slow.

My current "workflow" (which I find incredibly tedious) is: 1. Copy the raw SQL from the XML mapper. 2. Manually scrub the XML tags like and . 3. Replace all #{param} placeholders with actual values, one by one. (or :param) 4. Finally, paste the cleaned-up SQL into the IDE’s database console to see if it even runs.

I was surprised to find that, despite many MyBatis plugins existing, none of them seem to offer a "direct execution with parameters" feature within the IDE. I expected this to be a standard feature by now, but it feels like we’re still stuck with manual labor for query verification.

To solve this, I’m building an IntelliJ plugin () that: - Automatically detects parameters in your SQL (XML or Annotations). - Prompts for values and evaluates all dynamic tags/OGNL on the fly. - Executes the final native SQL directly via the IDE’s built-in database tools.

I’m curious to hear from the HN community: 1. If I were to release a tool like this, would it be something you’d actually find useful in your daily work? I'm trying to gauge if others share this specific frustration. 2. How do you currently verify your complex MyBatis queries before they hit production? 3. Are there any specific edge cases or reasons why you think this kind of "direct execution" hasn't been widely implemented yet?

I'm eager to hear your thoughts and suggestions. Many thanks for your feedback!

Comments URL: https://news.ycombinator.com/item?id=47104032

Points: 1

# Comments: 0

Categories: Hacker News

Show HN: AI Agent for SEO

Sat, 02/21/2026 - 2:52pm

Article URL: https://usefox.ai/

Comments URL: https://news.ycombinator.com/item?id=47104023

Points: 1

# Comments: 0

Categories: Hacker News

Identity Theft 2.0

Sat, 02/21/2026 - 2:36pm

Article URL: https://rekt.news/identity-theft-2

Comments URL: https://news.ycombinator.com/item?id=47103902

Points: 1

# Comments: 0

Categories: Hacker News

Ask HN: Do You Love My "Assess Idea" (AI) Robo-Reply Side Project Idea?

Sat, 02/21/2026 - 2:34pm

Chime in, HN, with the feasibility of the following idea for a side project…

_____________

User Story

As a reader logged in to Hacker News on a locally running web browser, I want a process running on my device that polls for "Show HN" posts and automatically replies to them — as me — with the results of an LLM-analyzed critique of the posted projects discovered by the process.

Acceptance Criteria

• A brutally frank critique of the posted "Show HN" project is given by a state-of-the-art LLM

• A count of existing projects functionally identical to the post being critiqued is displayed

• A list of authoritative learning resources on whatever the LLM determined the author is probably trying to accomplish is provided

• …???…

_____________

FWIW: Even with the well-documented initial inertia-reducing powers of today's coding agents, it's super, super unlikely that I'll ever get around to implementing this idea myself.

I'd be totally cool with somebody else taking a swing at it, though.

Comments URL: https://news.ycombinator.com/item?id=47103891

Points: 1

# Comments: 0

Categories: Hacker News

The Power of Constraints

Sat, 02/21/2026 - 2:29pm
Categories: Hacker News

The Broken Record

Sat, 02/21/2026 - 2:27pm
Categories: Hacker News

Pages