Usage Guidelines Violation Fee
A rare occurrence for most users, when your request is deemed to be in violation of our usage guideline by our system, we will charge a $0.05 per request usage guidelines violation fee.
King-Aaron · 1h ago
Ah, the "say mean things about Elon tax"
trilogic · 1h ago
That´s one way of collecting tax LOL, but we can´t blame Elon for everything. Maybe is some team leader that feels very powerful, so much that, it thinks it can apply this cheat under radar.
BoorishBears · 1h ago
As I mention in the sibling comment there's a real cost for blocked requests.
I just checked and since the inception of my site I've spent a bit over $3000 on inference that was ultimately blocked from being shown to the end user.
And I have very permissive thresholds for the classifiers, the content getting blocked is "radioactive", not even toxic.
BoorishBears · 1h ago
More like the "gooner/jailbreak tax"
For my product I don't charge the user for blocked requests because content classifiers aren't perfect and sometimes trigger frivolously... but in theory a persistent user intentionally trying to push boundaries could cost me a lot of money: since I'm still paying for resources used to do the inference that was blocked.
This seems like an ok way to deal with that gap, but only if there's a reasonable amount of grace built in that they're not detailing here (since detailing it will result in people abusing right up until said grace expires)
trilogic · 1h ago
That make sense but...
It establishes a new precedent by imposing new standards on users which may be misused in the future. Policy is private and very difficult to define, it may be interpreted by gusto/convenience.
This can only be good for our business, HugstonOne will get more users, like exponentially fast :)
Usage Guidelines Violation Fee A rare occurrence for most users, when your request is deemed to be in violation of our usage guideline by our system, we will charge a $0.05 per request usage guidelines violation fee.
I just checked and since the inception of my site I've spent a bit over $3000 on inference that was ultimately blocked from being shown to the end user.
And I have very permissive thresholds for the classifiers, the content getting blocked is "radioactive", not even toxic.
For my product I don't charge the user for blocked requests because content classifiers aren't perfect and sometimes trigger frivolously... but in theory a persistent user intentionally trying to push boundaries could cost me a lot of money: since I'm still paying for resources used to do the inference that was blocked.
This seems like an ok way to deal with that gap, but only if there's a reasonable amount of grace built in that they're not detailing here (since detailing it will result in people abusing right up until said grace expires)
This can only be good for our business, HugstonOne will get more users, like exponentially fast :)