HERMES.md in commit messages causes requests to route to extra usage billing
211–220 of 568 posts
Re: HERMES.md in commit messages causes requests to route to extra usage billing
#212Earlier quoted context omitted.
My insurance company and Synology would be my first targets. I'd gladly throw ~1k at each. Of course, I suspect the true business model to be to do nothing. You sell the "service" to people customers, but your enterprise customers pay you a subscription fee to not execute the order. ELaaS: Everybody Loses as a Service
You must have worked for Yelp
Suppose an enterprise customer released a new update that everyone absolutely hates, so angry customers are are more likely to wage war on their bots with the company's anti-bot token-draining mechanism: "Oh, whoops! Looks like you're in surge pricing territory. We can only refuse to do nothing for so long before we start to lose credibility with our people customers, so what would have been a subscription fee has now slipped into premium pricing territory!"
(Forgive my math below; avoiding coffee today.)
Surge pricing for Denial of, Denial of Chat Bot Token rate: (personPaymentPerHour + averagePricePerPersonPaid) * daysLeftInPaymentCycle ^ (hatePerPerson / time) + 1
hatePerPerson can be calculated as the averaged comment-to-upvote (or upvote to downvote, if available) across Social Media platforms.
If you want to be exceptionally malicious, you can also offer dynamic discounting to the person customers at the same time, to drive up the surge pricing even higher!
I would call this unethical but, well, every aspect of it kind of is. Everything from the service existing, to the the people participating, to the secret backend service, to the enterprise customers paying for that secret backend service. Might as well drain as much dosh from everyone as you can, if everyone is tip toeing in that dark-grey area anyway. :)
You know what? If I have time, I might even make a mock site to sketch all of this out. I've been meaning to come across a fun little project. This could work! lol
Re: HERMES.md in commit messages causes requests to route to extra usage billing
#213Re: HERMES.md in commit messages causes requests to route to extra usage billing
#214> However, I need to let you know that we are unable to issue compensation for degraded service or *technical errors* that result in incorrect billing routing. This is very surprising. I've never seen a legitimate business not give refunds for technical errors of their own fault. Minimum Anthropic should credit the full amount to them.
Wait, that was the actual response? With the DiCaprio clap? That wasn't a joke?
Re: HERMES.md in commit messages causes requests to route to extra usage billing
#215Earlier quoted context omitted.
Anthropic doesn't even use their own harnesses for their support chatbots (they're using fin.ai) - that's how little support matters to them. Seems like either you get attention on HN, know someone working there, or are at a large enough company to have an enterprise contact - otherwise, no reply.
They saw how Google providing absolutely terrible customer service for a very long time has done nothing to hurt their bottom line and decided to copy.
Re: HERMES.md in commit messages causes requests to route to extra usage billing
#216Earlier quoted context omitted.
I get the confusion -- it looks like the reporter of the bug just posted a raw email response that they got without adding any sort of decoration to make it clear it was from an email they got. At least, that's my reading of this. I'm also not sure if the person/bot who responded was saying "No refund" or that they couldn't issue a refund, or if a Github Issue was an appropriate place to ask for a refund. Let's hope…
Thanks. That makes sense, and the thread reads differently to me now. I’m not hopeful the guy will see any refund.
Re: HERMES.md in commit messages causes requests to route to extra usage billing
#217Earlier quoted context omitted.
The official response feels AI generated. I suspect this is a preview of our future. "You're totally right! I'm sorry but you're going to have to piss off anyway. Would you like to spend a few more hours discussing it with our AI chatbot? It won't help. But if it makes you feel better, it will probably cost us an extra $0.12 in tokens." I'll bet the first human at Anthropic learns about this from HN.
"Thank you so much for your thoughtful, candid feedback. You are absolutely right to be annoyed. I was overeager, lazy and not correct in my initial response when I said we will not be issuing a refund. However we will not be issuing a refund."
https://arstechnica.com/tech-policy/2024/02/air-canada-must-...
Re: HERMES.md in commit messages causes requests to route to extra usage billing
#218Earlier quoted context omitted.
Anthropic doesn't even use their own harnesses for their support chatbots (they're using fin.ai) - that's how little support matters to them. Seems like either you get attention on HN, know someone working there, or are at a large enough company to have an enterprise contact - otherwise, no reply.
Huh? Why wouldn’t they just spin up the current help-desk darling? (Intercom) Rolling their own seems silly.
But isn't AI going to destroy all current software vendors?? Everybody is going to roll their own?? In fact, AIs will handle all support autonomously?? I mean they can spin up their database if needed?? What more do they need?
Hence the SAAS apocalypse...
Oh wait... this sarcasm will get me targeted by the LessWrong AI god when he/she/it becomes omnipotent....
Re: HERMES.md in commit messages causes requests to route to extra usage billing
#219> However, I need to let you know that we are unable to issue compensation for degraded service or *technical errors* that result in incorrect billing routing. This is very surprising. I've never seen a legitimate business not give refunds for technical errors of their own fault. Minimum Anthropic should credit the full amount to them.