The better solution (and one that will likely be at least partially implemented on the PCI DSS facet of this sort of issue) is to simply remove access to customer records from employees who do not need to see them. There are already mechanisms in play that do this-- even granting limited access to a specific record at the moment that it is needed, and then removing access when it isn't.
It's worrying, but not at all surprising that Verizon doesn't understand how to secure the privacy of their customers.
Yeah, I could have told the crazy story of early cox/torvalds talent retention as played out by my own role in the years-long tulip driver debacle, highlighting the interplay of politics and innovation using specific examples which also (poetically) draw clean comparison between this interplay both on the developer and on the user side, possibly even successfully explaining a bit about, for example, why Redhat is allowed to call their kernel "linux" despite a decade of mucking about with the headers so much that software of any complexity has to be built specifically for it.
But one sentence seemed just a bit more efficient with all of that.
I explicitly called it a "minor issue" in the post you referenced--and it is. It's no more disabling in my life (perhaps it would be in others) being color blind.
It's important to make the distinction. It makes it easier for people who are actually disabled to get the help they need.
Did I ever say I was disabled? Read for comprehension, anonymous.
And finally the object lesson of the problem itself. Reading for comprehension. I daresay if it was done a bit more often, I wouldn't be in the position of it being a thoroughly good time to spend all my mod points on the down side.
See, whats going on here is that since I never post anonymously on slashdot, but only with one of several named accounts, a few people have taken it upon themselves to mod me down whenever they get the chance. I think this is what they call "revenge".
Clearly, I posted the first response to this article, as you can see above. Therefore it is not redundant. Six hours after I posted it, it was modded to +5, insightful.
Hey anonymous coward from the other thread, why did you mod this one down? Do you need me to tell you when I'm trolling and when I'm not? I can certainly do that.
In fact, here's the new rule. From now on, whenever I actually mean what I say in a post and I'm not being mean for its own sake, but for say the sake of object lesson (for example), I'll put this little note at the end:
If the software you're licensed to use from this company is not OSI compliant and you must have OSI compliancy, and if the GPL version IS compliant, then your course of action is clear:
Dump the license and use the GPL stuff to your heart's content. Where's the issue?
There should never have been an exception. Delusion is delusion, whether it's about being followed by snickering hoodlums in red and white cars, or if it's about sky daddy and his zombie kid ruling invisibly from somewhere...beyond...
Bleh. Horseshit is horseshit, no matter how much mayonnaise you dip it in.
Actually in many cases, you do too--at least with Virgin and Deutsche Telekom. And to be fair and balanced, as they say, about it, the number of commas in this sentence be damned, people in the US are not generally paying by the megabyte for broadband connections. Ah, you don't live in the US. I'm truly sorry.
Hey, thats fine. I'll just keep on keepin' on...in this case harvesting as many mod points as I can with replies specifically engineered to impress children who believe they're technically savvy, and then using them all (along with a few others now--looks like its a growingly popular idea!) to randomly mod down posts that in no way deserve it.
Once again modded down by children who don't read histories. Lets see, that's two points that I can now (according to my promise, see, poetically, my history) go and use to randomly mod down some randomly selected posts that probably deserve the opposite.
I suppose I could redeem myself in the eyes of these children and possibly reverse the above score by explaining (and giving three or four examples) of the kinds of things you hear from Google employees when you share a taste for coffee and when you happen to work across the street from their headquarters in Manhattan.
But why bother posting that kind of thing here, where it would be most assuredly lost in the effluvia of adolescent males?
Feel free to mod this down too. I've got five points left at the moment and so far only two have been accounted for.
That's some amateur shit to have made it beyond beta 1. What the hell are your programmers doing all day?
I'm starting to get a little suspicious, to be frank. You've existed for many, many moons, Google...you have over 20,000 employees. You have computing capacity that's normally limited to that of small countries. Shouldn't you be a little further along by now?
I know locate well. I use the above method (the line that creates biglist is actually part of a cron job that deletes the old one and generates the new one every so often, ideally) because find is actually far less resource intensive on the machines I use than updating the located database. It's also substantially faster.
Apart from that I'm just so used to grep syntax that it's faster for me to craft a regex in a grep command that will find precisely what I want than monkey with locate to do it.
Slashdot Mirror
5 insightful points for parroting every revolutionary from Socrates forward?
The better solution (and one that will likely be at least partially implemented on the PCI DSS facet of this sort of issue) is to simply remove access to customer records from employees who do not need to see them. There are already mechanisms in play that do this-- even granting limited access to a specific record at the moment that it is needed, and then removing access when it isn't.
It's worrying, but not at all surprising that Verizon doesn't understand how to secure the privacy of their customers.
Yeah, I could have told the crazy story of early cox/torvalds talent retention as played out by my own role in the years-long tulip driver debacle, highlighting the interplay of politics and innovation using specific examples which also (poetically) draw clean comparison between this interplay both on the developer and on the user side, possibly even successfully explaining a bit about, for example, why Redhat is allowed to call their kernel "linux" despite a decade of mucking about with the headers so much that software of any complexity has to be built specifically for it.
But one sentence seemed just a bit more efficient with all of that.
I explicitly called it a "minor issue" in the post you referenced--and it is. It's no more disabling in my life (perhaps it would be in others) being color blind.
It's important to make the distinction. It makes it easier for people who are actually disabled to get the help they need.
"The challenge on the flip side of that is to make sure that everyone in the Fedora community feels valued"
FAIL
Did I ever say I was disabled? Read for comprehension, anonymous.
And finally the object lesson of the problem itself. Reading for comprehension. I daresay if it was done a bit more often, I wouldn't be in the position of it being a thoroughly good time to spend all my mod points on the down side.
See, whats going on here is that since I never post anonymously on slashdot, but only with one of several named accounts, a few people have taken it upon themselves to mod me down whenever they get the chance. I think this is what they call "revenge".
Clearly, I posted the first response to this article, as you can see above. Therefore it is not redundant. Six hours after I posted it, it was modded to +5, insightful.
So, revenge it is then.
Hey anonymous coward from the other thread, why did you mod this one down? Do you need me to tell you when I'm trolling and when I'm not? I can certainly do that.
In fact, here's the new rule. From now on, whenever I actually mean what I say in a post and I'm not being mean for its own sake, but for say the sake of object lesson (for example), I'll put this little note at the end:
(im being super cereal!)
Just like that.
(im being super cereal!)
What disability?
Hey excellent, some child modded me down again. Time to do what I do best with MY mod points. Thanks for reminding me!
It's not anywhere near this complicated.
If the software you're licensed to use from this company is not OSI compliant and you must have OSI compliancy, and if the GPL version IS compliant, then your course of action is clear:
Dump the license and use the GPL stuff to your heart's content. Where's the issue?
There should never have been an exception. Delusion is delusion, whether it's about being followed by snickering hoodlums in red and white cars, or if it's about sky daddy and his zombie kid ruling invisibly from somewhere...beyond...
Bleh. Horseshit is horseshit, no matter how much mayonnaise you dip it in.
Really are you surprised that this is an ask slashdot? Not one of these people even remembers what the chicken was on alt.hack.
It's not funny if you have to explain it.
Actually in many cases, you do too--at least with Virgin and Deutsche Telekom. And to be fair and balanced, as they say, about it, the number of commas in this sentence be damned, people in the US are not generally paying by the megabyte for broadband connections. Ah, you don't live in the US. I'm truly sorry.
Hey, thats fine. I'll just keep on keepin' on...in this case harvesting as many mod points as I can with replies specifically engineered to impress children who believe they're technically savvy, and then using them all (along with a few others now--looks like its a growingly popular idea!) to randomly mod down posts that in no way deserve it.
Because really, fuck this place.
Ahem, look at the time stamp, moderator. It wasn't redundant when I posted it FIRST.
I've been a pro for twenty years, and I've always used usenet, and still do to this day. What pros are you talking about?
NO SHIT.
Three points. Keep it up.
Once again modded down by children who don't read histories. Lets see, that's two points that I can now (according to my promise, see, poetically, my history) go and use to randomly mod down some randomly selected posts that probably deserve the opposite.
I suppose I could redeem myself in the eyes of these children and possibly reverse the above score by explaining (and giving three or four examples) of the kinds of things you hear from Google employees when you share a taste for coffee and when you happen to work across the street from their headquarters in Manhattan.
But why bother posting that kind of thing here, where it would be most assuredly lost in the effluvia of adolescent males?
Feel free to mod this down too. I've got five points left at the moment and so far only two have been accounted for.
That's some amateur shit to have made it beyond beta 1. What the hell are your programmers doing all day?
I'm starting to get a little suspicious, to be frank. You've existed for many, many moons, Google...you have over 20,000 employees. You have computing capacity that's normally limited to that of small countries. Shouldn't you be a little further along by now?
Dude, EXCELLENT catch there. I'd forgotten about that completely! My slowly growing leisure time thanks you.
I know locate well. I use the above method (the line that creates biglist is actually part of a cron job that deletes the old one and generates the new one every so often, ideally) because find is actually far less resource intensive on the machines I use than updating the located database. It's also substantially faster.
Apart from that I'm just so used to grep syntax that it's faster for me to craft a regex in a grep command that will find precisely what I want than monkey with locate to do it.
Though I really have no idea why:
/* >> biglist
find
grep -i $SOMETHING biglist
Actually that hasn't impressed anyone in a while, come to think of it. At least not since Apple figured out what a find index is.