In short, yes. Wet, wildlife markets in China were the source of this outbreak.
In short, yes. Wet, wildlife markets in China were the source of this outbreak.
I recall some calculations that showed a decrease in latency over long distances because light travels slightly faster in a vacuum, there are fewer intermediate nodes over that distance, and a more direct path can be used than in our existing wired networks.
The biggest issue with current satellite connections is that the satellites are in geostationary orbits which imposes a minimum theoretical latency of something like half a second. It's physically impossible to send signals any faster[2].
1: https://arstechnica.com/information-technology/2020/03/musk-...
2: https://en.wikipedia.org/wiki/Satellite_Internet_access#Sign...
Whether or not that’s due to differences in education or purely signaling behavior is something I have yet to fully make up my mind about.
On one side you have people that managed to claw their way through the boot camp but didn't actually pick up any of the skills; they memorized enough to get through instead of actually learning stuff. On the other side, you have people that did learn but aren't confident in their skills and so flub the interview when their confidence gives out.
I've watched the latter happen on more than one occasion and I really wish I knew how to handle it as an interviewer.
Am I just missing something? Why wouldn't these businesses want people to help them out in this? Is it just the lack of notification and consent gathering?
The browser extension worked the best of any we trialed (this includes Dashlane, LP, Bitwarden, and 1Password).
Our users found the 2FA to be self explanatory and liked the option to use Yubikeys (when the platform supports it) and defaulting back to TOTP when not available.
The UI is simple and clear and as you pointed out the records are flexible.
Sharing is easy and the most robust of any solution we tested. (see what happens when a user you didn't intend to share with gets ahold of the share link in LastPass).
Data replication between uses and devices was near instantaneous with no user action to ensure the vault was in sync.
Additionally, we subscribe to BreachWatch and have gotten immense value in knowing that our users are not using breached credentials.
One final note from an enterprise perspective, the admin console for Keeper was clearly the easiest to use with the most features of any of the solutions we trialed.
WRT sharing, I can agree with that. LastPass's sharing isn't as robust, though I don't recall ever using share links. I don't like that Keeper doesn't tell you what record you just received, though. I already have many dozens of records and it can be difficult for me to find new ones that have been shared with me.
I've never had an issue with data replication on LastPass and haven't needed it with Keeper (I only have it on one machine, anyways).
I can't speak to the Admin UI's of either, though. I've never used them in an org setting. The closest I've come to that is the family account I manage via LastPass, which I imagine isn't the same as what you'd get with a full enterprise account.
All that aside, I'm glad that it's been working well for you and your org. I'm sure Keeper is fine (particularly on Windows or Mac) and that my experience is atypical, but it's still my experience with the thing. Unfortunately, I hate it.
Could we have both? e.g. CoC moderators elected by contributors from the ranks of contributors?
Granted, that's still open to abuse if the quorum requirements are small enough (how small would depend on the quantity of abusers), but I feel it's more in spirit than centralizing the power into a sub-group.
I will further grant that it's likely that, in any group, only a subset will care enough about these things to police them, so the point may be moot.
https://docs.microsoft.com/en-us/azure/active-directory/saas...
Off the top of my head:
1) The browser plugin is horribly written and has cause me numerous problems (Linux latop, YMMV), mostly related to performance and memory usage (both very bad).
2) Horrible 2FA management. You can configure Keeper to not ask you for your 2FA on a device for an hour, 30 days, or never again (iirc) and sometimes it'll just stop asking (like it did for me just now) or switch to a different 2FA for no obvious reason (I have both a security key and OTP).
3) Personal Opinion: I hate the layout of the "vault" and the browser extension's windows. I find all of them to be clunky and hard to use.
On the plus side, I do like how the actual records work. Most fields are optional and they have a decent custom field system. So, you can store pretty much anything in a reasonable way (from database credentials to PII, if you're into that).
Personally, I don't feel that there are many population centers in the US that are prepared to do the kind of testing that seems like would be needed to properly identify the sick.