Archive for the ‘Internet!’ Category


A year back, Gmail started letting users drop images from their desktop right into the compose window.

“Now, when you are running the latest version of Google Chrome, you can paste images right from your clipboard too,” Google announced.

“So if you copy an image from the web or another email, you can paste it right into your message. This is especially handy for passing around screenshots — you don’t have to save the files any more (I have been using Ctrl-C on my windows to save screenshots directly to the clipboard). While this currently only works in Chrome, we hope to enable it on other browsers soon,” Google added.

Facebook now enabled IPv6

Posted: June 8, 2011 in Internet!, News

Facebook’s Donn Lee has been getting the social network ready for this first worldwide test flight of IPv6 since last fall when plans for the June 8 event were put in place. Wednesday is the day that the giants of the InternetGoogle, Yahoo, Microsoft, Verizon and Facebook – will give IPv6 a whirl and see how it works.

Lee, who came up with the idea for World IPv6 Day with Google network engineer Lorenzo Colitti, said he’s confident all will go well and he’s not expecting any surprises.

“I’m completely excited,” Lee told Computerworld. “It’s grown into a life of its own from our initial idea that we had in the hallways of a conference last summer. Seeing all the excitement and energy around this day is immensely rewarding. This is when the Internet enters into the next stage of its expansion.”

IPv4 is the Internet’s main communications protocol, but it is quickly running out of unique IP addresses for all the computers, smartphones and other devices that need to be hooked up to the Internet. Hence, the development of an upgrade — IPv6, which is said to provide more than 4 billion times more addresses than IPv4.

Some people worry that migrating to IPv6 will be time consuming and expensive. World IPv6 Day is designed to test IPv6 and see how well it works. Internet users on Wednesday can think of themselves as test pilots.

Participating companies will flip the switch at 8 p.m. EDT Tuesday.

“This is going to be like opening night,” Lee said. “It’s a 24-hour test. We’ll turn it off after 24 hours. Most participants will… We think we’ve covered all our bases.”

He added that the participants have been going through “dress rehearsals” and he’s confident that most Facebook users won’t see any difference in the site’s performance Wednesday.

“We’ve already done some very comprehensive tests and simulations here and we have not had any effects to Facebook users,” Lee said. “We’ve tested users to see what their IPv6 and IPV4 connectivity is. We’ve been collecting data for many months. We pretty sure that our data is sound.”

Lee, who previously worked at Google and Cisco Systems, said a handful of Facebook engineers have been working on updating the company’s network so they can run a dual stack, which means running both IPv4 and IPv6 at the same time.

The site will check a user’s system and if it supports IPv6, it will use IPv6 for the first time. Most people don’t have IPv6 and will fall back to IPV4.

Lee figures that 0.2% of Facebook’s more than 500 million users are capable of using IPv6 at home or at work. That’s 1 million users.

He also contends that 99.97% of users will see no difference whatsoever. The other 0.03% can probably expect some slowdowns because of bugs either in their own systems or on the larger networks.

For Facebook, getting ready for Wednesday’s test has been in the works for months.

Lee said most of their efforts were focused on the company’s software, specifically, making code changes. “Most of our costs were having software engineers go through our code,” he added. “Where it expected a legacy address to now expect and support an IPv6 address.”

He said he didn’t know how much the migration cost Facebook.

The Internet is our business,” Lee added. “As far as we can tell, the future of the Internet is important not just to us but to all Internet companies. There aren’t really good solutions when you run out of addresses. I believe that IPv6 is the answer to the future of the Internet.”

Via [facebook]

today they rolled out a long-awaited feature: automatic link shortening. Now, whenever you type a link into the Twitter webapp, it will shorten anything over 11 characters using their service. What’s really great is that your original link (or a truncated version of it) will still show up in tweets, so people still know where they’re going (and don’t have to worry about phishing attacks). Sadly, if you want to use anything other than (like, which provides statistics and other features), you’ll still have to shorten links from that service’s home page. Still, if you still use the Twitter webapp instead of a dedicated client, this is a huge convenience. Note that the feature still seems to be rolling out, and you might not see it on your account just yet—but you should soon.

[via Twitter Blog]

The most observant of you surely remember the words of Steve Jobs when, about a year ago, presented FaceTime, the new service from Apple that make video calls from the device IOS, at first only fourth-generation iPhone. With a little ‘amazement, it turned out, indeed it was the same Steve Jobs to announce that FaceTime would have been a feature WiFi only “throughout 2010. At the end of the fifth month of 2011, one wonders if the new iOS 5 things will change.

Certainly almost no one expected that FaceTime also on the 3G network could be introduced without a major upgrade of IOS, which could then update to match its new5.0 firmware that Apple will be presented June 6 on the stage of the Moscone Center during the Keynote d ‘ opening of the WWDC 2011.

