I’ve actually had pretty good success with ChatGPT when I go in expecting it to hallucinate a significant chunk of what it spits back at me. I like to think of it as a way to help process my own ideas. If I ask questions with at least a base understanding of the topic, I can then take whatever garbage it gives me and go off and find real solutions. The key is to not trust it whole cloth to give you the right answer, but to give you some nuggets that set you on the right path.

I think I’ve basically turned ChatGPT into my rubber duck.

So...it's working now? I haven't touched anything yet, but I just checked my instance again and it works perfectly fine on desktop now. It always worked through Voyager, so I was able to let people know there was an issue. If it comes back I'll try some of these suggestions to find a more permanent fix.

Meaning I just wait a bit and retry later?

Upgraded to 0.18.5, which now gives me this error:

lemmy-lemmy-ui-1  | API error: FetchError: request to http://lemmy:8536/api/v3/site?auth=AUTH_KEY failed, reason: connect ECONNREFUSED IP_ADDRESS:8536

I created a gist with my compose file: https://gist.github.com/osiriswrecks/26a875576d3bbcf11923d7715ac15e6e. It should be stripped of all private info. I tried changing the version from 0.17.3 to 0.18.0 and the server returns a gateway error after restarting.

About freaking time. I have it as an option but I hate using it. I’ve been looking for alternatives for a while now because I just expect to lose a couple hundred bucks in “processing” for every project I work on.

They're about 8 years behind the curve though. Just like a client who recently told me they were thinking of getting into NFTs to make some money.

I thought the same maybe, but I assumed an actual camera because of context (using the camera's manual focus and printing out the photo afterwards). @WeirdGoesPro@lemmy.world ? Did I misunderstand?

Disclaimer: I'm not an optician. I do, however, work in advertising and happen to have a number of clients in the lens manufacturing industry. Take what I'm about to say with a grain of salt.

Short answer is, not really.

Diagnosing vision issues is much more complicated than simply "is it in focus". The shape of the cornea, how your eye physically reacts to light, distance from an object, and disease all have an impact on how you perceive the world around you. That's why you have things like aberrations, glares, near sightedness, far sightedness, and a plurality of other vision problems. When someone is fitted for glasses or contact lenses, a number of parameters (read, dozens) are required get what is considered a proper "fit".

There are some similarities between how a camera lens works and our eyes, but you also have to consider that you're not just looking through the lens itself, you're focusing on a screen that's attached to the lens. So, if you can't focus your eye sight at the distance the screen is at, it doesn't matter what the camera is seeing, because it'll look like garbage to you either way.

I used to read a lot more, and I do remember this happening, but it happens a lot for me now with podcasts. I'm a big podcast junkie and I will often find myself going down a rabbit hole of thought and realizing I have no idea what they're talking about anymore.

So looking at this again now, am I taking that whole block and adding it to the container's nginx.conf? If so, does that mean I have to change what port it's currently listening to (because there's already a rule in the file for port 80)?

There's a comment in that server rule that says "this is the port inside docker" and a comment immediately after that says "this is facing the public web", which confuses me.

The one meant for the Docker container or the one on the host?