722 karma · joined March 31, 2011
I agree, a password manager without E2EE is unusable in my eyes. However, I can also understand the institutional reasons this might be the case. I don't think it reflects an organizational aversion to E2EE.
Because ISPs are no longer required to be dumb pipes, they've started charging their customers a premium for access to video content. This is bad for Netflix, of course, because it cuts into their subscriber base.
They crunch some numbers and come up with an amount they're willing to pay the ISPs to exclude their subscribers from this segmented pricing scheme. The ISPs accept this mutually beneficial deal, and everyone's happy, right?
What about Notflix, though? We don't have the capital that Netflix has to pay into this protection racket, so our subscribers must choose between paying the ISP video premium + our subscription fee, or Netflix's subscription fee.
That's an uphill battle and straightforwardly anti-competitive, but is also the precisely the promise of a world without net neutrality.
I also disagree with your assessment that anybody is subsidizing internet giants. All those players pay for the bandwidth they consume to dump their data into the network. The end-user pays for the other end of the connection. Everything is being paid for, proportionally to the usage.
The last-mile ISPs simply want to double-dip. Comcast thinks Netflix should pay both Level 3 AND Comcast for using the pipes, which fundamentally undermines the architecture of the internet.
By asking you to sign in and sync, they're not just requesting access to information on your person -- that's an enormous expansion of their search powers.
The FCC’s regulations weren’t about protecting consumers’ privacy. They were about government picking winners and losers in the marketplace. If two online companies have access to the same data about your Internet usage, why should the federal government give one company greater leeway to use it than the other?
1. Is he implying that the previous FCC was intentionally boosting content providers over ISPs? What motivation would they even have for doing this?
2. Content providers and ISPs do not directly compete with each other in the course of their primary business, so in what respect does the rule create winners and losers in the marketplace?
I suppose he could mean in the advertising marketplace. I guess I would prefer that both Facebook and Comcast be losers in that marketplace though.
3. Two online companies do not have access to the same data. Facebook has data + metadata for any interaction you have with their platform. Your ISP has metadata for interactions you have with any platform, along with data for any plaintext interactions. This is a massive difference in scale.
Users have the choice not to use Facebook, and thus not provide them with data. Users do not have the choice to access the internet without making use of a public utility (i.e. their ISP).
He cites an expert saying:
Rather, the most commercially valuable information about online users . . . is coming from other contexts,” such as social-media interactions and search terms.
I can see how user-shared data might be considered more commercially valuable, but this misses the point about the differences in the kinds of data we are talking about. When someone publishes on social media, they're making an explicit choice to share information with the public.
When that same person visits a website, it is not commonly understood that this act might reveal personal information (though end-users ought to be more aware of this). Consider a teenager doing research on pregnancy tests -- they do not intentionally publish information, but the metadata (webpages visited, time of visits, etc) is potentially revealing.
Due to the circumstances, normalization wasn't an efficient option. I ended up throwing together a barebones tree with a 5-line DFS implementation to traverse it. It handled inserts, updates and deletions (for my use-case) in linear time.
The details aren't so important as the fact that adding a dependency would have been overkill for my needs. This isn't to say that efficient graph implementation libraries should not exist or be used, but I was able to produce this code faster by having that basic CS knowledge.
I'm also not convinced that depriving new programmers of real-time syntax checking actually helps them learn. Wouldn't immediate feedback help them memorize the correct syntax?
1. FDR did not propose a wage cap until 1942, 3 years after the Great Depression had ended. It was a temporary wartime fundraising effort (and was quite popular with the public). In fact, health insurance really first came into existence during the Great Depression (mostly to ensure physicians and hospitals got paid).
2. FDR's wage cap did not pass.
What actually happened was the passing of the the Stabilization Act of 1942, which gave FDR a power (that he invoked) to freeze wages and salaries during the war. The freeze was deeply unpopular with the labor movement, who threatened mass strikes. As a compromise, congress exempted health insurance (and other benefits like PTO and pensions) from the freeze.
This was certainly a contributing factor (proportion of US population with healthcare roughly doubled from 1940 to 1945), but ignores the other factors that prompted the rise of employer sponsored healthcare. Indeed, by 1945, less than a quarter of Americans had health insurance.
Rather, the two largest contributors to employer-sponsored health insurance was the demand of health coverage by labor unions and the 1954 legislative change that made health insurance tax exempt.
git shortlog -n -sI don't think your example vindicates Best Buy, but rather, simply repeats the central question of the case: was the Geek Squad employee simply functioning as a Geek Squad employee?
The prosecution has argued that an employee who happens to stumble on images of child pornography (analogous to your electrician stumbling on a drug lab) is not acting as an agent of the government. I'm inclined to agree with that judgement.
On the other hand, if the employee was conducting extra thorough searches, scrutinizing the files on any customer storage media, or otherwise performing surveillance tasks that had nothing to do with his job, then it seems apparent that the employee was acting as an agent of the law in accordance with a financial incentive from the FBI. It doesn't help, in this case, that the employee lied about having been compensated by the FBI.
Ultimately, this particular case will come down to the details of how and why the employee stumbled across these images. As a general principle, however, it seems wrong to me that any computer in for miscellaneous repairs (touchpad/screen replacement, battery refurbish, etc) should be subject to a search for illegal data pursuant to an FBI incentives program.
Granting that "reasonability" is a very fuzzy standard, it seems obvious that a product with 30 year old crypto should not be subject to lawsuits because someone got solved integer factorization on real hardware.
http://www.brown.edu/Departments/Economics/Faculty/Matthew_T...
As it turns out, there are more secure devices in the marketplace than the affected phones, but they cost more. All other things equal, a contractual obligation for security policies would increase the cost (and thus price) of devices, and users would likely stick with cheaper options.
https://en.wikipedia.org/wiki/Synthetic_cannabinoids
They typically cause more severe side-effects than traditional marijuana. There have been a few rounds of subway ads related to synthetic marijuana.
The 100-character allowance is for code "maintained exclusively or primarily by a team that can reach agreement on this issue".
Even if it's default browser behavior, keeping it around is a specific design decision.
Google does do this, and in a less subtle way -- it applies the classic, purple styling to visited links.
Still, I find your comments compelling enough to give DDG a shot. I found the results inadequate when I last tried a year or so ago -- I found myself using !g more often than not, which led me to abandon DDG altogether.
My point in writing my comment was to emphasize that the poor pay disproportionately more of their income towards basic needs than the middle class. My hope was that I would provoke some empathy when discussing the economics of poverty.
I don't disagree with you that bail is a tricky issue -- for it to accomplish its goal, it has to mean something. But on the flip side, there are people living in New York City who cannot afford bail and get stuck in the justice system for years without recourse, without a speedy trial, and that seems unjust to me.[1]
A little empathy goes a long way.
[1] http://www.newyorker.com/magazine/2014/10/06/before-the-law
On the flip side, minimum-wage earners are more likely to be employed part-time instead of full-time, but only 10% and 2% respectively of those groups are paid minimum wage or below, so it's pretty tricky to come up with a good estimate here.[1]
My main goal was to illustrate that the poor spend disproportionately more of their income on basic needs compared to the middle class, and inspire some empathy when we discuss the economics of poverty.
Assuming that they pay $1000/mo for their apartment (let's be generous -- this includes rent and utilities), that leaves them with $3,470 every year to cover all other living expenses.
If I spend $50/week on food (which is conservative for NYC), that adds up to $2400, which leaves us at $1070. At that salary, if you spend more than $70 in a YEAR on clothing, healthcare, toothpaste, public transit), then you won't be able to afford $1000 in bail. I spend more than that every year on public transit alone (MTA 30-day pass costs $116.50 -> $1398.00/year).
It's really not hard to see how a $1000 bail can be out of reach for the poor in New York.
http://2014.hackitoergosum.org/bittorrentsync-security-priva...
These concerns were amplified by the difficulty of auditing a closed-source product. Their argument that hashes are one-time secrets and not permanent keys is difficult to validate without access to the source.
Perhaps this was intentional :-)
__mydef -> _myClass__mydef