Could FaceTime on 3G as one of five new IOS? Very likely. Technically, Apple could implement this function from the beginning. However, to ensure that users always have as an efficient and precise, he preferred to wait and launch FaceTime only WiFi to test primarily the use by users and also to assess the prevalence (FaceTime could initially be used only between 4 iPhone , then also on your Mac, iPod touch and fourth-generation iPad 2), which was limited by its need to be connected to a WiFi network for video calls another contact.

Apple has nevertheless proved to be very careful with regard to this technologyhas been improved with every new iPhone firmware update, both internally and through integration with other applications on Mac and implementing the new cam in HD on newer models models . Precisely for this reason, given also the good results obtained by FaceTime on 3G iPhone on jailbroken (thanks to programs such as 3G Unrestrictor available via Cydia), there would be no surprise that in 2011, just 5 with IOS, Apple will allow users to FaceTime is used in WiFi on 3G.

If this happens, Apple users could hypothetically video calls to each other completely free of charge. However, it remains to understand what might be the response of the Italian telephone operators faced with a similar solution that both recalls the VoIP, certainly not loved by some, and what the actual traffic flow data users.

Recalling the words of Steve Jobs ” FaceTime will only work on WiFi for 2010 “we are quite confident that Apple can implement iOS 5 video in the long-awaited 3G iPhone and iPad 2.

Given the fact that Google Chrome share is continuing to grow a lot, you may wonder about the reasoning for this article title. The fact that Chrome is continuing to get more popular for Web browsing, it does not mean that when Web developers are working on their projects they still use Chrome.

For me that is not the case. Often when I am doing Web development work, I feel the need to switch to Firefox for the reasons that I am listing below.

Keeping in mind that this article is not exactly a rant against Google. Google gaves us, Web developers, a lot to be thankful to them, but when comes to Chrome there is still a lot to desire.

I decided to write this post now in the hope that maybe somebody at Google reads it and does something to address these issues that more than often really upsets many of us, as we do not want to be switching browsers all the time.

1. HTML viewing

When the code of our sites has bugs, often it generates HTML code that is incorrect or even invalid. So we need to examine the HTML code to help figuring what is wrong.

Firefox has this awesome feature that lets you select a portion of a page and it shows the exact HTML that corresponds to selected page portion. There is no such feature in Chrome.

The best you have is an Inspect Element feature that lets you find the HTML code for the page element under your mouse pointer. It is not the same thing. If I selected a region of the page, I would like to view the whole region HTML, not just a single element.

Another annoyance is that Chrome tries to beautify the HTML code. This means that if you have malformed HTML, you will not see where it is malformed, as Chrome will show you a beautified version of the HTML code after have been already fixed. I wish there was an option to disable beautification.

2. HTML Validation

Another great feature of Firefox is the possibility to show you any HTML validation errors that you may have. Actually, this is a feature provided by the HTML Validator extension.

I tried several extensions for the same purpose in Chrome but nothing was nearly as good. Some only used the W3C validation service passing the page URL, which is not good because when you are developing a non-public page, the W3C service cannot access it, neither can access it as an eventually logged user of the site you are developing.

Other extensions tried to copy the currently loaded page and pass it to the validator service but none showed the eventually invalid HTML as the Firefox HTML Validator extension does.

Also this Firefox extension does not rely on an external validation service. This means that you can validate your pages even if you currently do not have Internet Access.

So, for all these reasons, an equivalent version of Firefox HTML Validator extension is seriously needed for Chrome.

3. Disable JavaScript

Sometimes you need to test your site with JavaScript disabled. The only way to disable it in Chrome is going to preferences and disable it there. This is a real drag.

In Firefox you can use the Web Developer extension by Chris Pederick to add a button to the browser toolbar to quickly disable and re-enable JavaScript any time you want.

For Chrome there is also the Web Developer extension by the same developer but it does not provide a means to disable JavaScript.

The problem is due to a limitation of the Chrome API exposed to extensions. It does not provide a way to disable JavaScript from extensions.

There is a feature request for the Chromium project to implement the necessary support to disable JavaScript. The feature implementation was even assigned about 1 year ago to be implemented, but it never happened. Oddly users were disallowed to post further comments to that feature request.

4. Empty the browser cache

Sometimes you need to force the cache of the browser to be emptied, so fresh content is retrieved from the server of the site you are developing.

It is the same limitation as of disabling JavaScript. You cannot do it from an extension. You need to do it by going to the Chrome preferences.

There is also a feature request to enable support to empty the browser cache from an extension. This one was requested more than 2 years ago, but only 3 months ago it was assigned to be implemented.

