Skip to content

Nostr interface equivalent to Open WebUI

Random Thoughts

  • Do we want the LLM Bot to have a tone of different IP addresses

Tickets

Design Decisions

Research

Logs

2025-01-04T18:14:36-05:00

  • We need to scope out the functionality of our Nostr Client
  • We can also get started with our Graph Representation
  • But that is step 4, Knowledge Graph all the Things
  • We want to do Raindrop Next
  • But we are developing our own custom clients
  • WE NEED USER JOURNEYS
  • Open Web UI does a lot of things
    • Separate Chats
      • Chat Forking / Editing
      • Set and change LLM throughout
    • Importing existing conversations from OpenAI Chat JSON Format
    • Exporting existing conversations from OpeAI Chat JSON Format
    • Summary Tags for the Chats
    • Labeling individual responses
    • Publishing LLM Conversations
  • Open Web UI Server does a lot of things
    • Privacy of Conversations, Admin verses User access
    • RBAC, OPENAI_API Model Access
    • Proxy OPENAI_API Models
    • Proxy OLLAMA models
    • Works with LiteLLM Config
  • But we are not focusing on the correct problem here?
  • We need to design the event types for
    • LLM Conversations
  • Well what have we been putting off?
    • We need to start walking
  • We need to create a list of user journeys

2025-01-04T18:09:55-05:00

  • I am still lost
  • Once I have my LLM Interface I don't have any marketing plan

2025-01-04T17:48:06-05:00

  • So out end goal is to have a replacement for Open Web UI
  • But thats not really what we want
  • So we have the chatbot
  • We need to deploy it properly
  • Then we need to do something else
  • Why are we not interacting with the real world?
  • We have a product we can throw at people
  • DDT008 - NIP for Slash Command Style Stuff and DDT007 - NIP for streaming LLM responses are what we ought to do next
  • The slash command stuff should be simple