We’ve been waiting for so long that games don’t even remember Half-Life. It’s all “silksong copium” memes now lol
4am
joined 1 year ago
You cannot specify ports in a DNS A or AAAA record. www.example.com cannot resolve to 1.2.3.4:443 and app.domain.com cannot resolve to 1.2.3.4:5555
If the application (be it a game or whatnot) supports it, SRV records can identify a port for a hostname. So, you could have minecraft1.domain.com and an SRV record to specify port 25565, and minecraft2.domain.com SRV 25566.
This means you can have multiple Minecraft servers with the same IP address, but you won’t need to give people the port numbers to remember; the hostname allows the game to look up the port via the SRV record.
This is great for selfhosters because we generally only get one IP (until they rollout IPv6; probably half the reason they don’t)
Almost like an AI wrote it
Yeah I’ve fallen into this trap before as well. When I shop for a desktop, I tend to go as high-end as I can afford and then sit on the same machine for 7-10 years until it becomes unusable/support begins to wain. That desktop sits under my desk and doesn’t move that whole time, it is in a very controlled environment.
You cannot shop that way for a laptop that will be moved and handled and charged and stowed and scratched and bumped and bent and twisted. Even if you take excellent care of it.
You are correct, but the way people reacted is certainly conditioning from the rug-pulling enshittification going on daily in the tech world. (What are we all using instead of redis, again?)
This is a much more level take than your first comment.
They didn’t try anything. Stop inventing. Go read an actual article on the subject instead of feeding the scarebait frenzy.
“I only read the headline and the comments from the threads a week ago, I am truly disappointed in Bitwarden’s stance against FOSS as I’ve misunderstood it.”
Valve has a good track record, and you’ve never owned a game in your life. They’ve always been a license, with few exceptions. Even physical media.
view more: next ›
You can run into this issue with any two sync programs that operate on virtual files, as another commenter said. This isn’t specifically a OneDrive or NextCloud problem. You can safely run both at the same time on the same machine, as long as they are syncing entirely separate directories.
That being said, this is obscure enough that I feel like there should be some kind of check in these clients to make sure they’re not about to interfere with each other - users aren’t gonna know to check for this, especially since these clients are hiding what they’re actually doing behind the scenes!