I have argued this in the distant past and am glad it is getting attention, but we all need to worry about long-term recorded surveillance and the growing developments in machine learning. In the past, the majority of surveillance was recorded short-term and often examined in real-time for human operators to watch over larger areas easily. But we have quickly come to the point where long-term recording is getting cheap enough for indefinite storage. This might seem like a bad thing in itself but made even worse with the fact machine learning also improving to the point where processing hours of the recordings is easily possible with automated software.
This combination means that anyone could in theory be charged with a "recorded crime", meaning that law enforcement did not notice your crime in real-time and no one filed a crime against you but later follow up systems/software found the infraction. At first these systems will probably only be used to help existing investigations but no doubt it will be used later in much the same way as red-light and speeding cameras trying to generate revenue for municipalities.
Should this be allowed in our society? Where do we draw the line?
Secondly, the integrity of the recordings should be paramount. Your idea for encryption is a good one, perhaps expanding it to breaking down the recordings on a 10-15 minute basis with an individual key and checksum for each.
I mention a checksum because we are already at the point where computer generated imagery (CGI) has photo-realism and it could be possible for someone to easily plant images into these streams, allowing the changing of faces, clothing, etc. Body cam footage need to be handled as a chain of evidence and their recordings must be kept secure while also well documented against manipulation.
Law makers need to address this issue now, otherwise this will create a kind of police state that even makes the world of 1984 look like utopia.
The discovery reinforces earlier discoveries from last year about civilizations that groomed the rainforests and lived in the regions for thousands of years before Columbus arrived (with diseases) that wiped them out.
So, instead of modernizing or migrating these antiquated systems that have not been updated in more than a decade now it seems, the entire municipality should migrate the operating system again for their sake and leave them in their sorry state?
Seems like a pretty pathetic strawman to me.
Even if you do not believe in the negative effects of the use of coal (global warming, pollution, atmospheric radiation, etc.), you still need to keep in mind the fact that there is a finite source of that energy. If we use up all of the fuel now, we will have no energy to build alternative energy sources later.
So, it is in our best interest as a species and a nation to invest in alternative longer-term energy solutions when primary finite sources of energy are cheap and plentiful now.
Yes, let's open up web browsers into becoming a huge security and privacy invasion vector so you don't need to use "native apps" because it's "difficult to change platforms".
Meanwhile, any application developer with half a brain should be making their software in a method that is easily ported to the three major platforms.
But no, we should not expect them to do that. Instead, let's just open the browser up to do everything under the sun and hope nothing goes wrong./s
You would lose the wager. Because the files are on my personal AWS account's S3 bucket and can be easily traced back to me by law enforcement if it has anything illegal or harming inside.
I get the joke but the zips are a serious effort to help get the data shared. The original source took almost 6 hours to download fully because did they not compress or compact the files in any way. I'm just trying to save others interested that effort (and their bandwidth budgets for people with caps).
Which is why I want to download it and archive it. If there is a threat that scientific data is going to be attacked and purged, we should all be saving a copy just in case.
As I mentioned above, there is no HTTP compression and it's over 8000 files at over 60 GB uncompressed. Had they compressed it, I am certain it would be less than 1 GB based off the tests I mentioned.
Imagine all the bandwidth being wasted. I think it's incredulous to release a huge treasure trove of data this big and not think of compressing.
They present the data as 23 folders with over 100 ASCII at 5 MBs each. Downloading each one by one is annoying but not a show stopper, but why not compress?
I downloaded one of the files and used 7Zip to throw it into a Z archive. The size went from 5 MB down to 500 KB. I uncompressed to make sure it wasn't a fluke but was 100% accurate.
Shouldn't we expect a little more from the country's best and brightest? I mean, come on...
Or how about we just stop rolling out physical lines to individual houses in rural areas and migrate them all over to wireless technologies. Saves tons of money and is far easier to repair and upgrade.
One fiber trunk to each tiny small town and end-mile over wireless. Quick, painless, modern and economical for all parties.
Apple repurchased 3.18% of outstanding shares during 2016, reducing the number of shares in total. The year over year increase in diluted earnings per share was 2.43%. So, number of shares reduced by more than earnings increased. Typically if revenue increased and total shares decreased, the earnings per share would be greater than the percentage of shares removed.
For example, a company that made $100,000 at the end of 2015 has 1000 shares at the beginning of the year for $100 earnings per share. The company purchased 5% of the shares outstanding during 2016 (950 shares outstanding end of year) and also made $100,000 in revenue, putting the earnings per share at around $105 (an increase of 5% year over year).
Now imagine that same company instead had a decline in revenue of 3%, making $97,000, in 2016 instead. With the reduction in shares, the earnings per share for 2016 would be around $102, which is still greater than the year before at $100.
In the case of Apple, to beat the previous year's adjusted earnings per shares they would have needed 3.18% increase in revenue and not the 2.43% reported.
The six hours old snapshot was a fluke manual LVM snapshot run, normally they are 24 hours. The SQL_dumps weren't running at all because of mis-configuration, producing tiny little files and failing silently. Webhooks will need to be rolled back to the 24 hour backup since they were removed in the 6 hour one because of a synchronization process (meaning at best 18 hours of updates will have no webhooks but possibly all 24 hours at worst). Lastly, their replication of their backups from Microsoft's Azure to Amazon's S3 for what I assume is vendor agnostic redundancy has sent no files at all ("the bucket is empty").
It's like they thought out everything but never made sure any of it was working.
That explains nothing. Let me lay out the numbers for you.
In Q1 2016, Apple made $75.872 billion in a 13 week period or around $ 5.836 billion a week. In Q1 2017, Apple made $78.361 billion in 14 weeks or $5.597 billion per week. A difference of $2.489 billion year over year or a 4% decline in average weekly revenue.
As far as iPhones, they sold around 3.971 million units a week in 2016 and only 3.884 million units a week in 2017, or a decline of around 2%.
Then there's the quarterly earnings per diluted share which did you need to put in context of the buybacks Apple made during 2016. Apple repurchased 167.567 million shares of 5257.816 million outstanding or around 3.18%. Diluted earnings per share for Q1 2016 was $3.28 and Q1 2017 was $3.36 or a difference of 2.43, showing yet another hidden decline.
All of the fluffy language such as "record setting earnings per share" are all meant to throw you off from the truth. Ghoul's quick numbers seem to pan out across the details in the earnings documents.
Many very important computer-based presentations in my life. Contrary to what you say, the correct thing to do is to make sure you have as stable a platform as possible (and a backup). An unpatched system is not considered stable by any measure of the word. If you are worried about upgrading a computer, you're doing something wrong or not covering your bases properly.
People who hate updates are either running on hardware that have unresolved (or unknown if an incompetent user) issues, no regular backups or too slim a budget (time or money) to do their job properly. Or perhaps all three.
As far as the ad hominen, I'm a highly competent, experienced computer scientist with several decades of experience working in not only critical infrastructure systems but presentations as well.
Making sure your computer is up to date prior to an important event is not a "stupid move". Your same ignorant strawman argument could be used against taking vaccinations before traveling overseas but I doubt you'd risk your life or long term health on such moronic logic.
Regardless of context, you have the choice of doing something now that has a slim chance of going wrong and cause a problem that can be fixed before an important or risky event you know will occur, or ignore the issue and hope nothing will happen later with the chance of having a big problem when it really matters and no time to fix.
Anyone choosing the later is a short-sighted fool that deserves the consequences.
If you read the document, it states it is an update to a document last modified in 2011. Which means we do not know when the policy was put in place unless we look at the 2011 version as well and follow the paper trail.
So, can't exactly blame on Obama. On the other hand, this document was leaked under the Obama administration which could have been intentional. Bare in mind, the FBI's mandate and policies are governed by not just the President but Congress as well (if not more so).
Read the article and you will find the author is a complete idiot. He went to an important event where he needed 100% up-time in a public place that he most doubtfully was on a 3rd party wireless network and he made no effort to make sure his computer was up to date before hand. Anyone even on a Mac or Linux PC would still be wise to update before doing this sort of thing as well.
Sounds like an incompetent twit bitching about his own incompetence being undermined by Microsoft's automated systems trying to keep him secure.
Listen, if you're going to lie at least make up a believable number. Studies have shown people believe made up numbers ending in 1 and 7 more than the other eight numbers.
So, if you had said you found 17 medline articles, I might have believed you.
Please don't exaggerate. No one advocating basic income is asking for that much to be given out.
Basic income is designed to help stop people needing to hold two or even three jobs to survive, not stop people from working entirely.
The most reasonable amounts I have heard are pegged to the poverty level, such as 50-80% of the poverty line income (which is around $12,000 in the USA).
That would equate to $500-800 a month given to everyone over 18, which is around 243 million people or $1.5 trillion every year.
Also keep in mind that in a fiat reserve currency system like the USA, not all of that money needs to come from incoming tax revenues and would most likely increase tax revenues since most of the money being given out is going directly into the economy (and not high level banking instruments that only make the wealthy more powerful).
Pretty sure VLC and other video players can do this as well. I know VLC can apply filters and save out videos, and have seen demonstrations of people applying OpenGL shaders to videos.
Slashdot Mirror
I have argued this in the distant past and am glad it is getting attention, but we all need to worry about long-term recorded surveillance and the growing developments in machine learning. In the past, the majority of surveillance was recorded short-term and often examined in real-time for human operators to watch over larger areas easily. But we have quickly come to the point where long-term recording is getting cheap enough for indefinite storage. This might seem like a bad thing in itself but made even worse with the fact machine learning also improving to the point where processing hours of the recordings is easily possible with automated software.
This combination means that anyone could in theory be charged with a "recorded crime", meaning that law enforcement did not notice your crime in real-time and no one filed a crime against you but later follow up systems/software found the infraction. At first these systems will probably only be used to help existing investigations but no doubt it will be used later in much the same way as red-light and speeding cameras trying to generate revenue for municipalities.
Should this be allowed in our society? Where do we draw the line?
Secondly, the integrity of the recordings should be paramount. Your idea for encryption is a good one, perhaps expanding it to breaking down the recordings on a 10-15 minute basis with an individual key and checksum for each.
I mention a checksum because we are already at the point where computer generated imagery (CGI) has photo-realism and it could be possible for someone to easily plant images into these streams, allowing the changing of faces, clothing, etc. Body cam footage need to be handled as a chain of evidence and their recordings must be kept secure while also well documented against manipulation.
Law makers need to address this issue now, otherwise this will create a kind of police state that even makes the world of 1984 look like utopia.
The discovery reinforces earlier discoveries from last year about civilizations that groomed the rainforests and lived in the regions for thousands of years before Columbus arrived (with diseases) that wiped them out.
http://www.livescience.com/516...
So, instead of modernizing or migrating these antiquated systems that have not been updated in more than a decade now it seems, the entire municipality should migrate the operating system again for their sake and leave them in their sorry state? Seems like a pretty pathetic strawman to me.
Even if you do not believe in the negative effects of the use of coal (global warming, pollution, atmospheric radiation, etc.), you still need to keep in mind the fact that there is a finite source of that energy. If we use up all of the fuel now, we will have no energy to build alternative energy sources later.
So, it is in our best interest as a species and a nation to invest in alternative longer-term energy solutions when primary finite sources of energy are cheap and plentiful now.
Yes, let's open up web browsers into becoming a huge security and privacy invasion vector so you don't need to use "native apps" because it's "difficult to change platforms".
/s
Meanwhile, any application developer with half a brain should be making their software in a method that is easily ported to the three major platforms.
But no, we should not expect them to do that. Instead, let's just open the browser up to do everything under the sun and hope nothing goes wrong.
You would lose the wager. Because the files are on my personal AWS account's S3 bucket and can be easily traced back to me by law enforcement if it has anything illegal or harming inside.
I get the joke but the zips are a serious effort to help get the data shared. The original source took almost 6 hours to download fully because did they not compress or compact the files in any way. I'm just trying to save others interested that effort (and their bandwidth budgets for people with caps).
Which is why I want to download it and archive it. If there is a threat that scientific data is going to be attacked and purged, we should all be saving a copy just in case.
Finally done and posted links above, but here they are for your convenience.
GPS+Energetic+Charged+Particle+2016-12-08+63GBs.zip.001
GPS+Energetic+Charged+Particle+2016-12-08+63GBs.zip.002
I downloaded the entire dataset folder and compressed into a two-part ZIP for easy download and/or archiving to DVD.
Files are available on Amazon S3 here:
GPS+Energetic+Charged+Particle+2016-12-08+63GBs.zip.001
GPS+Energetic+Charged+Particle+2016-12-08+63GBs.zip.002
Keep in mind that the total folder is over 63 GBs and 8000 files.
At the rate it's going at the moment, it'll be done somewhere in the next 4 hours.
When, as I mentioned, it could have been done downloading before I even posted the first comment above had they used any form of compression.
But I'll throw in into an S3 bucket after it's all down and compressed for anyone interested.
As I mentioned above, there is no HTTP compression and it's over 8000 files at over 60 GB uncompressed. Had they compressed it, I am certain it would be less than 1 GB based off the tests I mentioned.
Imagine all the bandwidth being wasted. I think it's incredulous to release a huge treasure trove of data this big and not think of compressing.
The website does not seem to be http gzipping the files. I think it's just a pass-through portal page for their FTP.
But gzip would help. Just tested, it brought the files down to 600-700KB from 5-6 MBs.
Still, it's over 8000 files. Could have compressed each directory to a single file and made it easier on everyone.
They present the data as 23 folders with over 100 ASCII at 5 MBs each. Downloading each one by one is annoying but not a show stopper, but why not compress?
I downloaded one of the files and used 7Zip to throw it into a Z archive. The size went from 5 MB down to 500 KB. I uncompressed to make sure it wasn't a fluke but was 100% accurate.
Shouldn't we expect a little more from the country's best and brightest? I mean, come on...
Or how about we just stop rolling out physical lines to individual houses in rural areas and migrate them all over to wireless technologies. Saves tons of money and is far easier to repair and upgrade.
One fiber trunk to each tiny small town and end-mile over wireless. Quick, painless, modern and economical for all parties.
Uh, Apple's earnings show 14 weeks for Q1 2017 and 13 weeks for Q1 2016. They literally said it out loud during the call.
So, no. You are either not paying attention what they are reporting or out-right lying.
Livestream of the conference call from an Apple friendly source if you don't believe me:
http://www.macrumors.com/2017/...
Apple repurchased 3.18% of outstanding shares during 2016, reducing the number of shares in total. The year over year increase in diluted earnings per share was 2.43%. So, number of shares reduced by more than earnings increased. Typically if revenue increased and total shares decreased, the earnings per share would be greater than the percentage of shares removed.
For example, a company that made $100,000 at the end of 2015 has 1000 shares at the beginning of the year for $100 earnings per share. The company purchased 5% of the shares outstanding during 2016 (950 shares outstanding end of year) and also made $100,000 in revenue, putting the earnings per share at around $105 (an increase of 5% year over year).
Now imagine that same company instead had a decline in revenue of 3%, making $97,000, in 2016 instead. With the reduction in shares, the earnings per share for 2016 would be around $102, which is still greater than the year before at $100.
In the case of Apple, to beat the previous year's adjusted earnings per shares they would have needed 3.18% increase in revenue and not the 2.43% reported.
Uh, did you read the article?
The six hours old snapshot was a fluke manual LVM snapshot run, normally they are 24 hours. The SQL_dumps weren't running at all because of mis-configuration, producing tiny little files and failing silently. Webhooks will need to be rolled back to the 24 hour backup since they were removed in the 6 hour one because of a synchronization process (meaning at best 18 hours of updates will have no webhooks but possibly all 24 hours at worst). Lastly, their replication of their backups from Microsoft's Azure to Amazon's S3 for what I assume is vendor agnostic redundancy has sent no files at all ("the bucket is empty").
It's like they thought out everything but never made sure any of it was working.
That explains nothing. Let me lay out the numbers for you.
In Q1 2016, Apple made $75.872 billion in a 13 week period or around $ 5.836 billion a week. In Q1 2017, Apple made $78.361 billion in 14 weeks or $5.597 billion per week. A difference of $2.489 billion year over year or a 4% decline in average weekly revenue.
As far as iPhones, they sold around 3.971 million units a week in 2016 and only 3.884 million units a week in 2017, or a decline of around 2%.
Then there's the quarterly earnings per diluted share which did you need to put in context of the buybacks Apple made during 2016. Apple repurchased 167.567 million shares of 5257.816 million outstanding or around 3.18%. Diluted earnings per share for Q1 2016 was $3.28 and Q1 2017 was $3.36 or a difference of 2.43, showing yet another hidden decline.
All of the fluffy language such as "record setting earnings per share" are all meant to throw you off from the truth. Ghoul's quick numbers seem to pan out across the details in the earnings documents.
Many very important computer-based presentations in my life. Contrary to what you say, the correct thing to do is to make sure you have as stable a platform as possible (and a backup). An unpatched system is not considered stable by any measure of the word. If you are worried about upgrading a computer, you're doing something wrong or not covering your bases properly.
People who hate updates are either running on hardware that have unresolved (or unknown if an incompetent user) issues, no regular backups or too slim a budget (time or money) to do their job properly. Or perhaps all three.
As far as the ad hominen, I'm a highly competent, experienced computer scientist with several decades of experience working in not only critical infrastructure systems but presentations as well.
Making sure your computer is up to date prior to an important event is not a "stupid move". Your same ignorant strawman argument could be used against taking vaccinations before traveling overseas but I doubt you'd risk your life or long term health on such moronic logic.
Regardless of context, you have the choice of doing something now that has a slim chance of going wrong and cause a problem that can be fixed before an important or risky event you know will occur, or ignore the issue and hope nothing will happen later with the chance of having a big problem when it really matters and no time to fix.
Anyone choosing the later is a short-sighted fool that deserves the consequences.
If you read the document, it states it is an update to a document last modified in 2011. Which means we do not know when the policy was put in place unless we look at the 2011 version as well and follow the paper trail.
So, can't exactly blame on Obama. On the other hand, this document was leaked under the Obama administration which could have been intentional. Bare in mind, the FBI's mandate and policies are governed by not just the President but Congress as well (if not more so).
Read the article and you will find the author is a complete idiot. He went to an important event where he needed 100% up-time in a public place that he most doubtfully was on a 3rd party wireless network and he made no effort to make sure his computer was up to date before hand. Anyone even on a Mac or Linux PC would still be wise to update before doing this sort of thing as well.
Sounds like an incompetent twit bitching about his own incompetence being undermined by Microsoft's automated systems trying to keep him secure.
He looked stupid because he is stupid.
Listen, if you're going to lie at least make up a believable number. Studies have shown people believe made up numbers ending in 1 and 7 more than the other eight numbers.
So, if you had said you found 17 medline articles, I might have believed you.
Link to study for confirmation:
http://dilbert.com/strip/2008-...
Please don't exaggerate. No one advocating basic income is asking for that much to be given out.
Basic income is designed to help stop people needing to hold two or even three jobs to survive, not stop people from working entirely.
The most reasonable amounts I have heard are pegged to the poverty level, such as 50-80% of the poverty line income (which is around $12,000 in the USA).
That would equate to $500-800 a month given to everyone over 18, which is around 243 million people or $1.5 trillion every year.
Also keep in mind that in a fiat reserve currency system like the USA, not all of that money needs to come from incoming tax revenues and would most likely increase tax revenues since most of the money being given out is going directly into the economy (and not high level banking instruments that only make the wealthy more powerful).
Pretty sure VLC and other video players can do this as well. I know VLC can apply filters and save out videos, and have seen demonstrations of people applying OpenGL shaders to videos.