280 karma · joined September 28, 2019
One regret I have is not taking growing audience/following seriously.
> Ironically
of all the places :)
Well this is absolutely possible with ollama app running on your device and self-host package running on localhost.
Permission to deploy and use compiled code only, no modification, redistribution, sharing or reselling.
Open sourcing documentation is an interesting idea.
> Something along the line Set the environment variable OLLAMA_ORIGINS
I'll test it out and update the docs.
This is the absolutely ideal state of the product, i agree.
I'm planning to release more videos, stay tuned.
I would love if we had some kind of 'open-build' methodology so those projects not willing to open the source but are willing to perform any kind of necessary audit against the build, just a thought.
> Will the Self-host package include source (i.e. source available) or is it just the transpiler output?
No sources, just a folder with compiled assets that you can run on a static server. This is already available.
> Also, is there (or plan to be) support for postgres or other database for persistence?
Yes there are plans for local pg
> Are there keyboard shortcuts for all the operations shown?
For now yes, what would you like to be added?
Yes it's a wrapper with opted-out sentry and vercel analitycs, just like self-host package.
I have no plans to open source it at the moment, but it would be great to come up with something like 'open build' for cases like that.
Like I mentioned earlier for me the app is canvas-based first, node-based second. So connections are a tool, a visual tool to craft or manage prompt to then feed it to LLM. Canvas is a visual tool to organize and keep large amounts of chats.
I try use LLM not for the sake of chatting, but to get results and those tools seem to help me with that.
Hope that makes sense.
> What does "premium support" mean?
Premium option includes prioritized support and access to new features that might be unavailable for other types of licenses.
I will update the website for more clarity.
> Should I buy licenses for 14 (3x extended) instances
Yes that should work. Each license comes with 5 seat/activations. Each seat has its own copy of the data.
> In your case, do you hold N contexts (N being the number of leaves in the tree)?
It depends, contexts are just a form of grouping
> Are the chats disconnected from each other? > How do you propose to transition from an endless/unstructured canvas to some sort of a finished, organized deliverable?
RAG with in-app commands, i'm working on a local RAG solution, it's early but promising. Basically chat with all your data and applying a wide range of command on it.
This is something very similar to what i'm planning to add next, so stick around.
Me personally i find value in taking my time to organize and drag around, probably because i'm a visual thinker