This seems like a pretty brain-dead limit, since 10MB is not a lot of data and they’re hyping up 3G so much as being as fast as broadband. Well, what’s the use if you’re artificially disallowed from downloadling more than 10MB?

Chalk one up for the bean counters at AT&T who no doubt convinced Apple to include this “feature”.

http://www.google.com/url?sa=U&start=1&q=http://www.mozilla.org/&usg=AFQjCNGjMwD4PF4GezESBBRN2It3HBj5Qg

I suspect that the usg parameter is probably one used to prevent bots from gaming whatever results they’re trying to garner, and possibly also to link clicked search results to a specific user or browser session. I understand why they do this, but the downside for the end user is that the copy link option in the context menu of any browser is no longer useful. One needs to actually follow the link to get the URL in a form that you can copy into another application.

From my perspective, this is a pretty major usability bug, and I hope they revert it.

Clearing the cookies and cache doesn’t help. When I log in via IE7, it works fine. This problem started to happen after the upgrade to Firefox 3.

Personally, my favourite new feature is the AwesomeBar. What’s yours?

Issue #1 - Google Groups Atom Feed id and link attribute broken

I’ve detailed this issue more in my post to the Is Something Broken forum on the Google Groups website, but so far there’s no resolution. Basically the Atom feeds generated by Google Groups generate a id and link attribute that contains a relative link without an FQDN so that when viewed from an RSS reader, the links are broken because the RSS reader passes a URL without an FQDN to the web browser. I hope this gets fixed as it seems like a pretty major problem.

When viewed from Firefox’s Live Bookmarks it works fine, but not otherwise.

The RSS 2.0 feed generated by Google Groups does have an FQDN in the link attribute so it works properly. The “obvious” solution (other than fixing the issue, which is up to Google) is to use the RSS 2.0 feed instead of the Atom feed but that creates another problem.

UPDATE (18/06/2008): As of today, Google seems to have fixed the issue with the Atom feeds.

Issue #2 - FeedDemon 2.7 does not handle the pubDate in the RSS 2.0 feeds correctly

The pubDates in the RSS 2.0 feed seem to be generated correctly, like the following:

<pubDate>Fri, 06 Jun 2008 00:02:27 UT</pubDate>

When the RSS 2.0 feed is added to FeedDemon in synced mode (where it syncs with the Newsgator servers), it seems to ignore the pubDate and pick some arbitrary date for all the entries, and all the entries share this same date.

When the RSS 2.0 feed is added in non-synced mode (where FeedDemon pulls from the feed server directly), all the pubDates are respected and it works properly. In Firefox Live Bookmarks it works properly too.

With the Atom 1.0 feed from Google, the dates are correct in all cases but the links are broken. But at the moment users are in a quandry as there appear to be problems in both Google’s feed implementation and FeedDemon’s parsing of Google’s feeds.

UPDATE (08/06/2008): Nick Bradbury, the creator of FeedDemon has been able to reproduce the bug and has added it to the FeedDemon bug tracking database.

Network infection via guests is a real vector and one of which companies should be very afraid. Ideally guests would always be on a separate VLAN.

One way to acheive this is to use a FON router to sandbox guests into a separate VLAN. The FON routers have two SSIDs, a private one that is WPA2 protected that gives full access to the local network, and a public SSID that is (by default) completely separate from the main network and guests on this VLAN cannot talk to computers on the main network, only through to internet IP addresses.

Using the friends and family feature of FON, you can set up a custom username and password that your office guests can use to authenticate on the public SSID (multiple logins with a single credential is possible).

This kills two birds with one stone because you not only have secure access to your own network via WPA2 (which is generally considered to be unbreakable using today’s technology) and you offer guests wifi access to the internet without allowing them access to your internal network.

A couple of things are on my FON wishlist:

• Seamless handover between FON access points on both public and private SSID
• Proper resolution of NetBIOS names on the private SSID (even though its on a different subnet from the main network)
• Better tolerance for old network drivers (this is a big one because in quite a few cases clients using older drivers could not connect to FON even though they could use other wifi networks - older Intel drivers in particular seem to be a problem)
• More powerful customisation options for the FON portal
• On the La Fonera+, allow the extra wired ethernet port to optionally connect to the public FON network instead of the private network

One other thing to bear in mind is that if you choose this solution, you allow anybody to use your bandwidth when authenticated through the FON network. Depending on your corporate policies, this may or may not be a problem for you. If bandwidth is the only issue, on the public SSID you can optionally limit this to as little as 512Kbps to make sure that guests don’t hog your pipeline.

A couple of comments later, people pointed out that the problem is really Dell’s rather than Microsoft’s because Dell hadn’t bothered to release a driver update in years despite ATI continually updating their reference drivers. What’s worse, Dell has a deal with ATI where Dell users can’t download drivers directly from the ATI website. So users are supposedly stuck with the broken old Dell drivers that Dell couldn’t be bothered to update.

I did some researching on the Dell forums and found two entries that gave me the correct information so that I could find drivers that worked with SP3, even though they were unsupported by Dell. There is a “hidden” link on the ATI website that allows you to download the drivers for Mobility Radeon series bypassing the compatibility check that usually stops Dell users from accessing the drivers:

http://www.ati.com/online/mobilecatalyst/

After I got the drivers from this site, everything worked like a charm and I was able to use my video card rotation function correctly with SP3. One small gotcha regarding the latest ATI drivers is that you must have the Microsoft .NET Framework Version 2.0 installed in order to use them.

All of this would have been a lot simpler if Dell just kept their drivers up to date! I have a Dell Latitude D610, which is widely deployed at enterprises worldwide. It’s surprising that their enterprise customers haven’t made a bigger fuss about this.