5. Switching the browser user agent identification

Sometimes you need to access your site in development pretending to be using a different browser, so you can check if your site adapts to the current browser as you expect.

For instance, if you are serving an RSS feed to be handled by Feedburner, you need to redirect all browsers to the Feedburner feed URL, unless the current user agent is Feedburner itself checking if your feed was updated. So, it would be useful if you could make the browser pretend to be Feedburner, so you can check if it is working well as needed.

In Firefox you can use the User Agent Switcher extension also by Chris Pederick. In Chrome there is also an extension named User Agent Switcher. The problem is that it does not work. Well it does, but not in the way you expect.

This extension can only change the browser identification exposed to JavaScript. This means that the HTTP requests sent to the server will not use the user agent identification string that you need to be sent.

I suspect there is a feature request to have this implemented in the Chromium, but I did not find it. Until that feature is implemented, we have always to resort to Firefox which works well as necessary with the User Agent Switcher extension.

6. Buttons in the status bar

One good thing about Firefox and most other browsers is that you can have useful buttons below in the browser window in the status bar. That is were the Firebug and other useful extension buttons appear. When you want to use them, it is very easy to click a button to open Firebug and debug your JavaScript code.

Chrome practically eliminated the status bar. It is only used to show some temporary messages. If you want to open the developer tools to debug your JavaScript code or check the page HTML, you need either to find that function in the menus or memorize a non-trivial key sequence.

Eventually you will get used to this but it would be much more user-friendly if you could reach those extensions if they appeared in the status bar below or even at the browser window top.

7. Caching of posted pages in the browser history

Sometimes you need to go back in your browser history to a page that was presented after submitting a form using the POST method. However, you do not want to repeat the request that was sent to the server when that page was served.

In some cases, which I could not determine the exact circumstances, Chrome asks if I want to post the form again and does not show me the page in the browser history if I do not accept to post the form again. Firefox does not have this problem. It always shows me the page in the browser history, even if it was the result of a posted form.

8. The Flash extension crashes frequently

I do not develop sites in Flash. However, sometimes I need to access certain Google sites that provide useful information presented using Flash. That is the case of Google Analytics and Google Webmaster Tools.

Unfortunately, the Flash extension shipped with Chrome crashes frequently. That does not happen when using Firefox to access the exact same pages.

I would prefer that Google did not use Flash in such sites. Most of what they present did not really need to use Flash. I assume that changing such sites to not rely on Flash would take Google more development resources than they want to spend. In that case, it is necessary that Google fixes Flash extension that ships with Chrome.

9. HTML editing generates malformed HTML

Nowadays, most sites that publish HTML content submitted by the users, provide a rich text WYSIWYG editor interface. This is done setting the contenteditable HTML attribute, for instance of a div tag.

The problem is that HTML editors in Chrome are still quite buggy. Often if you copy and paste HTML in an editor results in malformed HTML.

I have seen HTML meta tags appearing out of nowhere in the middle of HTML pasted after being copied from other parts of the same HTML document being edited. I also often see bogus CSS styles named Apple-style-span appearing in pasted HTML, when such styles never existed before in the HTML being edited.

This is just a reminder that you need to have an HTML validator and filtering system on your server side scripts to clean-up any messy HTML submitted to the served after being edited on Chrome.

It is always a good idea to use such filters, as there is no guarantee that all browsers will always submit valid HTML. But the fact is that if you use Firefox you do not seem to get such malformed HTML.

10. No feedback to bug reports

I tried to report some of the problems above using Chrome built-in bug reporting system. You go on the menu Tools and then Report an Issue, and it shows a nice bug report page which may even include a screenshot of the current page you were browsing.

The problem is that I never got any feedback of my bug reports. So I do not know if the bugs were submitted and received properly, let alone having been seen and acted upon.

I do know if the time I spent trying to describe the bug reports was worth it. I suspect that it would probably be more efficient if I reported any bugs to the Chromium project directly.

Maybe I am getting this wrong, but sometimes I get the feeling that Google people does not see the act of providing feedback to the user community as an important thing.

This reminded me about the AppEngine issue of supporting PHP. It was the most requested feature for the AppEngine project. Google people decided to not support PHP in any sense, giving as justification the lack of resources. That is a bit odd thing to say for a company that makes many billion dollars in profits every year.

They also disallowed anybody from posting any further comments to that feature request. It seems that it is not relevant for Google what the PHP developers community can provide of feedback, despite it is probably the largest Web developers community.


This article is mostly my opinion and does not necessarily represent what most PHP and other Web developers think of how of Google should sort the priorities of development of Chrome and other Google products.

It is possible that I may have misunderstood certain aspects of how Chrome can work to address Web developer needs. Whether you agree or disagree with my opinions or you have other suggestions to solve the problems presented above, please feel free to post a comment telling what you think about it.

There is a new scam going on on Facebook right now, which involves you, your friends, and the yet to be released iPhone 5. Here is how it works. You see in your stream that one of your friends commented on an article titled “First Exposure: Apple iPhone 5.” Because your friend commented on it and because you really want to know about this iPhone 5, you click on the link as well.

You are then directed to a domain ending in .info (that should be a bad sign in itself), where you are asked to enter a captcha code to prove you are human. That should really be a second warning that this is not so legit…

After verifying that you aren’t a bot, a message is posted directly to your wall, notifying your friends that you have commented on the story. Your friends may or may not fall for it like you did. In the meanwhile, you are asked to fill out a survey to win some crappy prizes.

This technique is known as clickjacking. Although not as dangerous as a virus or spyware, it still acts on your behalf without your consent.

So really, watch out for what you click on. Sometimes a little good sense can go a long way.


Firefox 4 RC is out!

Posted: March 11, 2011 in News
Tags: ,
Mozilla Firefox word mark. Guestimated clear s...

Image via Wikipedia




The wait is over … Firefox 4 Release Candidate (RC) is available for download for Windows, Mac and Linux.




Here’s the official announcement:

Mozilla Firefox 4 for Windows, Mac and Linux has exited the beta cycle and is now available as a release candidate in more than 70 languages. The millions of users testing Firefox 4 will be automatically updated to this version and will join our Mozilla QA team in validating the new features, enhanced performance and stability and HTML5 capabilities in Firefox 4. Testers are encouraged to check out the Web O’ Wonder in order to see the future of the Web with cutting edge demos that showcase the incredible online experiences developers can now create and users can experience. Developers can submit their own demos to the Mozilla Developer Network Demo Studio.

The important stuff from the release notes:

This Firefox 4 RC is considered to be stable and safe to use for daily web browsing, though the features and content may change before the final product release. At this time many Add-ons may not yet have been tested by their authors to ensure that they are compatible with this release. If you wish to help test Add-on compatibility, please install the Add-on Compatibility Reporter – your favorite Add-on author will appreciate it!

Download available here.

Release notes here.

Changelist here.

Inernet Explorer 9 RC (Release Candidate) was released on 10th February, now Microsoft is ready to release the final version RTM of Internet Explorer 9 on 14th March at the SXSW conference.

Microsoft has alre

Internet Explorer 9

Image via Wikipedia

ady said that Internet Explorer 9 RC will automatically update to the Final version of IE9 (internet Explorer 9). But now it’s unsure whether Microsoft will provide this update on 14th March at the SXSW conference or if we’ll have to wait for the next Patch Tuesday. In either case direct download should be available around 9pm on 14th March.

On the other hand Microsoft Developer Network India, has tweeted that final Version of Internet Explorer 9 RTM will release on 24th March at Tech.Ed in India.
Microsoft might launch Internet Explorer 9 on 14th march and may officially launch it in India on 24th March. So Internet Explorer 9 Final version RTM is expected to release on 14th March, but is confirmed for Release on 24th March.

HTC will unveil two new Facebook branded mobile phones next month, City A.M. has learned.

The Taiwanese manufacturer will launch an official tie-up with Mark Zuckerberg’s $50bn (£31.6bn) social network at the Mobile World Congress event in Barcelona.

The high-end smartphones will be the first to bear the Facebook branding and colours. It could look similar to the mock-up pictured right, also created by HTC.

It is understood the phones will run on a tweaked version of Google’s Android operating system and will prominently display users’ Facebook messages and news feed on the home screen.

Other areas of integration expected include being able to call or email friends from information stored on their Facebook page.

Facebook has aggressively pushed mobile versions of its social network and industry insiders see this as an attempt to consolidate its position as the world’s leading social network.

Facebook’s Joe Hewitt (who worked on the Firefox web browser) and Matthew Papakipos (a leading member of the Google Chrome browser team) are thought to be behind the launch.

Google has just added the ability to drag-and-drop images from the desktop into a Google Docs document.

The new feature works with the latest versions of Google Chrome , Firefox and Safari, and Google says it plans to add support for other browsers soon. The feature works exactly as you would expect. Rather than importing an image using the web uploader, entering in a URL or doing a Google Image Search, you just drag the item from your desktop into your Google Docs document.

Drag-and-drop uploading is actually a pretty big win for a web app like Google Docs. Competitor Zoho supports drag-and-drop for some of its apps, but dragging an image into a Zoho Writer file just ends up inserting a local file address into the document.

The process works pretty well and we had no problem taking images from our Mac desktop and putting them in a Google Doc using both Safari 5.0.2 and the latest release of Google Chrome.