BTW, I created that animation in Fireworks and saved it as a standard 16×16 animated GIF.

How’s you do that?

Kicks serious booty.

Nice.

Especially the animated .gif icon.
I didn’t know you could do that.

I’ve heard of the favicon.ico bit. I thought that was cool. Is there any particular resource, especially Open Source, that caters to Firefox?

does anyone know?

I use Nvu now, but if I can find somthing better?

My bad. I should have made it clear that I was jesting about SSL being accelerated. While it would be wonderful, I agree that with current encryption methods it is highly unlikely given the key system currently used.

The only reason I let the comment creep in to begin with was that secure connections are doggedly slow over our dial-up connection vs. accelerated surfing - not to mention the benefit of the adblock plugin I just installed in Firefox to further maximize the efficiency and effectiveness of our minimal bandwidth. With Firefox, adblock and acceleration web surfing isn’t as painful as it could be. However, going from that to an SSL session - ouch!

Your point is well taken however. I am interested in your opinion on the original piece and subsequent comments - what is your take on acceleration?

- and hope that we’ll be able to find a way to apply the technology to SSL sessions soon!

There are several problems with this. First and foremost the data would have to be decrypted in the middle of the route to apply the “acceleration.” This would either require both the server and client to supply their private encryption keys to the accelerator or the accelerator would have to break the cipher key which can be done on an almost real time basis but is VERY expensive. With either method major security holes are opened up and for liability reasons I couldn’t imagine an ISP even attempting this.

Another problem is our good old friend the checksum. If the transaction is tampered with in any way the checksum changes and both ends reject it. While it might be possible to use a man-in-the-middle attack knowing all the public and private keys involved in reality this type of attack is very difficult. It would require the accelerator in the middle to pretend to be both ends of the link and completely re-write the SSL transaction. This is not good for security and would almost certainly increase the amount of time it takes to load the page beyond that of unmodified dial-up.

In theory accelerator SSL might sound like a good idea but in reality it opens up a can of worms I suspect no one really wants opened. Just imagine, instead of users giving out their sensitive data to the phishers the phishers would just have to re-route the data from the ISP’s acceleration server to their machine in Russia. This may sound difficult but in a day and age when ISP’s are only about profit it actually happens more often than most people realize.

I have several problems with the rant itself:

1. Misdirected Frustration
Yes, those who use accelerated dial-up yet don’t educate themselves about the process may criticize the website for the altered appearance. How is this different from the infinite other examples of user ignorance that we encounter everyday? For instance, those who fall victim to phishing and e-mail scams, download unsafe software, surf without virus protection and/or firewalls, etc? Many such users may blame the computer manufactures, the operating system programmers, and everyone else except themselves for their difficulties. How is this any different?

2. Images Front and Center? Not Exactly…
Accelerated dial-up doesn’t just accelerate images - in fact, out of everything that *is* accelerated, the images compression accounts for speed increases far less than other compressed data. Acceleration technology works not only via lossy compression (such as that used for images) but with lossless compression (such as that used for text and other data) as well. Watch the acceleration speed for content during an accelerated dial-up session and you’ll see the data/content acceleration in the following order (most to least):

A. Uploaded data streams
B. Text and lossless compression items
C. Graphics
D. Other

3. Compression is One of Three…
C’mon, accelerated dial-up doesn’t just rely on compression - it relies on filtering and caching technologies as well, both on the client and server side. All three methods - compression, filtering and caching - work in concert to use the available bandwidth more effectively.

4. Did You Read the Terms?
Speaking of ignorance-and I use that term in the spirit of lack of knowledge, not as a detrimental insult-this is also another example of consumers using a product or service without taking the time to fully understand it (see item one above). The terms of the service is normally *very* clearly spelled out - for example:

“Web Accelerator uses proprietary compression technology to accelerate certain web page text and graphics when compared to standard dial-up Internet service; however, actual results may vary and actual data transmission rates are not faster than standard dial-up Internet service. You agree and understand that the actual data speeds for downloading certain files, such as music or pictures, will not be faster using Web Accelerator than with standard dial-up service. Some web pages such as secure or encrypted web pages will not be accelerated. Web Accelerator may not be compatible with proxy based software or services such as content filters or firewalls.”

While the writers point is duly noted, I think the real issue is a lack of knowledge, not the service itself. Accelerated dial-up isn’t the perfect solution, but it *is* an option. Until broadband is widely available everywhere and not just in major urban centers, I think the service is a viable, and much welcomed, option indeed.