Facebook updates terms, data policy, and cookies policy

Posted by navaneeth on Nov 26, 2014 in General |

Facebook pushed a rare service notification to users on Tuesday, reminding millions of the social network’s members of updates to its terms, data and cookies policies, advertising systems, and new privacy controls.

The notification says

By using our services after January 1, 2015, you agree to our updated terms, data policy, and cookies policy and to seeing improved ads based on apps and sites you use. Learn more below about these updates and how to control the ads you see.

Here are some highlights:

Discover what’s going on around you: We’re updating our policies to explain how we get location information depending on the features you decide to use. Millions of people check into their favorite places and use optional features like Nearby Friends (currently only available in some regions). We’re working on ways to show you the most relevant information based on where you are and what your friends are up to. For example, in the future, if you decide to share where you are, you might see menus from restaurants nearby or updates from friends in the area.
Make purchases more convenient: In some regions, we’re testing a Buy button that helps people discover and purchase products without leaving Facebook. We’re also working on new ways to make transactions even more convenient.
Find information about privacy on Facebook at the moment you need it: To make them more accessible, we moved tips and suggestions to Privacy Basics. Our data policy is shorter and clearer, making it easier to read.
Understand how we use the information we receive: For example, understanding battery and signal strength helps make sure our apps work well on your device. We ask for permission to use your phone’s location when we offer optional features like check-ins or adding your location to posts.
Get to know how the family of Facebook companies and apps work together: Over the past few years, Facebook has grown and we want to make sure you know about our family of companies, apps and services. We use the information we collect to improve your experience. For example, if you’re locked out of your Instagram account, you can use your Facebook information to recover your password. Nothing in our updates changes the commitments that Instagram, WhatsApp and other companies have made to protect your information and your privacy.
Your information and advertising: People sometimes ask how their information is shared with advertisers. Nothing is changing with these updates—we help advertisers reach people with relevant ads without telling them who you are. Learn more about ads and how you can control the ads you see.

Remote Server Transfer using php

Posted by navaneeth on Nov 24, 2014 in Php |

In this tutorial I am going to explain how to transfer large files from one server to another without any time lag.

It is a hell job to download and then upload files while at the time of server transfer.In this we can use an alternative called remote upload.

Most of the servers support remote upload.But in some hosting providers like silliconhouse.net doesn’t support remote file transfer.If it is not supporting the server transfer will be a hell job.

Here is the code for Remote Upload files using Php:

<?php
define('BUFSIZ', 4095);
$url = 'http://www.navaneeth.me/alexa-top-ranks.csv.zip';
$rfile = fopen($url, 'r');
$lfile = fopen(basename($url), 'w');
while(!feof($rfile))
fwrite($lfile, fread($rfile, BUFSIZ), BUFSIZ);
fclose($rfile);
fclose($lfile);
?>

Step 1: First you need to create a file called upload.php where you want to upload the files.
Paste the above code in that file.

Step 2: Replace the url with your url required to be remotely upload.

Step 3 : Run the file upload.php and it will automatically copy your requested files in a fraction of second.

Hope this is helpful for you.
Enjoy the Remote Uploading using php.

Magento Go is Shutting Down

Posted by navaneeth on Nov 19, 2014 in Magento |

E-commerce platform Magento, owned by eBay’s Enterprise division, is closing down two of its products designed to reach small to medium-sized online retailers: Magento Go and ProStores. The company has posted notices and informational guides on both product websites, directing current customers to “Migration Center” dashboards and various FAQ’s that will help them move their businesses to other platforms. Combined, the two products include around 10,000 merchants.

This is what eBay Enterprise Says

We’ve made the difficult decision to shut down Magento Go on February 1, 2015. Your store will not be affected during the Holiday shopping season – it will continue to operate and perform normally, and Magento will continue to provide customer service until February 1, 2015.

Over the past five years we’ve had the opportunity to work with thousands of merchants and have been humbled to be a part of so many success stories. Going forward, we’re focusing our resources on Magento Enterprise Edition and Magento Community Edition, two solutions that better support and better equip small and medium size merchants to prosper in the evolving and increasingly competitive eCommerce landscape.

Please be sure to take advantage of the checklists, planning resources and special offers found in the Migration Center to help smooth your transition to a new eCommerce solution.

PayPal Users Must Discontinue Using SSL 3.0

Posted by navaneeth on Nov 13, 2014 in General, Payment Methods |

PayPal Users Must Discontinue Using SSL 3.0 By December 3, 2014

To address a vulnerability with the SSL 3.0 security protocol, PayPal and other payment gateways will be disabling SSL 3.0 support. Merchants must upgrade to Transport Layer Service (TLS) by December 3, 2014 to avoid PayPal payment operation failures.

Recently a vulnerability was published that affects a particular version of the Secure Sockets Layer (SSL) protocol, which is used to secure connections to websites. The vulnerability, which only exists in SSL 3.0, allows a cyber criminal to gain access to connections previously assumed secure. Fortunately, SSL 3.0 is not the only option available to secure these connections, and this vulnerability can be prevented by disabling support for SSL 3.0. PayPal will completely disable SSL 3.0 support, which will prevent this vulnerability from impacting users of PayPal, including those who may be using an integration via a merchant’s site.

Whilst disabling this protects users from harm, it may result in compatibility issues for some customers, particularly those merchant sites that rely on SSL 3.0. No need to worry though, updating your integration to be secure and compatible is quick and easy.

Ensuring you are secure is a simple process. If you are currently using SSL 3.0, update to use TLS, a more recent standard than SSL that provides a secure connection. Once you have done so, consider issuing new API credentials; this may not be necessary, but is recommended for security purposes.

If you are unsure whether you are using SSL 3.0 all you need to do is test your integration against the Sandbox. If you can make an API request, you are not using SSL 3.0, as this has already been disabled on the PayPal Sandbox, and you will experience no compatibility or security issues. If you are unsure how to test your integration against the Sandbox, please refer to the Merchant Response Guide for more details.

Read more at Poodle SSL 3.0 Vulnerability

For additional information about the POODLE vulnerability and PayPal’s response, please see this blog post from PayPal CTO, James Barrese.

Author Archives: navaneeth