as a parent of a kid dealing with CommonClusterfuck I can say that this has *nothing* on just how political and railroaded CC is.
[rant] Us parents were billed as "it's an additional method to help us teach, not all kids understand the math lessons we grew up with"... BUT! My kid is hyper analytical (and an aspie, so...) he thrives on a sheet of graph paper and columns for long division, not this brainfuck of repeated additions and subtractions to find the right answer. He was reduced to sobbing trying to figure out how to do his homework, which might as well been written in greek, considering the teachers can't even properly explain it.
I read it, extracted the actual division problems and taught him how to use graph paper to keep his columns straight for classic long division with remainders. He did the entire worksheet with the right answers. and got an F.
Any other algo that could detect "soft" changes to the image would have to store something that is not a hash, but is rather a (basically) reversible image map. I suppose you could just edge detect the image and store that data as a "hash" and any other image that had the same edges at the same relative offsets from each other would be blocked, but I think that could increase the false positive rate.
Seriously, they could release a "restrict pic" app that you could use to generate the hashes locally and then upload just the hash, but... All the revenger has to do is change some metadata, or a pixel, and BANG! new hash. Making this all relatively pointless.
Well in this particular case since they're expecting you to upload your nudies that implies you took a selfie or some such... in which case I'd like to add an addendum to GP:
and for $DIETY sake, don't take nudies and send them to someone!
Also I have a tangential question (sorta reverse revenge porn): 1) Minor takes nude selfie and sends it to target (say hated step parent). 2) Reports target for being in possession of CP. 3) now what?
Absolutely agree. And as Kapersky has demonstrated with the KGB, Apple may be compromised by an individual (or small group) of dev who is working for No Such Agency and would have little/no way of knowing.
Well, the second one is just the writer pointing out they're using the implicit operators (usually you don't need to spell out @_ or $_), eg: $foo = shift; is equivalent to $foo = shift @_; and foreach @someAry{print;} is equivalent to foreach @someAry{print $_;} is equivalent to foreach $foo @someAry{print $foo;}
now, in *most* code it is rude to the people that come after you and who may not have a deep grasp of Perl's oddities to use all the implicit stuff, so you spell it out with $_ and such. In something really buried that last foreach loop will be slower because it has to do an assignment, while the first two will be faster. This only counts when you're looking at *massive* loop counts, at which point... why are you using a scripting language again? Lack of comments, and shit code is on the coder, not the language. I can write unmaintainable C/C++ just as easily as I can Perl, easier even, because I can have some seriously hidden interactions that I rely on but that you have *no* way of knowing interact (like mallocing the same memory block to two different structs and using them as a conversion pipe).
As to the TIMTOWTDI issue, that's helpful and hurtful, and a lot is because of how the language is assembled I think.
2000 if you're counting Python 2. 2008 for Python 3.
and you just hit my single biggest gripe with Python! I have Py 2.x code that I can't use in Py 3.x *WHY* When Perl made the jump from 4 to 5 there was a lot of care taken in backwards compatibility with the addition of one single line to the code *possibly* being required for any given perl4 script.
I learned ANSI C, then went back to K&R for curiosity. I still maintain that Perl is C for lazy programmers. Inevitably I find myself making C syntax errors that are *duh* errors after having been writing Perl scripts for a while... but that's because the overall syntax is so similar that I think they occupy overlapping parts of my brain.
remember PHP initially stood for "Perl Hypertext Preprocessor". Took everything about Perl that was good and shot it, leaving only the bad bits behind.
I *love* perl. It is C for lazy programmers. I tend to use it for four distinct problem domains:
* one-offs for data processing (file to file, file to stream, stream to file, stream to stream). When I'm done I don't need it any more
* glue code for complex build processes (think a preprocessor and puppetmaster for G/CMAKE)
* cgi scripts on websites. Taint is an amazing tool for dealing with untrusted user input. The heavy lifting may be done by a back end binary, but the perl script is what lives in the/cgi-bin dir.
* test applications. I do QA and Perl is a godsend for writing fuzzers and mutators. Since it's loosely typed and dynamically allocates/frees memory in a quite sane manner it is able to deal with the wacky data you want fuzzers to be working with.
That depends, what's the battery lifetime? If the battery lifetime is 7 years then those batteries are going to enter the supply stream same as ultra high grade ore. Pb-H2SO4 batteries are something like 98% recyclable (and most of that 2% is the casing). I presume that other metal chemistry batteries are similar in their recyclability, so the waste stream actually makes a very large portion of the supply stream once you're past the initial growth period and are in or near maturity.
Given their very public stance WRT to the iPhone crypto issue I would tend to believe them more than some others... Or at least be willing to give them benefit of doubt.
HIPPA, Pretty sure they'd be in deep shit in the US too if they kept *medical* info about you.
From what I understand they basically don't screen private stuff for much beyond viruses and CP. Once you share it, it becomes subject to tighter scrutiny.
My vendor (Pixel on T-Mobile)? no. Google? yup. I literally only had to sign into my phone and auth my phone from my desktop (which was auth'd from one of three yubikeys) and *everything* was there within a few hours. All apps (that were compatible, there was one that worked on the Nexus5 but not the Pixel), contacts, call history, SMS history, WiFi network credentials, *EVERYTHING*.
All in all I considered this to be brilliant (and I knew it was being done because I turned it all on).
For the stuff that I don't want the world's governments and advertisers to not have access to I use a burner phone, with no account, and sideband loaded APKs and its own number. Yes they can still link the two if they have access to the cell providers as they both reside at the same location most of the time, but if BadGuys(tm) want me that bad I'm fscked anyway.
or the easiest, for a form you want to use from a bot farm that needs Captchas solved just window them on your page for a live user to solve in order to access something they want... porn, answers to tests, whatever.
Slashdot Mirror
as a parent of a kid dealing with CommonClusterfuck I can say that this has *nothing* on just how political and railroaded CC is.
[rant]
Us parents were billed as "it's an additional method to help us teach, not all kids understand the math lessons we grew up with"...
BUT!
My kid is hyper analytical (and an aspie, so...) he thrives on a sheet of graph paper and columns for long division, not this brainfuck of repeated additions and subtractions to find the right answer.
He was reduced to sobbing trying to figure out how to do his homework, which might as well been written in greek, considering the teachers can't even properly explain it.
I read it, extracted the actual division problems and taught him how to use graph paper to keep his columns straight for classic long division with remainders. He did the entire worksheet with the right answers. and got an F.
[/rant]
/win
I assumed the same (signature) but TFA actually points out: "Cryptographic Hash".
so...
I still assume signature.
Any other algo that could detect "soft" changes to the image would have to store something that is not a hash, but is rather a (basically) reversible image map.
I suppose you could just edge detect the image and store that data as a "hash" and any other image that had the same edges at the same relative offsets from each other would be blocked, but I think that could increase the false positive rate.
Seriously, they could release a "restrict pic" app that you could use to generate the hashes locally and then upload just the hash, but...
All the revenger has to do is change some metadata, or a pixel, and BANG! new hash.
Making this all relatively pointless.
Well in this particular case since they're expecting you to upload your nudies that implies you took a selfie or some such... in which case I'd like to add an addendum to GP:
and for $DIETY sake, don't take nudies and send them to someone!
Also I have a tangential question (sorta reverse revenge porn):
1) Minor takes nude selfie and sends it to target (say hated step parent).
2) Reports target for being in possession of CP.
3) now what?
slowly, but when (if?) it lands it will still support Perl5 code... So I don't understand your point in asking about 6.
Honestly, perl6 isn't really needed, as a result I doubt it will ever hit 1.0.
almost certainly.
Beautiful tool that thing...
Absolutely agree.
And as Kapersky has demonstrated with the KGB, Apple may be compromised by an individual (or small group) of dev who is working for No Such Agency and would have little/no way of knowing.
Well, the second one is just the writer pointing out they're using the implicit operators (usually you don't need to spell out @_ or $_), eg:
$foo = shift;
is equivalent to
$foo = shift @_;
and
foreach @someAry{print;}
is equivalent to
foreach @someAry{print $_;}
is equivalent to
foreach $foo @someAry{print $foo;}
now, in *most* code it is rude to the people that come after you and who may not have a deep grasp of Perl's oddities to use all the implicit stuff, so you spell it out with $_ and such. In something really buried that last foreach loop will be slower because it has to do an assignment, while the first two will be faster. This only counts when you're looking at *massive* loop counts, at which point... why are you using a scripting language again?
Lack of comments, and shit code is on the coder, not the language. I can write unmaintainable C/C++ just as easily as I can Perl, easier even, because I can have some seriously hidden interactions that I rely on but that you have *no* way of knowing interact (like mallocing the same memory block to two different structs and using them as a conversion pipe).
As to the TIMTOWTDI issue, that's helpful and hurtful, and a lot is because of how the language is assembled I think.
Yeah, Python that fad language from 1991.
2000 if you're counting Python 2. 2008 for Python 3.
and you just hit my single biggest gripe with Python!
I have Py 2.x code that I can't use in Py 3.x *WHY*
When Perl made the jump from 4 to 5 there was a lot of care taken in backwards compatibility with the addition of one single line to the code *possibly* being required for any given perl4 script.
not once they dig into it... The Perl bits are what came from Rational, and still work. ;)
I learned ANSI C, then went back to K&R for curiosity.
I still maintain that Perl is C for lazy programmers. Inevitably I find myself making C syntax errors that are *duh* errors after having been writing Perl scripts for a while... but that's because the overall syntax is so similar that I think they occupy overlapping parts of my brain.
We are, apparently, a very tiny minority...
Except that the language is still in production everywhere.
As an aside:
Clear Case source control system has *massive* swaths of its codebase written in Perl.
You're conflating the language with a library. Python can't lift heavy loads, it needs the Tensor Flow lib to do that for it.
remember PHP initially stood for "Perl Hypertext Preprocessor".
Took everything about Perl that was good and shot it, leaving only the bad bits behind.
I *love* perl.
It is C for lazy programmers.
I tend to use it for four distinct problem domains:
* one-offs for data processing (file to file, file to stream, stream to file, stream to stream). When I'm done I don't need it any more
* glue code for complex build processes (think a preprocessor and puppetmaster for G/CMAKE)
* cgi scripts on websites. Taint is an amazing tool for dealing with untrusted user input. The heavy lifting may be done by a back end binary, but the perl script is what lives in the /cgi-bin dir.
* test applications. I do QA and Perl is a godsend for writing fuzzers and mutators. Since it's loosely typed and dynamically allocates/frees memory in a quite sane manner it is able to deal with the wacky data you want fuzzers to be working with.
That depends, what's the battery lifetime?
If the battery lifetime is 7 years then those batteries are going to enter the supply stream same as ultra high grade ore.
Pb-H2SO4 batteries are something like 98% recyclable (and most of that 2% is the casing). I presume that other metal chemistry batteries are similar in their recyclability, so the waste stream actually makes a very large portion of the supply stream once you're past the initial growth period and are in or near maturity.
Given their very public stance WRT to the iPhone crypto issue I would tend to believe them more than some others...
Or at least be willing to give them benefit of doubt.
hey... S&M has a big following. He's just added "on the internet" to it. The old .com business model at its finest!
My cloud resides in "The Planet" datacenter down in Brea, CA, USA.
I have control over it, though it's someone else's HW (VPS).
HIPPA, Pretty sure they'd be in deep shit in the US too if they kept *medical* info about you.
From what I understand they basically don't screen private stuff for much beyond viruses and CP. Once you share it, it becomes subject to tighter scrutiny.
My vendor (Pixel on T-Mobile)? no.
Google? yup. I literally only had to sign into my phone and auth my phone from my desktop (which was auth'd from one of three yubikeys) and *everything* was there within a few hours.
All apps (that were compatible, there was one that worked on the Nexus5 but not the Pixel), contacts, call history, SMS history, WiFi network credentials, *EVERYTHING*.
All in all I considered this to be brilliant (and I knew it was being done because I turned it all on).
For the stuff that I don't want the world's governments and advertisers to not have access to I use a burner phone, with no account, and sideband loaded APKs and its own number. Yes they can still link the two if they have access to the cell providers as they both reside at the same location most of the time, but if BadGuys(tm) want me that bad I'm fscked anyway.
"Going back to my ex is a horrid idea, until you... nah, still a horrid idea"
Sry, I've been doing QA work all day, I'm on a run breaking things.
or the easiest, for a form you want to use from a bot farm that needs Captchas solved just window them on your page for a live user to solve in order to access something they want... porn, answers to tests, whatever.