I’m having a hard time imagining an accident caused by not wearing a seatbelt… I guess maybe being thrown from the vehicle and hitting a passenger in another car who was wearing a seatbelt?

Cheers to that!

There is legitimately good wine at just about every price point… You definitely should not write off a wine just because of the price.

And conversely, there’s lots of BAD wine that’s expensive.

Try everything and keep track of what you like! Your wine drinking experience will improve, and it’ll probably cost you less to boot!

Gotcha… as long as you understand that any device that receives that traffic can see exactly what’s in it! (no sarcasm intended at all… if you’re informed of the risk and OK with it, then all is well!)

What’s your reason for using HTTP? That seems like a really bad idea this day in age, ESPECIALLY if that’s something you’re going to make available on the internet.

A reverse proxy is basically a landing place that acts as a middle man between the client and the server. Most people set it up so that all traffic on 80 or 443 go to the reverse proxy, and then the reverse proxy gets the correct website based on the host header of the request.

If you are currently serving multiple websites on your server, then that means you are serving each website on a different port.

So, just make sure that the reverse proxy is serving on a port that is not used by your other sites. It will only respond on it’s own port, and it will only serve the site(s) that you have configured in the proxy.

You’ll be fine!

I run a Nextcloud instance on my Unraid server.

I hear you… it’s definitely not about one tasting better than others, but maybe more about the eating experience. I do think there’s a legitimate argument about how different pasta shapes encourage different pasta to sauce ratios, but at the end of the day it’s just the two elements coming together and the taste is what it is. We should all enjoy it the way we want to! I just wanted to explain why some people talk about certain sauces and certain pasta shapes “belonging” together.

It has everything to do with the consistency of the sauce and how well it sticks to the pasta. For example, spaghetti with a meat sauce isn’t a great choice because the meat won’t actually stick to the pasta and you’ll have to scoop up that meat “manually.” Better is pappardelle, which has a huge surface area that causes the meat to stick to the pasta.

Indeed. A wise wizard once said: “It is a curious thing, Harry, but perhaps those who are best suited to power are those who have never sought it.”

It was not a prediction of victory… it was a 71% chance of winning the electoral college. Said another way, they gave her a 29% chance of losing.

https://projects.fivethirtyeight.com/2016-election-forecast/

ahhhh yes, that makes perfect sense… thank you for pointing that out! Especially since I’m not good enough with vi to know how to bulk delete the first character in specific lines, I had to manually arrow and delete.

I successfully migrated postgres 15 to 16. I followed the general idea of the guide you posted, but I found it a little easier to do a slightly different process. Here’s what I did:

1. docker-compose down for the lemmy instance

2. edit the docker-compose.yml file and comment out all of the services except postgres. In addition, add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles

2. edit the docker-compose.yml file and add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles
3. docker-compose up -d postgres (this starts just the postgres service from the docker compose file)
4. docker exec -it [container name] pg_dumpall -U [username] -f /miscfiles/pgdumpall20240628 (I think this will work, but it’s not exactly what I did… rather, I ran docker exec -it [container name] bash, and then ran pgdumpall -U [username] -f /miscfiles/pgdumpall20240628. The end result is a dumpall file saved in the ./volumes/miscfiles directory on the host machine)
5. docker-compose down
6. mv ./volumes/postgres ./volumes/postgresBAK20240628 (move your existing postgres data to a new directory for backup purposes)
7. mkdir ./volumes/postgres (re-create an empty postgres data folder. make sure the owner and permissions match the postgresBAK20240628 directory)
8. edit the docker-compose.yml and update the postgres image tag to the new version
9. docker-compose up -d postgres (you’ll now have a brand new postgres container running with the new version)
10. docker-exec -it [container name] psql -U [username] -f /miscfiles/pgdumpall20240628 (again, I think this will work, but I bashed in and ran the command from within the container. This also allows you to watch the file execute all of the commands… I don’t know if it will do that if you run it from the host.)
11. docker-compose down

12. edit the docker-compose.yml and un-comment all of the other services that you commented out in step 2

13. docker-compose up -d

Hopefully that helps anyone that might need it!

edited to reflect the comment below

I agree… I was simply clarifying that Nate Silver did NOT predict that Hillary would win (nor is he predicting that Trump will win this election), which is a common misunderstanding about probability. For these types of models to be meaningful to the public, there needs to be literacy on what is meant by the percentages given. Really, I’m just reinforcing rodneylives’ point from another angle!

I don’t remember him predicting that she would win. His model (https://projects.fivethirtyeight.com/2016-election-forecast/) gave her a 71% chance of winning. 71% is a long way from 100%, and the result of that election definitely fit within the model.

That said, you are absolutely correct… we need to keep shining a light on the realities of each of these candidates, because in the light of day Biden is a much better choice than Trump.

Thank you, that’s super helpful!

Stop j’terrorizing me!

Depending on what exactly you’re looking for, Photostructure might be a good option. It’s got a great UI for viewing photos, and it’s meant to play well with other Metadata software.

I don’t think I’d call them assholes… more just shortsighted about the realities of selling an album, specifically in how you refer to the album both in speech and in writing.

There’s lots of youtube content on this subject… here’s a decent jumping off point, if you’re interested: https://www.youtube.com/watch?v=7Nw6qyyrTeI