I think the idea is that you pay the ISP for a "Netflix booster", and then your Netflix traffic gets un-humped into the fast lane.

Is it just me, or does anyone else see the foolishness in one of the highest volume uses of the Internet also being one of the highest priority? That people are thinking of the huge transfers of pre-produced video as being something other than the dead last, lowest priority cheapest-per-byte traffic there is, is totally ridiculous.

The only things that should be "fast laned" (low latency) are VoIP, videoconferencing, interactive terminals, etc: most of which is either low-bandwidth or else niche. If "high priority" is what many peoples' connections are doing several hours per day, then our very sense of "priorities" is fucked up.

I can't say I'm a fan of the ISPs that Netflix is fighting with, but at the same time: Fuck Netflix. Netflix is a case study in how to do video technologically wrong and it seems like they're just totally ignoring common sense. Why shouldn't doing things like a luddite, be relatively expensive? (Really, having storage in your box is still considered prohibitively expensive? It sure wasn't expensive in 2000 with Tivo series 1. Things got worse since then?!?) If the pampered princess insists that her cake be delivered from the kitchen a bite at a time and the commoner just puts a whole slice on his plate and takes a bite at the table whenever he wants it, we expect the princess' servants to be rolling their eyes when she's not looking, embezzeling, etc.

When we have broken up the monopolies and our streets have conduits under them containing a dozen competing fibers, we can re-evaluate the tech from our position of abundance. Maybe video streaming won't be on-the-face-of-it-stupid, then. But that's the future, not today.

Picture, instead of Clippy, we could have Microsoft Creeper.

How apt....

Sure, it's not the most efficient codebase, but on a modern machine with power to spare, it's rather fine. Now, I have run it on a rather high end Core2Duo. That's less fun.

It should be the car that is disabled (or your license taken away)

Exactly - as they do already in the UK: get caught driving while using a mobile phone, you get 3 penalty points. That puts your insurance premiums up in itself, and if you reach a total of 12 points, no more driving for a few years. The penalty may be increased to 6 - in which case, get caught driving on the phone twice, you're in the passenger seat for several years. If someone's been caught driving on the phone (whether texting, talking or reading Slashdot), why let them continue driving at all? Will disabling the phone stop them driving while fiddling with the radio, eating, shaving etc? Of course not - so get them away from the wheel and let them text all they like as passengers.

It is against the law pretty much everywhere. However that law is enforced pretty much nowhere. It is just simply too difficult to enforce it, as a police officer has to catch the person in the act to even write a ticket. And then the ticket is so laughably small in terms of the monetary penalty as to be pointless to even write.

Here in the UK, the penalty is that you get one-quarter of the way to no longer driving (3 penalty points, where 12 means a driving ban); the government announced earlier this year they were considering doubling that to halfway, i.e. get caught doing it twice (within 3 years) and you won't be driving again. However small the risk, I suspect that's a big enough deterrent to scare many - particularly since it would often mean losing their job too. You don't have to be caught red-handed, either, just suspected enough for the police to investigate, then they check the network usage logs and confirm you were using the handset at the time in question. (Or get seen on a traffic camera, of which there are many.)

The idea in the article is just silly, though.

Crazy, isn't it?

Evidently, there is some unwritten law that states that Geolocation by IP address shall override any and all set preferences by the user on their device, and ignore any possibility that barring or redirecting the user makes no sense.

I get a version of this periodically on Spotify, where I'm informed that the particular album or single I'm looking at can't be played because it isn't licensed to my region. And of course there's the small matter of my being IP-blocked from Pandora Radio for the same reason.

I ran into a particularly nasty geolocation issue back in late 2012, when I was informed that I couldn't access my National Lottery account because they no longer believed that I was accessing it from the UK. Went back and forth between them and my ISP (VirginMedia), with each blaming the other for the problem.

I've also heard of situations where people have found the books on their Kindles vanishing because they're holidaying in an area where said books aren't licensed.

So sure, it's easier to hang up on them but you are actually doing them a favor and helping them out by doing so.

No, failure to take hostile action isn't a favor; it's neutrality. Installing their malware would be a favor. I can appreciate those with the time and energy to take fight to this enemy (good on you!), but I have other battles to fight with my (however high) limited anger.

The problem with this enemy, which makes it so hard to care, is how irrelevant they are. So they call people about bullshit, wasting their time. That can be annoying, but there are so many more annoying things.

I suppose some people would say this enemy is worse that that, because the call is just a way of performing a SE attack, but I disagree. I just can't help but get blame-the-victim-y with SE attacks like that. I think many of our society's real problems are caused by SE, much of it legal (e.g. "vote for me, because I'm a member of the correct party," or "believe our religion's dogma, because your parents did") and that we'd all be a lot better off with more "scam antibodies" in ourselves. So part of me hopes these scammers flourish, thereby teaching people to stop being so fucking gullible. Maybe you can't fix stupid, but we can try, and an environment full of con artists is good for that. These assholes are evil, but they're good for us.

No, I'm not fully committed to that outlook (sure, I wanna hurt the bad guys too) but I'm conflicted enough that it evens out. And while we're at it, don't knock lazy! So a position of neutrality, it is.

I have never gotten one of these calls. But I have gotten a few calls like this:

[Phone vibrates. I see the non-local calling number. Reject and block.]

That's the new, lazy version. Until a few weeks ago, I had many of these:

[Phone vibrates. I look at the non-local calling number and wonder who that could be. Google the number and apparently every non-local number that ever calls me, is associated with robocalling. Reject. They call again a few days later. Reject and block. Then a few days later I look at my Visual Voicemail which my shitty Galaxy S4 software never tells me has new entries until I refresh it, and some actual human speech may happen.]
ME: "Fuck."
[And I see they left a few messages containing nothing but silence. Delete.]

But that second scenario doesn't happen anymore. Robocallers have successfully trained me.

(I still do things the classic way: filesystem on lvm on luks on mdadm. not using ZFS yet.) I'm not sure it's exactly about what's required.

Consider wear leveling on SSDs. Only the filesystem really understands which blocks need to preserve data and which ones are don't-care. So to do SSDs right, it needs to pass info about unallocated storage down to the volume manager, whch then passes it to the encryption, which then passes it to the RAID, which then gives it to old-school "real" block device (which then passes it to the wear-leveling firmware, I guess). Sure, that can work. But when the filesystem can talk to the physical block device, it's easier. If you're writing block devices that implement things like volumes and encryption and RAID, from your PoV, things that are allocated vs not-allocated are totally different than how the filesystem sees it. To you, a block is just a block and a whole bunch of ioctls are totally irrelevant and not related to what you're working on. You're going to find this type of information to be pesky and you might not handle it right (or more likely, it takes a long time before you handle it at all). And in fact that has happened a few times, where certain block devices' feature set lagged a bit, behind what people with SSDs needed.

I suppose another easily-contrived example would be if you have a few gigabytes of data on a few terabytes of RAID, and need to [re]build the RAID. If your RAID doesn't know which blocks actually have data, then it'll need to copy/xor a few terabytes. If it's a unified system, then it can be complete after copying/xoring a few gigabytes.

Get rid of your dictator and adopt a representative democracy and it will be over. Indeed, nobody could have thought it would go on this long.

..contracts requiring NDA's that now allows customers to review secret details of products or company practices on public forums.

Can someone who favors this, explain why this might be a good thing instead of a bad thing? Maybe an example? It sounds to me like endangering such a (seemingly, to me) bad practice might be an intended consequence, not an unintended one.

I can't even see how a review made under an NDA might be useful. The premise is that the reviewer is withholding information. "The spaghetti was excellent. [censored]I am prohibited from saying anything about the sauce.[/censored]"