Spyke

Replies

Comment on

Study finds that Chat GPT will cheat when given the opportunity and lie to cover it up later.

Reply in thread

They said "it just repeats words that simulate human responses," and I'd say that concisely answers your question.

Antropomorphizing inanimate objects and machines is fine for offering a rough explanation of what is happening, but when you're trying to critically evaluate something, you probably want to offer a more rigid understanding.

In this case, it might be fair to tell a child that the AI is lying to us, and that it's wrong. But if you want a more serious discussion on what GPT is doing, you're going to have to drop the simple explanation. You can't ascribe ethics to what GPT is doing here. Lying is an ethical decision, one that GPT doesn't make.

Comment on

Study finds that Chat GPT will cheat when given the opportunity and lie to cover it up later.

Reply in thread

I think the reason I'm not comfortable with using the term "lying" is because it implies some sort of negative connotation. When you say that someone lies, it comes with an understanding that they made a choice to lie, usually with ill intent. I agree, we don't need to get into a philosophical discussion on choice and free will. But I think saying something like "GPT lies" is a bit irresponsible for the purposes of a discussion

Comment on

I threw away Audible’s app, and now I self-host my audiobooks - Ars Technica

Reply in thread

One of the big draws for me is the scrobbling, across a lot of my self-hosted apps. Comics, shows, books, whatever. I love that I can watch some of a show, or read some of a comic series, then go months without worrying about where I was before picking it back up again. I can pick up where I left off, which is one area where simply having files on a file-system falls short.

Comment on

Docker Help: Port collisions when using container-networking

I am also currently dealing with this same exact issue, I'm wanting to run multiple instances of Lidarr for MP3 / FLAC libraries with Gluetun. I don't have an answer (I haven't put in the time to try and solve it yet), so apologies if I got your hopes up. I'm just here to confirm that others have this issue too!

Edit: Regarding that documentation, it seems like it's not saying that changing the port breaks it, it's just that you have to set both sides of the mapping to be the same. The default is 8080, so instead of 8080:8080, change the mapping to 8081:8081. That's how I'm reading it, anyways.

I should also mention that the closest that I got to fixing this was to boot up my 2nd Lidarr container separately, setting the port in the Lidarr WebUI console to something different (8687, for example), and then attach it to my Gluetun docker compose file. I did a docker compose pull to update my stack, then docker compose up -d for it. You might try this approach, and tinker around with it. I just haven't had time to really play with this "solution"

Edit 2: Played more with the solution I mentioned, and that LifeBandit666 found. We both gave the same solution, and the solution seems to work. Just don't be a dumbass, and remember to do application configuration to your container (unlike me, who, after putting the container into my Gluetun docker compose file, forgot that I didn't do application configuration and just saw a bunch of errors with Lidarr).

Comment on

Whishper: a complete transcription suite.

Would love to deploy this, but unfortunately I'm running server equipment that apparently doesn't support MongoDB 5 (Error message MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!). Tried deploying with both 4.4.18 and 4.4.6 and can't get it to work. If anybody has some recommendations, I'd appreciate hearing them!

Edit: Changed my proxmox environment processor to host, fixed my issue.

Comment on

My Docker containers can no longer communicate with the host's local network

Reply in thread

That's what I've been seeing, but I run enough stuff on Windows that has poor support for Linux that makes it a toss-up. Do you think it's feasible to run Docker on Linux in a Hyper-V container on Windows? I'm really trying to evaluate my options, I've considered Proxmox to separate my Windows and Linux stuff; currently I am running an instance of Ubuntu in Hyper-V for my Linux stuff. Do you think Proxmox is more viable?