How exactly does that prevent spam, vs just using other existing established verification methods like email validation? If the only goal is preventing spam, its overkill, and other web sites who also have to contend with spam don’t use it.

It’s trivial to create new accounts and emails to verify those accounts. It is not trivial to get a new phone number since virtual numbers are blocked by the verification process.

There exists other words that start with gi but use the soft g, gin for example. But regardless, the pronunciation of one word is not determined by the pronunciation of other unrelated words.

Neither have sauce in them, they are more akin to a calzone

That’s not what the definition said, realise is just the British spelling. If you re-read the definition in your screenshot, it says both realizes and realises are 3rd person present

I believe the developer is in complete control of the pricing on steam, so it would be the developer being shady

The chance of you rolling [6,6,6,6,6,6,6,6] is the same chance of rolling [1,5,3,2,3,5,3,4] that’s how randomness works

there’s an entire wikipedia article for this that makes it super easy https://en.wikipedia.org/wiki/Pirated_movie_release_types

Is it just me or does that “comparison” make no sense for this thread. It’s mostly comparing vaultwarden to the cloud version of bitwarden, not the self hosted version. It only mentions the self hosted version in passing. It doesn’t do anything to help someone choose between vaultwarden and self hosted bitwarden

I’m not sure if I would even recommend starting with fdm if your goal is resin. So little that you learn about fdm actually transfers to resin, they really are that different. If your end goal is resin because you want to make miniatures, you’re just wasting money getting an fdm printer.

It sounds like what you need to do at this point is find what IP address your lemmy instance and mastodon instance containers are using on your VPS. you can do “docker inspect containername” and look for the IP address in there. it might be something like 172.16.0.1 for lemmy and 172.17.0.1 for mastodon. then you want to set up your reverse proxy to point lmy.my-domain.tld to 172.16.0.1:80 (or whatever port you set lemmy to use) and then mstdn.my-domain.tld to point to 172.17.0.1:80 (again, port might be different, i dont know what the default port is)

-IF- both of the containers are using the same IP, then you will need to make sure that they are using different ports. if they are on the same ip and same port, whichever container loads 2nd will fail to properly load, because when a port is taken on an IP address, it is reserved and nothing else can try to listen on that port.

So a reverse proxy is sort of like a phonebook or directory, it routes outside requests to the appropriate place. So imagine your reverse proxy is a receptionist, someone comes in and says “hey I am looking for plex.mydomain.com” the receptionist would then use the phonebook and say “ok if you are looking for plex.mydomain.com, go to building 192.168.1.10 (the ip), room 9000 (the port)”

Since you are asking about dockerized services, the networking for those can be done in several different ways, but the one thing that really matters is that each service needs to have a unique combination of ip and port, because only 1 service can live at each address. With docker, you could set up multiple services that use the host server’s ip, in which case each container will need to be on different ports, or you could have it so each container has its own ip, in which case the port can be anything.

homeassistant community store has a cloudflared add-on that works great to get it to easily work over cloudflare tunnels

Just fyi how a client handles multiple DNS servers might not always be you expect and just depends on how it was implemented. Some clients can just send a DNS request to all DNS servers at once and take whatever responds first, essentially randomizing which DNS server gets used

I’m not gonna lie, between the dirty camera lens and the color of the filament, I can’t tell wtf is going on in this pic at all

You didn’t keep your 2fa backup codes like they tell you to do?

I’m fairly certain hardware based 2fa has been around since the early 90s maybe even earlier. It’s not the maturity that’s the issue, as I’m fairly certain its significantly older than application based, but that it’s extremely inconvenient for the user to have to buy a physical key and keep it safe

Think about what happens to water if it’s heated above 100C… it turns into steam! The more water there is in the plastic the more steam there will be, causing the various issues like bubbling. The release of steam also means some of the heat is not being absorbed by the filament, leading to temperature issues as it exits the nozzle

I had a similar issue where it was thin in regular intervals similar to what it looks like in your pics, the issue I had was the extruder gear was clogged up on one side so it wasn’t gripping the filament and slipping until it spun around to the unclogged side and it would extrude normally again.

Look into NUT, Network UPS Tools. It runs in a server/client type of set up. You’d install the server onto the device that has the UPS data connected to it. It then monitors the UPS status and can tell all the clients to shutdown when the UPS is running low.