billycao

5 ms·

1. 1.▲
   by billycao 1y ago

   There are only 16 direct dependencies, and they all look pretty reasonable to me. Have you worked with any Node.js projects before? I'd actually say this is a relatively sparse list of dependencies for a user-facing tool.
2. 2.▲
   by billycao 2y ago

   Thanks a bunch! For launch/beta, we're paying for the GPU time ourselves. :) Quoting Matt below: "We weren't really sure how to price it, so we're using the beta period for now to figure out what mix of models peopl
3. 3.▲
   by billycao 2y ago

   Appreciate the feedback! We currently use fly.io as our cloud GPU provider, but we're actively investigating other providers due to various limitations (like NVLink support).
4. 4.▲
   by billycao 2y ago

   Borrowing Matt's words from our reddit thread: It means that we can spin up a single model server and use it for multiple people, effectively splitting the cost. Whereas if you try to rent the GPUs yourself on something like Runpod, yo
5. 5.▲
   by billycao 2y ago

   Might have been a transient error as we were deploying some auth provider fixes. Should be good to go now! :) - Billy
6. 6.▲
   by billycao 2y ago

   This is now fixed, and signups should be working again! Had a misconfiguration with our auth provider, even though we were on the paid plan. Thanks for testing! :) - Billy
7. 7.▲
   by billycao 2y ago

   Whoops! We had a hiccup with our auth provider and have just pushed the fix. Sign up should be working again! Thanks for testing! :) - Billy
8. 8.▲
   by billycao 2y ago

   Thanks for the feedback! We're working on fleshing out ToS, privacy policy, and company specifics, but just to answer your first question, I'm Billy Cao, an ex-Google eng, and Matt Baker is ex-Airbnb, ex-Meta. Re: concerns, our i
9. 9.▲
   by billycao 2y ago

   Hey there! We currently use vllm under the hood and vllm doesn't support Codestral (yet). We're working on expanding our model support. Hence (almost) any model. Thanks for testing! :) https://github.com/vllm-proje
10. 10.▲
    by billycao 2y ago

    2nd dev Billy here. Great point. Right now we don't log or store any chat messages for the API (only what models people are choosing to run). We do store messages for the web UI chat history and only share it with inference providers (
11. 11.▲
    by billycao 2y ago

    Hey there! I'm Billy, the other dev working on glhf.chat :) We do have API support! We expose an OpenAI compatible API. You can see details when logged in at https://glhf.chat/users/settings/api Just like our
12. 12.▲
    by billycao 16y ago

    I might subscribe to the oft-repeated mantra to not fix what isn't broken, especially considering that users cannot view other users' calendars, so mediocrity or spam is not of a major concern to you. That said, awesome app. It's certainly
13. 13.▲
    by billycao 16y ago

    It's interesting opening two tabs and only drawing on one, and using the second tab to see what other people are probably seeing. Some strokes have huge lag during spikes, others that I made on my screen are never displayed on the other tab
14. 14.▲
    by billycao 16y ago

    I agree, I highly doubt that the percentage of storage that is non-unique is enough to increase Dropbox's profit margins significantly. I'm certain they use this and several other techniques such that each user reflects a far less impact on
15. 15.▲
    by billycao 16y ago

    I'm wondering, how do you strike a balance between having a long runway and not falling into a sense of well-funded sloppiness? Many suggest that the lack of funds forces a startup to be lean and mean, but I can see how appropriating funds