orders delivery

falls asleep

complains about “Bullshit fucking app”

(⁠╯⁠°⁠□⁠°⁠）⁠╯⁠︵⁠ ⁠┻⁠━⁠┻

Give an alternative a go, see if you have better luck. There’s adguard home, blocky, and Technitium DNS for you to consider.

Alternatively, the window trick should work.

I think that happened 8 years ago or so

I honestly do not see what you’re upset about, both search engines look like they did well here.

Let me expand a little bit.

Ultimately the models come down to predicting the next token in a sequence. Tokens for a language model can be words, characters, or more frequently, character combinations. For example, the word “Lemmy” would be “lem” + “my”.

So let’s give our model the prompt “my favorite website is”

It will then predict the most likely token and add it into the input to build together a cohesive answer. This is where the T in GPT comes in, it will output a vector of probabilities.

“My favorite website is”

"My favorite website is "

“My favorite website is lem”

“My favorite website is lemmy”

“My favorite website is lemmy.”

“My favorite website is lemmy.org”

Woah what happened there? That’s not (currently) a real website. Finding out exactly why the last token was org, which resulted in hallucinating a fictitious website is basically impossible. The model might not have been trained long enough, the model might have been trained too long, there might be insufficient data in the particular token space, there might be polluted training data, etc. These models are massive and so determine why it’s incorrect in this case is tough.

But fundamentally, it made up the first half too, we just like the output. Tomorrow some one might register lemmy.org, and now it’s not a hallucination anymore.

Very difficult, it’s one of those “it’s a feature not a bug” things.

By design, our current LLMs hallucinate everything. The secret sauce these big companies add is getting them to hallucinate correct information.

When the models get it right, it’s intelligence, when they get it wrong, it’s a hallucination.

In order to fix the problem, someone needs to discover an entirely new architecture, which is entirely conceivable, but the timing is unpredictable, as it requires a fundamentally different approach.

🖕

Do you have ssh access running on local network? If so, all you have to do is forward the port. I’d recommend exposing a non-standard port, also using keys rather than password.

If you don’t have your sshd running yet, it sounds like you need to read some guides to get a foundation, then come back with specific questions.

I have done that so many times to fix a problem I didn’t understand so I completely get that.

Got it working?

Got it working?

The best way to troubleshoot your setup is to test each bit by bit individually until you figure out where it’s gone wrong.

Try your qbit container without glutun. Can you download and seed a Linux iso from the same directory your current seeds are? If not, you’re probably looking at a permissions issue.

Next test your glutun container. Can you ping the tracker from the container? If not, your VPN isn’t set up correctly.

Lastly try qbit via glutun, if it doesn’t work it’s a port forwarding issue.

Good luck!

Brilliant