Is anyone else having immense problems with this website due to Claude writing it?
Beyond the AI writing style and the pure amount of sentences, nothing seems to transmit the right information at the right time.
You need to read the entire page twice to get what is going on.
For example, the first text you read is:
—- Axtary checks the exact diff, message, query, or tool payload before a connector executes. Routine actions follow policy; higher-risk actions require approval of that exact payload. —-
Without having read the rest, nothing in this paragraph seems to tell me anything.
Only after I read the rest of the website do I somehow get what is even meant.
That’s fair feedback. I was trying to explain the product without under or overselling it, but I may have made the page too bloated. I’ll simplify the opening around few concrete examples and remove the extra explanation (haven't written or claimed anything that it doesn't do though..)
The intended model is that reusable policy automatically allows routine ones, denies the prohibited ones, and asks for approval only for a small set of higher risk actions maybe(that should hopefully reduce the approval fatigue).
Is anyone else having immense problems with this website due to Claude writing it?
Beyond the AI writing style and the pure amount of sentences, nothing seems to transmit the right information at the right time. You need to read the entire page twice to get what is going on.
For example, the first text you read is: —- Axtary checks the exact diff, message, query, or tool payload before a connector executes. Routine actions follow policy; higher-risk actions require approval of that exact payload. —-
Without having read the rest, nothing in this paragraph seems to tell me anything.
Only after I read the rest of the website do I somehow get what is even meant.
That’s fair feedback. I was trying to explain the product without under or overselling it, but I may have made the page too bloated. I’ll simplify the opening around few concrete examples and remove the extra explanation (haven't written or claimed anything that it doesn't do though..)
How do you deal with approval fatigue? In our experience users start rubber-stamping everything within a week, and then the whole layer is theater.
The intended model is that reusable policy automatically allows routine ones, denies the prohibited ones, and asks for approval only for a small set of higher risk actions maybe(that should hopefully reduce the approval fatigue).
[flagged]