I'm guessing they're implementing this after The Huffington Post ran that article months ago confusing the difference between what a "Terms of Service" is compared to "App Permissions" in regards to the Facebook Mobile Messenger. Now any "News" site that talks ill of Facebook will be labeled "SATIRE"! Perfection. This is ingenious marketing on Facebook's part! Now they'll never look bad ever again!
Exactly! Comcast has to pay NBC/Universal (owned by Comcast) money for their content! It all makes perfect sense.
Twitter Bots are GREAT! Seriously, Twitter is the new RSS. This is honestly how I find out about the latest Slashdot articles, because their account is bot based to feed content from this site to their Twitter account. A huge chunk of the accounts I follow on Twitter are in this same category, just news services. Twitter has become the modern day RSS feeder, and I personally love it for this purpose.
Yes, yes it is!
(and yes, this is used in production on mission critical systems)
I can't even begin to count the number of things wrong with their web site which already makes me not trust them...
* Using Flash just to have a "fancy" text label on the home page
* Video where the lighting exposure is off and the audio quality is questionable
* Speech during the video where the guy stumbles on his own words a couple of times
Really, for a company that supposedly "mitigated risk for 7 years on $1.9 trillion of investments" and ran by a supposed tech superstar genius, you'd think they'd at least get the basics of technology and media correct on their own e-penis self-promotion presentation...
So you're telling me that a Final Fantasy 1 sprite on the NES is still exceedingly more detailed than a human being captured using this system? Cool, we're good!
I've got a complaint... The site is slow as shit and buggy as hell. After a long wait, the homepage FINALLY loads. Click on anything, and get a spinning little "loading" thing pop up in the middle of the page, and then nothing happens. After some minutes, and error box popped up in the top-right corner of the page saying there is some technical issues.
OH wait, this is McAfee we're talking about... yeah, shit's gonna suck, forgot.
Something else I've personally noticed, and this is consistent with everyone I've asked about the issue...
"Top Stories" for desktop viewing vs mobile viewing are COMPLETELY DIFFERENT. I have to check FB on both my desktop AND my tablet every day just to get an idea of what going on with my social circle. This is just stupid bad. What is even worse is that there is next to zero intersection between these two separate news feeds from the same account. It is as if Facebook decided to split timelines in half, one set for mobile, the other for desktop.
And this is exactly why I wish Google Fiber was deployed in more areas. They have a simple solution: a FREE tier for life.
And as far as the $300 setup fee, I'm not sure about other cities, but Portland is working on subsidies to cover this cost as well, so it is $0 for low income families to have basic 5mbps internet service.
Get with the times! Switch to Y10K compliance already.
And those who are extremely educated fall into the "don't trust the Internet" group quite easily. How many security exploits do we need before people stop trusting in various internet services? But not trusting it doesn't mean we stop USING it! We simply alter our actions on the internet.
For those not clicking links, this is what T-Mobile had to say about this:
We have seen the complaint filed today by the FTC and find it to be unfounded and without merit. In fact T-Mobile stopped billing for these Premium SMS services last year and launched a proactive program to provide full refunds for any customer that feels that they were charged for something they did not want. T-Mobile is fighting harder than any of the carriers to change the way the wireless industry operates and we are disappointed that the FTC has chosen to file this action against the most pro-consumer company in the industry rather than the real bad actors.
As the Un-carrier, we believe that customers should only pay for what they want and what they sign up for. We exited this business late last year, and announced an aggressive program to take care of customers and we are disappointed that the FTC has instead chosen to file this sensationalized legal action. We are the first to take action for the consumer and I am calling for the entire industry to do the same.
This is about doing what is right for consumers and we put in place procedures to protect our customers from unauthorized charges. Unfortunately, not all of these third party providers acted responsibly—an issue the entire industry faced. We believe those providers should be held accountable, and the FTC’s lawsuit seeking to hold T-Mobile responsible for their acts is not only factually and legally unfounded, but also misdirected.
-- John Legere, CEO of T-Mobile USA
Much in the same way regulations for fuel efficiency are wasted because we have fully electric cars now....
How about we focus on Comcast / NBC / Universal / Time / Warner first?
13 hours ago, Amazon / AWS sent out the following email:
Dear Amazon S3 Customer,
Amazon S3 now supports server side encryption with customer-provided keys (SSE-C), a new encryption option for Amazon S3. When using SSE-C, Amazon S3 encrypts your objects with the custom encryption keys that you provide. Since Amazon S3 performs the encryption for you, you get the benefits of using your encryption keys without the cost of writing or executing your own encryption code.
Until now, in order to use your own encryption keys, you needed to encrypt your data client-side prior to uploading them to Amazon S3. With SSE-C, you now have the option to securely store your data using keys that you manage, without having to build client-side encryption infrastructure.
To use SSE-C, simply include your custom encryption key in your upload request, and Amazon S3 encrypts the object using that key and securely stores the encrypted data at rest. Similarly, to retrieve an encrypted object, provide your custom encryption key, and Amazon S3 decrypts the object as part of the retrieval. Amazon S3 doesn't store your encryption key anywhere; the key is immediately discarded after S3 completes your requests.
You can learn how to use SSE-C today by visiting "Using SSE with Customer-provided Keys" in the Amazon S3 Developer Guide.
The Amazon S3 Team