this is great, I've always wanted something like this, do you think you can add other model metadata, like api name (`gemini-2.5-pro`), context length, modalities, etc
Readit Newshagope commented on Show HN: Price Per Token – LLM API Pricing Data pricepertoken.com/... · Posted by u/alexellman
Deleted Comment
Anthropic and all the AI vendors need to implement "Login with ___" allowing users to trust sites to use their own AI resources, similar to how Dropbox allows 3rd party access to the User's storage. Most users don't want to bother with generating and loading API keys, nor can they manage it safely.
hagope commented on Exo: Run your own AI cluster at home with everyday devices github.com/exo-explore/ex... · Posted by u/simonpure
I used to be excited about running models locally (LLM, stable diffusion etc) on my Mac, PC, etc. But now I have resigned to the fact that most useful AI compute will mostly be in the cloud. Sure, I can run some slow Llama3 models on my home network, but why bother when it is so cheap or free to run it on a cloud service? I know Apple is pushing local AI models; however, I have serious reservations about the impact on battery performance.
hagope commented on Introducing ChatGPT and Whisper APIs openai.com/blog/introduci... · Posted by u/minimaxir
hagope commented on Show HN: Phind.com – Generative AI search engine for developers phind.com... · Posted by u/rushingcreek
This is really cool! Are you using OpenAI API under the hood or have you trained your own model?
hagope commented on Postgres 15 improves UNIQUE and NULL blog.rustprooflabs.com/20... · Posted by u/Twisell
You do both.
The foreign key only gaurantees that the other entity exists.
The unique constraint ensures that only one pair of entities has this relationship, preventing a one-to-many binding.
The distinctness of NULL allows you to have multiple entities with the same NULL value without violating the above UNIQUE constraint.
The "NULL is empty" vs "NULL is unknown" is a series of trade-offs of labor-saving. Imho, the wrong trade-offs were made, but once the choice is made it makes sense to continue and be consistent with it. I'd rather be consistently wrong than inconsistently right.
If the entity doesn't exist, wouldn't it violate the FK and therefore no need for the nullable constraint?
hagope commented on Postgres 15 improves UNIQUE and NULL blog.rustprooflabs.com/20... · Posted by u/Twisell
When an entry can belong to 0 or 1 related object only. Not that I'd put a constraint in such scenario, but I imagine a User can optionally have a Subscription, so subscription_id is either nil or present, and said subscription cannot be associated to any other User.
in that scenario why not use foreign key? any advantage to using constraint?
hagope commented on Postgres 15 improves UNIQUE and NULL blog.rustprooflabs.com/20... · Posted by u/Twisell
This is cool, but wouldn't creating a constraint using a nullable column be considered a poor design decision? In which scenarios would this be a good idea?
hagope commented on Show HN: OnlyRecipe.app – Remove clutter from recipe sites showcase.onlyrecipe.app/... · Posted by u/AwkwardPanda
Would be cool if you could enter Yotube URL and you parse out the recipe from the audio/video.