projectmoon

OpenWebUI connected tabbyUI's OpenAI endpoint. I will try reducing temperature and seeing if that makes it more accurate.

Context was set to anywhere between 8k and 16k. It was responding in English properly, and then about halfway to 3/4s of the way through a response, it would start outputting tokens in either a foreign language (Russian/Chinese in the case of Qwen 2.5) or things that don't make sense (random code snippets, improperly formatted text). Sometimes the text was repeating as well. But I thought that might have been a template problem, because it seemed to be answering the question twice.

Otherwise, all settings are the defaults.

I tried it with both Qwen 14b and Llama 3.1. Both were exl2 quants produced by bartowski.

Perplexica works. It can understand ollama and custom OpenAI providers.

Super useful guide. However after playing around with TabbyAPI, the responses from models quickly become jibberish, usually halfway through or towards the end. I'm using exl2 models off of HuggingFace, with Q4, Q6, and FP16 cache. Any tips? Also, how do I control context length on a per-model basis? max_seq_len in config.json?

Seems to be the only necessary thing in my case! Thanks.

Yeah I definitely have the default GTK chooser. Guess I have some config playing to do later.

Can you explain a bit more about this and how to configure it? When I use FF on gnome, the save dialogue just looks like other dialogues?

That is exactly the plan.

You can right click the URL bar for sites that support the OpenSearch XML standard. Which I guess is what they wanted to replace it with. But I don't really know why they removed the button to a about: config setting. Could at least be a checkbox or something to enable.

Returns the add custom search engine button. Which for some reason, has been hidden by default.

That would probably be a task for regular machine learning. Plus proper encryption shouldn't have a discernible pattern in the encrypted bytes. Just blobs of garbage.