I'm sorry, but why is this on the front page with 2 up votes? Do we really need to be alerted every time the Claude API responds with an error?
Claude Seems Down
51–55 of 55 posts
Re: Claude Seems Down
#52Re: Claude Seems Down
#53Earlier quoted context omitted.
[flagged]
It’s not, you drink too much Kool-Aid, and your employer has too much money. Or the things you do are simply so irrelevant that nobody cares you’re sending stuff to a company of dubious morality.
Re: Claude Seems Down
#54Earlier quoted context omitted.
It’s not, you drink too much Kool-Aid, and your employer has too much money. Or the things you do are simply so irrelevant that nobody cares you’re sending stuff to a company of dubious morality.
Well which is it? Because the first one also contradicts the claim i'm responding to. I think those thinking their codebases are so novel as to not dare to provide to the providers are quite full of themselves. 99.9% of code is mundane.
Re: Claude Seems Down
#55Earlier quoted context omitted.
Well which is it? Because the first one also contradicts the claim i'm responding to. I think those thinking their codebases are so novel as to not dare to provide to the providers are quite full of themselves. 99.9% of code is mundane.
Nobody says novel. We just ”can’t send not our own intellectual property to a third party because contracts”. Then we roll out on premise. And we don’t miss anything, in fact we feel we gain more than we lose out. With proper tools we are not far off.