Last mile delivery companies don't handle the volume of non-package traffic that the USPS does. At that scale, tailoring can really pay off in productivity.
Are you saying that the USPS delivering a handful of advertisements in addition to the odd package has greater demands than UPS/Fedex/Amazon delivering the bulk of the large packages in our society?
I don't think this is the same article of which you're thinking. This is a tool to rotate DKIM keys and publish the old ones (in a sense, a scheme that replaces revocation).
A few years ago, there were a number of devices that came on the market that essentially blew ozone through the airflow pathways in PAP devices, and this was supposed to be a substitute for disassembly and scrubbing (which is a lot less convenient). While nobody has said these devices and the ozone methods actually damaged the foam, replacement PAP units all are not warranted if ozone cleaning devices are used. I don't know if this is the only "cleaning material" to which the article refers.
Turns out Montessori education runs in 3-year cycles (ages 2-3-4, and 5-6-7, for example). Not all schools make that clear, and, if you put a kid in in the middle of a cycle, there is orientation material they will miss. Without that grounding, Montessori can turn out to be a really ineffective experience. (Source: Was a parent who realized this and had to compensate for it. The 5-6-7 cycle was much more effective.)
I can see how moving 1st grade into the first bucket would help even things out. I think pre-K was often 2 years, though, so the first bucket still covered 3 ages or grade-levels.
JIRA implementations I've seen don't help people see what's ahead; they focus on what's been done to date. If you're on a single, small team that has minimal dependencies on other teams, that can work, but if the project has any significant dependencies on other teams, it becomes very hard for anyone to understand how things are going.
How do you move money among the accounts? I like the idea of using multiple bank accounts as financial firewalls for my money, but it seems difficult or expensive to move the funds, especially if the accounts are not all at the same institution.
ACH transfers (aka bill pay in some banks), most regular payments out of account X also have a corresponding transfer ~5 days prior from a main cash account to account X.
It's not flawless, but it is insulation against ACH fraud, both electronic and forged checks/e-checks (I've been hit by both before).
It also makes it nearly impossible to use most budgeting softwares out there, aside from battle-tested Excel.
A serious problem with biometrics is credential revocation. The best answer I've seen to this is using the biometric to locally unlock some other credential like a certificate that can be revoked. There are other problems that are flashier, like spoofing and liveness, but revocation is a real show-stopper that is frequently ignored.
The new FIDO UAF standard solves exactly this problem, all biometrics are only unlocking a local identifier preferable on Secure Element or in a Trust Zone.
It's great that this exists. Many typical users are still befuddled by multifactor authentication, and the one thing that helps is practice. Unfortunately, by having all these islands of identity, the frequency of interaction for many of them ends up being low, resulting in users forgetting they enabled MFA and the associated recovery costs.
There have been technologies to try to bridge the identity islands -- social login (which previously created trust issues through OAuth abuse - many resolved, but trust is hard to win back), Mozilla persona and others. But, at the end, the hostility of end user identity is still a problem that needs to be solved in such a way that end users have good authentication choices (no more bad security questions, for example) with good security attributes (low replay, discoverability and guessability, for example) with good usability. Ideally, an end user should be able to choose an identity provider, trust them, and then use that identity provider across multiple services. I know that some companies are working on this, but it still tends to be in islands, rather than an industry group, for example, dedicated to making it work. At this point, a de facto standard may be the best thing.
I've been in meetings with IAM architects at large banks who scoff at social login because they don't want to trust social login security, yet their own end user security is marginal. Some honest conversations need to happen in this space to help move things forward.
Better identity infrastructure for end users will help service providers.
Great points. I love TFA (e.g. Google Authenticator) but I recognize that ~95% of Internet users will never care as long as it is as hard to use as it currently is.
