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

Points: 1

# Comments: 0

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

Points: 1

# Comments: 1

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

Points: 2

# Comments: 2

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

Points: 1

# Comments: 0

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

Points: 1

# Comments: 0

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

Points: 2

# Comments: 0

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

Points: 3

# Comments: 0

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

Points: 4

# Comments: 1

RipStop is a node package implementing a set of rules that consumers can use to protect their repos from wilder actions by LLM agents. A consumer needs only a few lines of code to configure the rules they wish to apply. Example rules: no PII in commits, no Git actions that interfere with the Git history and thus might impact your ability to recover from problems.

I built this for two main reasons: - in my own repos I had a few incidents - in one Claude Code erased some un-staged changes, and in another started trying to roll back some commits. - I was reflecting on why agentic development is slow on the uptake in corporate environments. One possibility is fear of the wilder actions LLMs take - so I thought it might be helpful to illustrate how to control these.

The security model is as follows: - Layer 1 - guidance to the LLM in AGENTS.md or CLAUDE.md. This is of course guidance, and gets forgotten if context rot sets in. - Layer 2 - Git controls, via hooks that get fired automatically on various actions. Higher hurdle - the LLM would need to generate very specific commands to get round these. This is the space I am aiming at. BTW we also generate a file to go into AGENTS.md to tell the agent the environment it is working in and the controls the consumer has chosen, so there is a bit of layer 1. - Layer 3 - containers with hard configuration. Not trying to go this far in this package. This is really the space the major labs are going after with cloud agents.

I think it might be useful in two domains: - People running local agents who want a little more safety - A POC for corporate controls

Feel free to look, provide commentary, and use.

Jon

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

Points: 2

# Comments: 1

This library solves the problem of ensuring that sensitive endpoints do not trigger side-effects multiple times - this is especially useful for any endpoints that handle financial operations. Currently, the library supports Spring MVC (Servlet-based) applications and MySQL and PostgreSQL with jdbc regarding storage backends. It is very simple to integrate, all that you have to do is add @Idempotent to any endpoints that need idempotency.

Full explanation of the functionalities and configuration is available in the readme of the repository. Repository : https://github.com/josipmusa/idempotency4j

I would love any feedback or review regarding the implementation - also, any recommendation is welcome.

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

Points: 2

# Comments: 1

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

Points: 3

# Comments: 1

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

Points: 4

# Comments: 2

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

Points: 2

# Comments: 0

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

Points: 3

# Comments: 0

When I was a kid and was playing soccer in my home town, my Dad had an idea - what if there was a correlation between a successful soccer player in a specific position and the birth month - i.e., can we determine based on a player's month of birth if he could statistically become a good goalkeeper, defender, midfielder, or an attacker? Obviously, back then the data was hard to come by and I did not think too much about it until recently.

Now, I'm my Dad's age when he vocalized the idea to me, he is still alive, and I felt an obligation to to build something to help him his own stats. That's main the reason I started to build the dataset for the World Cup API, which eventually grew as more data points were introduced. over a few weekends because LLMs are genuinely.

What you can find right now is - every World Cup since 1930, every group standing, every squad, every scorer, every match, every venue, etc. etc. etc.

In addition to the API, I've also wrapped it in an MCP and published it out for folks to play around and provide feedback.

I've also built a live sample dashboard if you want to preview without installing anything: https://api.zafronix.com/wc-explorer/

Otherwise, you can get started with a free API key takes 30 seconds, 1,000 req/day, no card. Repo + install: https://glama.ai/mcp/servers/zafronix/wc-mcp or find it on ChatGPT and Claude marketplace.

Like I said, looking for constructive feedback.

Thanks HN!

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

Points: 1

# Comments: 2

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

Points: 2

# Comments: 0

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

Points: 1

# Comments: 0

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

Points: 9

# Comments: 0

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

Points: 3

# Comments: 0

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

Points: 9

# Comments: 3