1,437 karma · joined October 10, 2019
[ my public key: https://keybase.io/hwbehrens; my proof: https://keybase.io/hwbehrens/sigs/dLHJ81Px5e89QVjFDYNRo6_ogUJozHWtgGR9MK3AYQQ ]
It wasn't revealed at all until the founder's memoirs in 2007, and it wasn't reported widely until this [1] 2014 article.
0: https://awrestaurants.com/blog/aw-third-pound-burger-fractio...
1: https://www.nytimes.com/2014/07/27/magazine/why-do-americans...
To reach Authenticator Assurance Level (AAL) 2, there are restrictions placed on PSTN-delivered OOB verification as described in Sec. 5.1.3.3. They explicitly state (in Sec. 5.2.10) that the validity of restricted authentication can change at any time, AND that organizations "SHALL" offer alternative MFA options that are not restricted.
Specifically: "The use of a RESTRICTED authenticator requires that the implementing organization assess, understand, and accept the risks associated with that RESTRICTED authenticator"
So now when you go to the PHB and say, the government says that we are potentially opening ourselves up to legal liability according to such-and-such document subsection whatever, you're much more likely to get allocated resources to implement alternative options. Plus, the government could potentially disallow phone-based 2FA at any time! Imagine how the board will react when they find that we didn't plan for this contingency and suddenly can't comply...
There is a 3rd scenario that I've occasionally seen: Two employees with the same title on the same team. Employee One is unhappy because they are paid 10% less than Employee Two, despite same experience and title. Employee Two ALSO unhappy because in practice they do 50% more work than Employee One for 10% more pay.
I still don't see the parent's connection of transparency to lower pay, but there is a rich scientific literature on the concept of "Comparison is the thief of joy" -- I hypothesize that turnover rates might positively correlate with transparency because they could promote intra-team competitive feelings.
The exception would be if there were a rigid structure that you know going in, similar to how e.g. government pay scales work. Since you know going in that the only input is seniority, you won't care that exceptional work is not rewarded because that was made clear from the get-go, and if that would have bothered you you wouldn't have accepted the offer in the first place.
The natural counterargument to that is that if the only input to compensation is seniority, then there is reduced incentivization for performing "above and beyond", possibly cultivating a culture of mediocrity.
It also would promote pay equity, however, since e.g. employees' implicit biases and social conditioning would not come into play under subjective evaluations.
This is just speculation, but based on a conversation with my partner, there are two types of computer users. The first group makes use of hierarchical storage, consistent naming conventions, and other organizational tricks to give them a rough idea of where any file might be. The second group has never heard the term "file systems" and just stores everything with an arbitrary name in whatever location the originating application uses by default.
The first group would prefer to search the given directory, because the supplied context (of which folder to start the search in) drastically improves/speeds search results. The second group prefers to search the entire disk, because supplying that additional context is impossible - any file might appear anywhere.
The set intersection between the first group and "people who change their default settings" is much higher than it is with the second group. Consequently, the whole disk search is enabled by default.
Additionally, given the addition of an "All My Files" view in Finder (a feature which the first group would probably find baffling), Apple may also believe that the latter group outnumbers the former.
If you had a specific (sub-)field of science that you were looking for, you might have better luck with your search.
In CS research, this many references in a peer-reviewed work would be a red flag for me, however.
If it were an NSF grant proposal, then it would actually be fairly few -- for whatever reason grant proposals might have 300+. So, the context is very important when evaluating citation prevalence.
Of course, if you keep the approach private and use it for yourself, there's no guarantee that someone won't find it in the future and either exploit it or report it themselves. Do you feel comfortable having cameras in your house that could (in theory) be accessed silently by an unknown 3rd party?
A smart home is just a problem solver, and everyone has different problems.
Just to give you some context as a counterexample, I often need to read 10-50 pages of dense, size 10, double column scientific PDFs with many graphs and figures. These documents, which are typically either A4 or letter size, look abysmal at nearly any scale <90%. Color is also regularly required to parse many graphs properly.
I use my Kindle exclusively for reading documents which are primarily lightly-formatted text (e.g. novels, textbooks, etc) but it's atrocious for PDFs. When needed, I switch to an iPad Pro that I use exclusively for reading (and annotating) these PDFs, which is likewise horrible for reading "regular" text.
It seems silly that most of the volume and weight of the device I carry around daily are totally unused, and that most of the tradeoffs it makes are irrelevant to me, but most small desktop machines are either too large or too slow (to meet a price point, presumably?). None that I know of is designed to operate from a single Thunderbolt cable like a docked laptop can.
Does such a product exist? I understand that this is a small fraction of a fraction of a use case, and until recently connectivity options weren't really there to support such a device, but I think there is some promise in this idea.
The Framework desktop case seems to come the closest so far, but it still doesn't (I think?) address the single-cable connectivity question. There's not too much info about it on the website so I couldn't answer all my questions about it.
I suppose for simple libraries this might be possible (e.g. left-pad) but how would you know in general that something is bug-free? `units` was introduced in 1979 and is still one of the canonical examples used in automated program repair research to show that new bugs can be found even in extremely well-studied codebases.
I think people might be:
1. Implicitly assuming that all nontrivial code has bugs, and 2. Using recent commits as a signal that means, "If I ran into a bug, there is someone who might fix it (or at least accept a fix PR) to take away my immediate pain.
> How would this work for cars or couches or headphones?
This would be great for many things! I'm sure there are plenty of people who just want a good quality, reasonably priced -whatever- and would be fine with this model. Actually, that seems like it's basically just the business model for Kirkland.
If there was a retailer who just sold one carefully-chosen thing in each category, I think they'd do pretty well. They wouldn't be able to capitalize on market segmentation, fashion trends, etc. which would hurt their profitability, but they'd also benefit from being the "default" choice for many people.
Another article [1] suggests that it's not actually raw generation that will be the constraining factor, but actually power quality -- the authors suggest that cleaning and converting the power for high-voltage DC charging could be a much bigger task than scaling generation.
[0]: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=883...
[1]: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=933...
If they pre-cooled the night before it might be a different story.
Of course, that oversimplifies the problem somewhat, since any changes could worsen the situation overall, e.g. decreased mental health. Sitting in a bare room paid for by someone else and watching the wallpaper peel away has very little out of pocket cost, after all.
The counterargument is that homelessness and loss of medication would probably be far worse -- for example, it could be wiser to sell the car and live an ascetic lifestyle for 16-24 months until the disability appeals are processed, at which point the OP could return to an equilibrium. Stretching out the runway, so to speak.
Forming any actionable advice in this vein is impossible without a better understanding of the OP's costs, however.
I would argue that this trait is not unique to blockchain systems -- in fact, if you presented this argument without context, I doubt many readers would put blockchain in the top 5 potential referents. See: economic systems, political power struggles, social structures, etc.
I can't speak for the parent, but when most people say this they mean "least likely to break my websites", completely ignoring that this is a symptom, not a cause, of Chrome's dominance. Even my health insurance website breaks in Firefox, and their error message suggests that everyone should just use Chrome. We'll end up back in the early 2000s Internet Explorer situation eventually before the pendulum swings around again.
I used to sit in a cubicle under fluorescent lights, and I often received compliments on my webcam quality when I used a C920e, which I think has the same quality as the C920.
Don't underestimate absolutely horrendous laptop webcams becoming normalized, especially after stream compression.
I guess it's probably unrealistic to expect P-values in a blog post, though...
This is actually fairly common in Apple-land, now that I look:
- ADB (1986) to PS2 (1987) to USB-A (1996) for HID
- Firewire (1995) to USB 2.0 (2000) to Firewire 800 (2002) to USB 3.0 (2008) for data transfer
- VGA (1987) to ADC (1998) to DVI (1999) for video
A lot of the connectors they proposed are now lost to the mists of time, but I can at least understand the argument that some of these changes were plausibly driven by Apple's rejection of the then-standard in favor of some new benefit (faster speeds, better UX), which lasted only until a new standard was developed to incorporate that benefit, and the process repeats again.
While the article specifically calls out biology programs, at my university the CS department is similarly affected. (Stipends are set at a standard rate for all engineering depts.)
If your stipend is $19K, a single student's take-home pay is $16,734, less ~$1,600 in required departmental fees. So, you've got about $1261/mo to pay for everything. If you split a 1-bedroom for $2.2K (not including utilities), that means you've got $161 for electricity, food, phone, internet, fun, literally every other expense for the rest of the month.
The rapid rise in rents is the big killer here -- the difference between $500 and $1000 for a shared room is more than enough to break the bank.
The effort we invest to encourage thoughtful dialogue is paid back in the long run by keeping the quality of discourse high(er) and making less work for dang.