SomeonesAccount

6 ms·

1.
by SomeonesAccount 5d ago
exactly. all of these people complaining are using it wrong. you cant just expect a layer of abstraction to perfectly fix all the layers below it! plus, open router does a great job of handling a lot of the provider problems, but it literal
2.
by SomeonesAccount 5d ago
exactly. you can specify a provider in your request to openrouter, or, better yet, use the :exacto endpoint to make open router automatically choose one that is good at tool calls.
3.
OpenAI's next big AI model has 'entered the AGI era'(theverge.com)
5 points by SomeonesAccount 13d ago|0 comments
4.
by SomeonesAccount 13d ago
great article, very detailed
5.
by SomeonesAccount 20d ago
I wrote that slop comment
6.
by SomeonesAccount 20d ago
That is a very common title format for HN, and has been for a while. It wasn't just since AI has evolved—it has always been a load bearing part of HN 100% Human written slop
7.
by SomeonesAccount 20d ago
Exactly! Composer 2/2.5 were amazing, cheap, and fast. Everyone else was Gaga about GPT 5.5 and such, while we were over here doing the work with less cost and more speed
8.
by SomeonesAccount 20d ago
I don't think it was necessary for two different AI buttons, but whatever
9.
by SomeonesAccount 20d ago
This actually looks sick
10.
by SomeonesAccount 20d ago
That is sick
11.
by SomeonesAccount 21d ago
This is why I never use AI for ideas. Always my own ideas.
12.
by SomeonesAccount 21d ago
Definitely agree. If it is small (eg. Qwen 3.8 28b or gpt-oss-120) then this might be amazing. If it is anywhere near Kimi K3 it would need to have some other differentiating factor than intelligence.