Pinkert

3 ms·

1. 1.▲
   by Pinkert 7mo ago

   That's actually a great question. and the answer is yes and no; While it does disable the caching mechanism for the conversation history (and not for the system prompt, who remains constant), there is a difference between a chatbot wit
2. 2.▲
   by Pinkert 7mo ago

   Thanks! I'd love to hear how you implemented it, and if you can suggest any improvements for my solution. feel free to submit PRs as well!
3. 3.▲
   by Pinkert 7mo ago

   One architectural tradeoff we are actively working on right now is the latency of the "Select" step for shorter conversations. Currently, the open-source version of Librarian uses a general-purpose model to read the summary index
4. 4.▲
   Show HN: Librarian – Cut token costs by up to 85% for LangGraph and OpenClaw(uselibrarian.dev)

   8 points by Pinkert 7mo ago|7 comments
5. 5.▲
   by Pinkert 7mo ago

   Using a v3 onion address as both the cryptographic identity and the NAT traversal layer is such a clean architectural choice. No STUN/TURN servers, no hole punching, you just boot the script and Tor handles routing. For those who use T