Comment

Comment by subscribed

So are we just holding it wrong, or is the distinct absence of any mechanism to tune/turn it off for our own good?

Also why you're so dismissive with the 2/4% figure while completely ignoring the TFA analysis and the other examples in their linked github issue?

Seriously, you're adding a feature that silently burns 15-25% tokens (that is burning money for API clients while hiding that fact), take away everything that could be used to mitigate it, and your response is basically, "eh, your numbers are unimportant and ours say it's negligible but since you complain we'll make it a bit cheaper".

Seriously, that looks so intentionally customer-hostile and revenue-friendly, but reading the room no one is surprised.

parent subscribed 2 days 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