Timeline
Post
Remote status
Fetching context…
This post replies to something we haven't fetched yet. We'll try to pull in the missing thread context in the background.
I wanted raw inference API access. A curl script and nvim wasn't enough, too much hassle just to see the <think> tokens and being able to edit them
If you use a UI over these, you cannot edit the reasoning. It says "not supported". Why is it not supported? Who knows. It's just a fucking string dude.
Anyway. I explained this in detail to the clanker and told it to implement the v1/completions API. Foolish as I am, I forgot that the geniuses at openAI named the successor API v1/chat/completions.
So of course it got confused
I told the AI multiple times that I want a fucking string buffer on the screen and just to append to that, and in the background, unbeknownst to me, it built a fucking dictionary, a parser, multiple roles. All that to just fucking concat it to a single string in the end, making the whole thing pointless.
This balooned the code up to 10x the size it had to be though. What a waste of time
If you use a UI over these, you cannot edit the reasoning. It says "not supported". Why is it not supported? Who knows. It's just a fucking string dude.
Anyway. I explained this in detail to the clanker and told it to implement the v1/completions API. Foolish as I am, I forgot that the geniuses at openAI named the successor API v1/chat/completions.
So of course it got confused
I told the AI multiple times that I want a fucking string buffer on the screen and just to append to that, and in the background, unbeknownst to me, it built a fucking dictionary, a parser, multiple roles. All that to just fucking concat it to a single string in the end, making the whole thing pointless.
This balooned the code up to 10x the size it had to be though. What a waste of time
Replies
0Fetching replies…