> It doesn't know if 1 person made all those requests, or N.
FWIW this is highly unlikely to be true.
It's true that the upstream provider won't know it's _you_ per se, but most LLM providers strongly encourage proxies like OpenRouter to distinguish between downstream clients for security and performance reasons.
Fair point. Would be good to hear from OpenRouter folks on how they handle the safety identifier.
For prompt caching, they already say they permit it, and do not consider it "logging" (i.e. if you have zero retention turned on, it will still go to providers who do prompt caching).
OpenRouter tells you if they submit with your user ID or anonymously if you hover over one of the icons on the provider, eg OpenAI has "OpenRouter submits API requests to this provider with an anonymous user ID.", Azure OpenAI on the other hand has "OpenRouter submits API requests to this provider anonymously.".
But does "anonymous user ID" mean that they make a user ID for you, and it's sticky? If I make a request today and another tomorrow, the same anonymous user ID is sent each time? Or do they keep changing it?
I believe they are static user ids that only OpenRouter knows is you (the anonymous part. Static id is required for any cached pricing. If the user id changes each request, it would be a massive security hole to reuse that cache between requests with different user ids.
Without caching, it would make sense to be per-request (more like a transaction-id, and would make sense to be) as this could then be tied internally back to a user while maintaining external anonymity, but unfortunately I don’t believe that is the case.
I took the trouble of logging in to HN to call bullshit on this whole thread. The reason these teenagers aren’t building standalone apps is generally because they know that web apps are the future. Moreover, there are dozens of new travel planning startups every year (YC regularly funds them!) and they seem to discover the same thing that Microsoft did—the real reason they stopped updating this magical app—which is that everybody wants better travel apps but nobody wants to pay for it.
I’m sure someone will crack the code someday and I’m glad they will keep trying, but I refuse to accept the premise that $100 Apple developer accounts are their primary impediment.
$100 is $100, you seem to comment from a position of privilege. When I learned programming, in my early 20s, that was close to my monthly salary. Granted I've been a paid programmer for more than 15 years now and I make more than that, but, even so, seeing as app development is not what brings me money it looks like a waste to me to throw $100 at something each year so that I'd have the privilege of running my code on a piece of hardware I already own.
And let's say that maybe I'm a cheap bastard, but the reality remains that $100 is still a lot of money for a lot of young people around the world who have just gotten into programming.
No way my parents would have forked over $100 to me on some computer thing they didn't understand. Being able to spend your parents money on the internet as a kid is rare.
Maybe web apps are going to be used for commercial things but nothing beats the power of being able to write your own tools, and its just so easy to do that locally as its always been. A little bash script or some python goes far.
For other public BigQuery datasets I’d certainly consider just adding them to the demo for free—which specific Bitcoin/finance datasets did you have in mind?
For private datasets, we’re looking at adding that functionality to the core Tabby service (that’s the SaaS this relates to). Please email for info!
Are you looking to set it up for another public dataset or your own private one? Either way, shoot me an email (on the demo page and also in my HN profile) and I’ll see what I can do.
Thanks for noting this! The functionality is definitely not perfect, and the opaque nature of the underlying model does not give much opportunity for tweaking. I suspect slightly altering your input might help drive better output.
FWIW this is highly unlikely to be true.
It's true that the upstream provider won't know it's _you_ per se, but most LLM providers strongly encourage proxies like OpenRouter to distinguish between downstream clients for security and performance reasons.
For example:
- https://developers.openai.com/api/docs/guides/safety-best-pr...
- https://developers.openai.com/api/docs/guides/prompt-caching...
reply