Maybe I misspoke; I meant “the commenters in this thread” because I was definitely reacting to some comments i saw here
I agree, and I think you approached this well.
It’s funny that most of the .world posts are like
It’s cute that you think much paperwork is needed at all.
The only time they do paperwork is when they need to present evidence publicly, like in a court. Lead generation is essentially free, and then they just construct a parallel charge.
NUT works with many UPS models and provides monitoring and control
involves a lot of sweat, requires you to clean up any mess you make, and communicate with any partners about their preferred techniques instead of rawdogging it and waiting for issues. The pushing and pulling will come naturally but you need to know how and when to release, and be clear about how you wish to commit. People might judge you for using the word “master” but it should be alright in private.
Don’t talk about my mom that way
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!
Use ropes to pull your legs apart while you lay on your back on a table.
[BRAZZERS]
Don’t worry I didn’t even see it until now
That is patently false. Encrypted email and patient portals are absolutely allowed under regulation.
What you have here is a practice that has probably been in operation since the 80s or before, and they refuse to change their ways.
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)
FPGAs would be considered “hardware emulation” but a lot of people don’t like that term, and think emulation should be a term limited to software.
Like, there aren’t real N64 chips in there. The hardware IS emulating an N64 - it’s just not doing so in a way that’s comparable with software emulation at all.
Passkeys are basically client certs for website logins.
Server stores a public key, encrypts a challenge on login attempt. Client browser uses private key to decrypt challenge (and sign it maybe?) and respond to web server to authenticate.
Hackers can’t get a shared secret (like a password or password hash) by hacking the website’s database becaus the public key is all they store; useless without the private key.
Not foolproof, but much harder to exploit than passwords - which many people re-use across multiple sites.
Can’t keep archives of Saturday morning cartoons we all grew up with and loved; will sue you for keeping copies of them.
Definitely ok to being three mile island back online for AI though, that’s the ticket to a better humanity!
For real why has everyone with any kind of money gone psycho? Have the bad guys started winning even harder?
I think the meme is more about perspectives and listening to the way someone thinks about operating IT is very different from the way someone things about architecting IT
It’s next to X and C on the keyboard, so you don’t have to move your fingers much to cut/copy then paste quickly.
Once again, the problem can be traced back to DNS 😜