







Are you sure they’re hitting the hostname and not just the IP directly?


This is a good read and makes a lot of great points. I think everyone in tech needs to understand the arguments here. The biggest thing for me is that LLMs are incredibly useful tools, but not in the way they are advertised. They are great for learning how existing code works, but shit at writing anything novel or innovative. From the article:
The past is a prison when you’re inventing the future.
In my opinion, if you’re using LLMs to do anything but help you learn from the past, you’re doing it wrong. LLMs cannot move you forward, and I think that may be the point.


What happens when you eat them more? As a scientist, that is.


That’s what Emby thought.


I can’t read the word without thinking this.


Lol, “study”.
I see what you did there.
I have an extra chromosome. Do you want it?


Assuming your local service is accessible from the nginx server, you can proxy the request to it:
server {
listen 80;
location / {
proxy_pass http://10.100.100.2:3000/;
}
}
…where 10.100.100.2 is your local IP on the VPN and 3000 is the local port your service is listening on, and 80 is the public port your nginx server listens on. Everything that hits your nginx server at http://yourserver.com/ will proxy back to your local service at http://10.100.100.2:3000/. Depending on what you’re hosting, you may need to add some things to the config.


I’m assuming that you are trying to proxy an http web server. If not, you’re going to have a hard time with nginx. Can you post your nginx config? Are you getting any response from nginx at all?


I too have never heard of Oregon City. I can only assume it’s in Oregon. The only thing I remember about the Oregon Trail is that I died from dysentery every time I followed the trail.


Who do you call when it’s the police doing the harassing?
Here’s a good place to start:
gpg --gen-key
Then follow the prompts.


This is patently false. Secure boot and hibernation are not mutually exclusive.


Zee shell ist die beste.


it will make pretty much everything faster…
This is just not true. Environment variables are only going to be used by programs that are looking for them specifically. Putting them in your .bashrc as you have done is going to make them only available in contexts where that file is sourced, e.g. interactive command line environments.
…at the expense of breaking some commands here and there…
You probably experience this because you used a single to overwrite your .bashrc entirely with that single command. Anything that was in that file before is now gone. Using > will append rather than overwrite.
That variable in particular is probably one used by mesa, a 3D graphics library. It’s only going to be used by programs that use the mesa library. I don’t know what it does exactly, but there will be documentation somewhere.


It has space for a standard PSU inside, but I’m pretty happy with this one:
https://www.amazon.com/dp/B0785GRMPG
I’ve been running it for about 4 years now.
If you have a fat GPU, you might have trouble with additional PCIe cards. You’ll definitely need more cooling as it only comes with one tiny fan.


It’s not DNS.
There’s no way it’s DNS.
It was DNS.
-SSBroski
I think you’re conflating shells and terminals.