If RUssia wouldn't have done it someone else would. If you lave a bag of money open outside your door, someone will eventually take it and its your fault for leaving it out for someone to easily steal it
I'm looking right now at something like what I describe that I built 10 years ago, except the sensor is much less accurate (±1.0℃), the ESP8266 module I used didn't have USB so it is powered by an MB102 breadboard power supply, and I used NodeMCU.
On the breadboard there is the ESP8266 module [1], the sensor breakout (a BMP280, which uses I2C just like the newer much more accurate sensors), the MB102, and 6 wires. 2 wires are connecting the ESP2866 module the power and ground, 2 wires connecting the BMP280 to power and ground, and 2 wires connecting the BMP280 to the ESP8266.
If I had used an LLM it probably would have not left out the important thing that I completely overlooked: the SDA and SCL lines for I2C need pull-up resistors. Many sensor breakout modules include them, such as the BMP280 modules in my 10 year old project, so I forgot about them.
1. Yes, but if i can't rely on openrouter to route to providers to give me the best price and the best uptime across a number of providers, and it instead gives me inconsistent results, then I will not use them.
2. As long as the apis use the openai spec, it should be fine? And what makes you say the providers are using different weights? The blogpost says the exact opposite?
3. Great example, if amazon does not lead me to good products, I will stop using it, and this is why I dislike amazon. There are so many crap products, and the search seems to try to push crap products instead of what i'm actually looking for at a good price.
You take a bunch of providers with not great uptime, put them in a pool and now you get great uptime - but it doesn't work if it's at the cost of shitty performance or failing toolcalls.
> 1. Yes, but if i can't rely on openrouter to route to providers to give me the best price and the best uptime across a number of providers, and it instead gives me inconsistent results, then I will not use them.
OpenRouter does reliably route to your specified model and provider, otherwise it'd pretty much be fully broken. Parent is complaining about the auto-provider chosing, not that all providers are unreliable.
> 2. As long as the apis use the openai spec, it should be fine? And what makes you say the providers are using different weights? The blogpost says the exact opposite?
In theory, yes. In practice, no, there are differences. Ollama, llama.cpp, vLLM and SGLang all say "ChatCompletionRequest" compatible, but the devil is in the details, they don't have 100% the same request/response schema across all compatible models.
> 3. Great example, if amazon does not lead me to good products, I will stop using it, and this is why I dislike amazon. There are so many crap products, and the search seems to try to push crap products instead of what i'm actually looking for at a good price.
Yup, makes sense! If you're unable to find models when you use OpenRouter, it makes zero sense to continue to use OpenRouter.
> You take a bunch of providers with not great uptime, put them in a pool and now you get great uptime
Huh? That's not how it works or does it make sense, nor have I've seen anyone use OpenRouter like that.
> Parent is complaining about the auto-provider chosing, not that all providers are unreliable.
Parent is claiming that the choosing is unreliable. If I rely on a provider to bring me tuna to some spec, but they get it from many different fishermen, it doesn't mean that the tuna doesn't have meet the spec. The complaint is that they're given a bunch of knobs that simply don't work with providers that they could be switched to. That's like saying that I want my tunas to be 20lbs. minimum, and I get switched to a provider that doesn't weigh their tuna at all.
The choosing is all OpenRouter provides. If it doesn't do that, then what is it good for? If I have to permanently pin the one provider who doesn't ignore what I've asked, why shouldn't I just deal with them directly?
edit: it's really supposed to reduce providers to a commodity market. If you're selling e.g. produce to a commodity market, you can't just ship whatever the hell you want. You ship something indistinguishable from others, or more likely the market itself allows you to grade what you're shipping so it's put into a bin with virtually identical stuff. The customer just buys Grade B Wheat.
Specifically for a terminal, i'd really prefer it to be open source.
Primarily for security reasons, but also just so it's easier to avoid slop, in times like this with heavy LLM usage.
Yes, there is a lot to unpack - and im sure very smart people has worked on these changes, so spotting what is and what is not peculiar ways to get around EU regulations is not easy.
reply