Because I see this becoming bigger than me and a separate organization made sense. There is a super thin backend component right now too. There is the potential to also add in some extra features that require a server/db. I'm kind of inspired by the atuin model of things.
I've got a LONG list of features I'd like to implement over time.
You said factual. But what is factual for you and I may not be for someone else. There are a lot of recollections in the article where sama remembers one version or doesn't remember at all and the other party remembers something else. Combine that with the nature of the article and the legal issues considering egos and sums involved. To top all of that New Yorker is known for fact checking that is exhaustive to the point of paranoia.
I am just speculating but if @ronanfarrow is still checking the discussion here, it would be amazing to hear the actual reasons.
> There are a lot of recollections in the article where sama remembers one version or doesn't remember at all and the other party remembers something else.
Unfortunately not right now, it's in the works. Polyphonic guitar to midi is a problem I am yet to understand and try solving in this one. Jam Origin's Midi Guitar is good like that, I still need to get there.
Everyone is surprised at the $300k/year figure, but that seems on the low end. My previous work place spends tens of millions a year on GPU continuous integration tests.
Is this what the legal request demanded or is this just something that OpenCode is doing out of spite? Seems unclear. To me the meat of this change is that they're removing support for `opencode-anthropic-auth` and the prompt text that allows OpenCode to mimic Claude Code behavior. They have been skirting the intent of the original C&D for awhile now with these auth plugins and prompt text.
Using your API key in third-party harnesses has always been allowed. They just don't like using the subsidized subscription plan outside of first-party harnesses. So this seems to be out of spite
Out of curiosity, why did you make a new Github account for the extension instead of developing it on your own account?
reply