this post was submitted on 14 Jun 2024
574 points (97.0% liked)
Technology
59148 readers
2006 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yep, instant sync is never a guarantee. There still has to be a queue for command messages along with authentication plus authorization of said commands. And just like you said, you must be connected to a network that then can reach their cloud to even receive the command queue.
I run a sync service between multiple Active Directory domains as a result of a merger and the directories haven't been cutover yet. Along with this sync is a password sync that is normally instant. Most of the times (> 90%), less than a second. Sometimes 3 seconds. Other times? 2 minutes. Even when things are within the same LAN, there's the possibility of a backed up queue.
So yeah, this is purely on him trusting the sync implicitly and not verifying. In my case, I trust it too but will on occasion have to assist users because it's not infallible. Karma got him and I have zero sympathy.