Comment

Comment by mungoman2

In this case it could be solved by not letting the LLM consume the transaction message. Effectively the same as preventing user supplied info going to the first argument of printf().

The transaction in question can remain opaque to the LLM and a %transaction.message% string is resolved in the layer between the LLM and the user.

parent mungoman2 4 months ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton