PaulSpoerry.com

Windows 7’s user interface overhaul, there’s is a lot of hype about this right now. We know what’s going to change, we know what it looks like, but there’s one important question that has not really been given much stage time: why? At PDC, one session was dedicated to just that question. Speaking was Chaitanya Sareen, part of the windows user interface team. He placed the changes in Windows 7 into context, talked about Windows’ user interface history, and explained why certain changes were made. An interesting insight into the goals of the Windows 7 interface.

Watch the video here.

The new Digsby is here!  We just released Build 32 (r17926) which is the culmination of a massive effort to improve performance, improve connectivity, fix most of the remaining bugs, and add some new functionality to boot. Major changes in this release include:

• RAM Usage: We optimized from the ground up and fixed memory leaks to lower RAM usage by almost 75%.  This has been the number one complaint since our launch and we are proud to introduce this massive improvement.
• Performance: User interface elements draw twice as fast for better performance. We have made changes to the architecture that will improve GUI responsiveness and CPU utilization across the board.
• Connectivity: Every IM protocol automatically tries multiple connection methods and ports to improve the odds of getting through restrictive firewalls and proxy servers.
• LinkedIn: Digsby now supports LinkedIn in addition to the other social networks.  Functionality includes a full newsfeed, alerts when new messages arrive, and the ability to set status right from Digsby.
• Bug Fixes: We have fixed hundreds of bugs, making Digsby more stable than ever.  There have been almost 3,000 revisions in our codebase since the last release so there are too many fixes to list in our changelog.

Digsby
Build 32 – Better than Ever! [Digsby Blog]

Image via Wikipedia

Yup, the blogosphere is on fire with concerns over privacy, the EULA, what information Google will/can collect when you use their new Chrome browser, etc (ok it’s also on fire over the release of this thing in general).

Matt Cutts who is a software engineer at Google and currently the head of Google’s Webspam team wrote up a great article detailing questions about privacy and how/when Google Chrome communicates with google.com. Should you be concerned?

The short answer is no. For the long answer, read on.

To read the detailed list visit Matt’s site for his article Preventing paranoia: when does Google Chrome talk to Google.com? For the shorter list, read on:

• If you’re just surfing around the web and clicking on links, that information does not go to google.com.

• If you are typing a search or url in the address bar, Google Chrome will talk to the current search service to try to offer useful query/url suggestions.

• By default, crash reports and other anonymous usage statistics (e.g. which features are used most often) are not sent to Google.

• I believe if Google Chrome sees a very short, stock 404 page (less than 512 bytes), it talks to Google in order to try to suggest other possible pages and options.

• Google Chrome checks for automatic updates every 25 hours.

• Every 30 minutes, Google Chrome downloads a list of 32-bit url hashes of urls thought to be dangerous (malware or phishing). That is a download of data from google.com, not to google.com.
• When you choose your language in the user interface, Google Chrome downloads a spellcheck dictionary. Again, that is a download of data from google.com, not to google.com.

In short it doesn’t appear the is much to worry about and the conspiracy theorists are just freakin out. Not that the almighty Google doesn’t already have enough power and we shouldn’t ever be concerned. However, it appears the initial freak out by those on the net are just inflated conspiracy worries. Another bonus of this browser is that it’ll be open-sourced so any fears can be double checked by reviewing the source code.

Again, this is just the summary, check out Matt’s post for the full low down and more detailed information for each item.

Google announced it will release a brand new open source web browser called Google Chrome. Yesterday a site went up, and has subsequently been taken down at http://gears.google.com/chrome/?hl=en (as of this morning clicking this link take you back to regular old Google).

According to Crunchbase the features include:

• Tabbed browsing where each tab gets its own process, leading to faster and more stable browsing. If one tab crashes, the whole browser doesn’t go down with it
• A distinct user interface that places tabs on top of the browser window instead of right below the address bar
• An “incognito” mode that lets you browse the web in complete privacy because it doesn’t record any of your activity
• A new JavaScript engine built from the ground up for speed
• Malware and phishing lists that automatically update themselves and warn you of bad websites
• A default homepage that displays your most commonly used sites and other personalized information

Read the rest of this entry »

If you use AJAX already for your Web 2.0 projects or are just thinking about it and need information, check out this one-stop source of AJAX plug-ins. In addition to free code that covers things from fish-eye effects for icon browsing to auto completion text fields Ajaxdaddy shows you the code, and gives you a sandbox area to get a feel for how the widget performs and to do some experimentation.

Read the rest of this entry »