Weves

5 ms·

1. 61.▲
   by Weves 3y ago

   You can plugin any model of your choice! Self-hosted, open source models are a great choice if you're very concerned about keeping your data safe and secure
2. 62.▲
   by Weves 3y ago

   You can also use any other LLM provider / any open source model of your choice!
3. 63.▲
   Combine GPTs with private knowledge for actually useful AIs(medium.com)

   103 points by Weves 3y ago|34 comments
4. 64.▲
   Show HN: DanswerBot – Open-source Slack bot to automate repetitive questions(docs.danswer.dev)

   6 points by Weves 3y ago|3 comments
5. 65.▲
   How to host a GPU backed Llama2-13B API for free(medium.com)

   4 points by Weves 3y ago|0 comments
6. 66.▲
   by Weves 3y ago

   See https://news.ycombinator.com/item?id=36671406 for more details on this. TL;DR didn't like llama-index's connectors, and we're planning to move to LangChain soon.
7. 67.▲
   by Weves 3y ago

   We'd love for you to contribute. Let us know in Discord / Slack (if you haven't already), and we'd be happy to find something interesting for you to hack on.
8. 68.▲
   by Weves 3y ago

   Right now, Danswer does send data to OpenAI. Once we support locally hosted, open source generative models that will change. If you go with that option, your data won't be sent anywhere.
9. 69.▲
   by Weves 3y ago

   That's a good suggestion! Will look into it, should be fairly easy to support
10. 70.▲
    by Weves 3y ago

    Agree with the point about intelligent chunking being very important! Each individual app connector can choose how it wants to split each `document` into `section`s (important point: this is customized at an app-level). The default chunker
11. 71.▲
    by Weves 3y ago

    Great question! Right now, our access control is very basic. When admins setup connectors to other apps, all documents indexed are accessible by all (meant to be public documents only). Individual users can index private documents by provid
12. 72.▲
    by Weves 3y ago

    Amazing foundational tools like Qdrant make building in this space so much easier <3
13. 73.▲
    by Weves 3y ago

    Native support for the Microsoft suite of tools is something we plan to add fairly soon! We're a small team, and currently swamped with connector/feature requests so no promises on the timeline. Ticketing platforms like ServiceNow
14. 74.▲
    by Weves 3y ago

    Adding local/open source model support is at the top of our TODO list! When we started building, open source models were quite a bit more behind of GPT-4 then they are now. At that time the performance gap was at a point where locally
15. 75.▲
    by Weves 3y ago

    LlamaIndex is a very generic framework to ingest data (from anywhere, with no specific context in mind). Developers then build on top of this framework in order to simplify the process of creating LLM-powered on apps. Developers need to h
16. 76.▲
    by Weves 3y ago

    We're actually planning on migrating to LangChain very soon (primarily to allow for memory / tool usage + automatic integrations with llamacpp / other open source model serving frameworks). We didn't start with it initia
17. 77.▲
    by Weves 3y ago

    We are actively building a Notion connector! Will be out very soon :)
18. 78.▲
    by Weves 3y ago

    Thanks! For now, we're just focused on making sure this solves a problem effectively for people. In the long term, if we're able to build up trust, we'll probably offer a managed version.
19. 79.▲
    by Weves 3y ago

    Yea, that's good feedback - we've gotten requests for open source model support from a lot from people we've talked about. It's one of our highest priorities, and should be available soon!
20. 80.▲
    Show HN: Danswer – Open-source question answering across all your docs(github.com)

    189 points by Weves 3y ago|66 comments