This is not exactly what you're looking for, but commercial entities (primarily hotels) have special-application machines for towels, sheets, and blankets. Here's a random example.
The final tally of 30 countries seems unreasonably low to me, but it turns out TFA says "out of 65 surveyed." I think 46% still sounds low, but more believable than 30 of ~130.
Small, but nonzero, even within a single American state. Several months ago I became curious about whether the incidence of First/Middle/Last name matching exactly was more or less common than First/Last name and exact birthdate. I found myself reading an interesting analysis of "duplicate" voter records in New Jersey. From one section:
Applying the “Birthday Problem” to voter registration lists is fairly straightforward. By including the year (and thus the full birth date), the statistics change somewhat, but the threshold is still surprisingly small to many: given some reasonable assumptions about the average lifespan, the probability that at least two of 150 people have the same exact birth date – day, month, and year – is 50%. And in a group of 300 people, the probability that two share a birth date match is approximately 90%.
Imagine that our group contains all of the registered New Jersey voters with a given first name and last name – such as all of the 417 Robert Smiths who are listed on New Jersey records as voting in 2004. The probability that at least two of these 417 individuals have the same birth date – day, month, and year – approaches 100%. The fact that two Robert Smiths with the same birthday voted in 2004 thus indicates not voter fraud, but a straightforward application of the “Birthday Problem.”
Indeed, the probabilities above likely underestimate the chance that a group of voting Robert Smiths share the same birth date, because the above calculations assume that birthdays are randomly distributed when, in fact, they are not. Certain given names are more common in certain years (it would be unsurprising to find two Jessica Smiths born on the same day in 1985, or Lisa Smiths in 1965, or Mildred Smiths in 1925). Likewise, the prevalence of surnames will fluctuate with the immigration patterns of particular ethnicities, which vary from decade to decade. Because older individuals vote at higher rates than younger people, too, we would expect a clustering of voting “Robert Smiths” weighted toward years past. Finally, birth dates themselves are not evenly distributed, as obstetricians are more likely to induce labor during the work week.
I was really excited about v57 (see my posting history), but when the 4 extensions I considered critical were all ported over to WebExtensions, I tried it for a fortnight and gave up.
For all the touting of how great v57 is at RAM usage, particularly for lots of tabs, it was a monster for me. Chrome is comparable. Also, I make use of multiple profiles, each of which has its own proc cluster.
Things about FF I rediscovered and briefly enjoyed: tagging bookmarks; hotkey-able search engines ("jira foo-85"); and autocomplete to switch to an existing tab.
New things in FF I appreciated: lots of customization in the UI; "reading mode".
Things that are bollocks: full-screen mode; RAM usage is still uninspiring; multiple simultaneous user profiles (UI, management, processes); can't get Pocket out of the UI.
I like how they add that innocent little phrase. "...as well as some citizens".
This appears to be a rather broad category of people (solicitors, doctors, interpreters, and the like) who provide professional services to INA individuals and I quote:
Relatives and associates of any of the individuals listed above who are subject to the INA;
There's a funny question I have about how that's interpreted. Does the final clause link to the "individuals listed above or does it link to the "relatives and associates?" Depending on the law's reading, this could be most of the USA and a fair number of everyone who has ever known a person who moved there.
Did your uncle marry someone who wasn't a US citizen from birth? Do you work with a green-card holder? Under one interpretation, that's you, and the DHS can hold for 100 years after your birth, information including the following (among others):
Family, criminal, education, travel, and employment history; Professional accreditation information; Medical information; Social media handles and aliases, associated identifiable information, and search results;
Search results? The DHS is specifically asking to browse your search results? Great work, America.
'hr/' + ENTER is only one more character, and works on some browsers with the all-in-one address bar. To be clear, though, I understand your point and agree that it's an annoyance.
Serious questions here: Have you used v57? Does it still have the sandboxing issue you describe? Or the cross-tab leakage?
I, too, left FF because it ate all my RAM and stalled, but I like what I see in the Nightly and I'm expecting to switch back. Now it's Webkit/Blink/Electron "apps" eating all my RAM.
I don't understand. HTTPS Everywhere and uBlock Origin work just fine on the nightly (v57). I had to ask the extensions to update themselves, but now they work great. I can't speak to the other things on your list, but I also use PrivacyBadger which works fine and performs the functions of Ghostery without phoning home.
I will probably switch to Firefox from my current browser when v57 hits Beta or Stable. I only left because the built-in development tools for WebKit and Blink were better than FF or Firebug.
I am no sound engineer, but I don't think filtering high frequencies above speech would necessarily help their speech comprehension. Upper harmonics might well give hints to the module about the intended words. Second-language learners had more trouble understanding their non-native tongue over the old telephone networks, partly because of the filter on upper harmonics. POTS operators used the lowest bitrate they could get away with.
I assumed someone discovered a pattern to upper harmonics and is exploiting the hinting I described. If this is just shifting a "voice" to an inaudible pitch, that'd be kind of funny and clearly broken. TFA doesn't seem super-clear. I'd be curious to hear more from those who have relevant experience.
Clearly, if it's a security flaw, the companies in question will have to patch it and do something else.
Slashdot Mirror
I think you missed that it's song lyrics.
This is not exactly what you're looking for, but commercial entities (primarily hotels) have special-application machines for towels, sheets, and blankets. Here's a random example.
If you haven't seen this essay by Clay Shirky, you might find it interesting.
The final tally of 30 countries seems unreasonably low to me, but it turns out TFA says "out of 65 surveyed." I think 46% still sounds low, but more believable than 30 of ~130.
You've probably seen this already, but in case anyone else missed the Movie Physics review of The Core, here it is.
NIMH
Small, but nonzero, even within a single American state. Several months ago I became curious about whether the incidence of First/Middle/Last name matching exactly was more or less common than First/Last name and exact birthdate. I found myself reading an interesting analysis of "duplicate" voter records in New Jersey. From one section:
Applying the “Birthday Problem” to voter registration lists is fairly straightforward. By including the year (and thus the full birth date), the statistics change somewhat, but the threshold is still surprisingly small to many: given some reasonable assumptions about the average lifespan, the probability that at least two of 150 people have the same exact birth date – day, month, and year – is 50%. And in a group of 300 people, the probability that two share a birth date match is approximately 90%.
Imagine that our group contains all of the registered New Jersey voters with a
given first name and last name – such as all of the 417 Robert Smiths who are listed on New Jersey records as voting in 2004. The probability that at least two of these 417 individuals have the same birth date – day, month, and year – approaches 100%. The fact that two Robert Smiths with the same birthday voted in 2004 thus indicates not voter fraud, but a straightforward application of the “Birthday Problem.”
Indeed, the probabilities above likely underestimate the chance that a group of voting Robert Smiths share the same birth date, because the above calculations assume that birthdays are randomly distributed when, in fact, they are not. Certain given names are more common in certain years (it would be unsurprising to find two Jessica Smiths born on the same day in 1985, or Lisa Smiths in 1965, or Mildred Smiths in 1925). Likewise, the prevalence of surnames will fluctuate with the immigration patterns of particular ethnicities, which vary from decade to decade. Because older individuals vote at higher rates than younger people, too, we would expect a clustering of voting “Robert Smiths” weighted toward years past. Finally, birth dates themselves are not evenly distributed, as obstetricians are more likely to induce labor during the work week.
I was really excited about v57 (see my posting history), but when the 4 extensions I considered critical were all ported over to WebExtensions, I tried it for a fortnight and gave up.
For all the touting of how great v57 is at RAM usage, particularly for lots of tabs, it was a monster for me. Chrome is comparable. Also, I make use of multiple profiles, each of which has its own proc cluster.
Things about FF I rediscovered and briefly enjoyed: tagging bookmarks; hotkey-able search engines ("jira foo-85"); and autocomplete to switch to an existing tab.
New things in FF I appreciated: lots of customization in the UI; "reading mode".
Things that are bollocks: full-screen mode; RAM usage is still uninspiring; multiple simultaneous user profiles (UI, management, processes); can't get Pocket out of the UI.
A hallowed godded asteroid, then?
In case it is helpful, I griped about this, too, and swillden responded, suggesting that I remove the phone number after adding another 2FA.
It's Xeno's chairman!
Ah, I see the problem: It's the spirits in his keyboard.
"B is for 'Buy n Large,' your very best friend"
Different people have different needs, something that a lot of people commenting on this article don't seem to realize.
The OP is trolling, which is another thing a lot of commenters don't seem to realize.
Sorry about your foot troubles, though. Glad you found something that works.
I like how they add that innocent little phrase. "...as well as some citizens".
This appears to be a rather broad category of people (solicitors, doctors, interpreters, and the like) who provide professional services to INA individuals and I quote:
Relatives and associates of any of the individuals listed above who are subject to the INA;
There's a funny question I have about how that's interpreted. Does the final clause link to the "individuals listed above or does it link to the "relatives and associates?" Depending on the law's reading, this could be most of the USA and a fair number of everyone who has ever known a person who moved there.
Did your uncle marry someone who wasn't a US citizen from birth? Do you work with a green-card holder? Under one interpretation, that's you, and the DHS can hold for 100 years after your birth, information including the following (among others):
Family, criminal, education, travel, and employment history; Professional accreditation information; Medical information; Social media handles and aliases, associated identifiable information, and search results;
Search results? The DHS is specifically asking to browse your search results? Great work, America.
My experience mirrors yours. I am waiting for one extension to release a compatible version, and I'm in.
+1 Funny
I hear he tends to shoot from the hip so take what he says with a grain of salt...
Shoots first ands asks quest^H^H^H^H^H for payment all in advance.
+1 in the "Me, too" sense.
Have you tried adding a trailing slash?
'hr/' + ENTER is only one more character, and works on some browsers with the all-in-one address bar. To be clear, though, I understand your point and agree that it's an annoyance.
uBlock Origin already works, as does HTTPS Everywhere, and Privacy Badger.
Serious questions here: Have you used v57? Does it still have the sandboxing issue you describe? Or the cross-tab leakage?
I, too, left FF because it ate all my RAM and stalled, but I like what I see in the Nightly and I'm expecting to switch back. Now it's Webkit/Blink/Electron "apps" eating all my RAM.
I don't understand. HTTPS Everywhere and uBlock Origin work just fine on the nightly (v57). I had to ask the extensions to update themselves, but now they work great. I can't speak to the other things on your list, but I also use PrivacyBadger which works fine and performs the functions of Ghostery without phoning home.
I will probably switch to Firefox from my current browser when v57 hits Beta or Stable. I only left because the built-in development tools for WebKit and Blink were better than FF or Firebug.
You misunderstand. This is Siri training you to talk in silly voices for its own amusement.
I am no sound engineer, but I don't think filtering high frequencies above speech would necessarily help their speech comprehension. Upper harmonics might well give hints to the module about the intended words. Second-language learners had more trouble understanding their non-native tongue over the old telephone networks, partly because of the filter on upper harmonics. POTS operators used the lowest bitrate they could get away with.
I assumed someone discovered a pattern to upper harmonics and is exploiting the hinting I described. If this is just shifting a "voice" to an inaudible pitch, that'd be kind of funny and clearly broken. TFA doesn't seem super-clear. I'd be curious to hear more from those who have relevant experience.
Clearly, if it's a security flaw, the companies in question will have to patch it and do something else.