Category: Tech

Posted on
by

Now that it’s live, I’ve downloaded the Google Chrome beta on my Windows box at work.  Thoughts so far:

Good:

  • Site compatibility seems to be fine so far, with a couple of minor issues (see the “Bad” section).  Mostly I’ve tested it with a couple of forum sites, LiveJournal, Slashdot, and WordPress.
  • I like the simple settings box, with “Basics,” “Minor Tweaks,” and “Under the Hood.”
  • It does feel fast.
  • Showing the URL of links in the lower left-hand corner is a perfect compromise between the spatial advantages of a permanent status bar and the extra room provided by leaving it out.
  • I like the task manager for the browser itself.  It’ll be good for developers, but it’ll also be good for users: as the comic points out, if your browser starts chewing up all available resources, you’ll be able to tell what page/plugin/program is at fault instead of just blaming the browser.

Bad:

  • Gears support doesn’t seem to work quite right.  WordPress.com doesn’t detect that it’s available.  Local WP installs with Bad Behavior can’t sync completely.  (It doesn’t send an Accept header on the request for one of the TinyMCE files, which causes Bad Bahavior to think it’s a spambot and triggers a 403.)
  • Cookie management is too simplistic.  I like to accept all cookies temporarily, but clear everything when I end my browsing session, with exceptions for sites where I want to stay logged in.  This is easy in Firefox, a little trickier in Opera, and doesn’t seem to be an option in Chrome.
  • I have seen it pause a couple of times, with as few as 5 tabs. [edit: these seem to be related to Flash content]
  • No Incomplete spell-check.
  • I keep hitting the forward-slash key to search within a page, since that’s the shortcut I’m used to in Firefox and Opera.
Debatable:
  • The UI does indeed stay out of your way.  I guess this sort of makes Chrome the Anti-Flock.
  • DNS Pre-Fetching is enabled by default.  This is different from full HTTP pre-fetching in that all it does it look up the IP addresses of the links that you might click on.  It’s not clear at what point it does this — I don’t remember seeing it mentioned in the comic, which (ironically) isn’t searchable.  I suppose it could either hit the domains of all the links on a page, or just those that would trigger HTTP pre-fetching, or even just send the query when you hover over a link (to get a split-second head start before you click). Update Sep. 17: Google has a blog post explaining pre-resolving in detail. Apparently it does check the domains for all the links on the current page.

Posted on
by

Google Chrome seems to be a multi-threaded open-source browser based on WebKit (with some code from Firefox as well), focusing on making a browser that will work well with web applications.

It’s got built-in support for the Gears API (not surprising). And, like Firefox 3, IE8, and Opera 9.5, it’ll do full-history search & auto-suggest in the location bar. Interestingly, they’ve adopted a couple of UI elements from Opera, including thumbnails of your most-visited pages when opening a new tab (like Opera’s Speed Dial, though in this case the list is automatically generated from your browsing behavior), and putting the tabs above the main toolbar — something that Opera has taken a lot of flack for.

According to the blog post, the first preview release should be out for Windows tomorrow, with Linux and Mac following.

Oddly enough, I found out about it through comics blogs (A Distant Soil, specifically), not tech blogs, because Google hired Scott McCloud (Understanding Comics) to explain what makes the browser different in comic-book form.

Posted on
by

A word to the wise for anyone planning to set up paperless billing: make sure the notices go to the right email address.

Last night, while paying bills, I realized I hadn’t seen a bill for our internet access in quite a while, and noticed that my bank showed the last payment had been sent in June. That didn’t look promising.

I logged onto the U-Verse website, and sure enough, our account was set for paperless billing. I hadn’t gotten the bills because they were being sent to an AT&T address which had been created as part of the setup process, but which I’d never used. So I paid the overdue bill, set up auto-pay so I wouldn’t have to worry about it again, and then set about making sure I’d actually get the statements. I thought about changing the address listed on the U-Verse profile, or forwarding it to my regular address, but settled on just setting up POP access to the account.

The weird thing is, I’m not entirely sure how we ended up with paperless billing. My filing system’s a mess right now, but I distinctly remember getting one bill on paper. (We signed up in May, as soon as we moved in.) I can’t have marked a checkbox on the bill, though, because I paid it through my bank’s website, not by check. My best guess is that I chose it during the setup process and forgot, and they just sent the first bill on paper.

Posted on
by

Waaay back in the dark ages of the Web (somewhere between 1994 and 1997) I discovered a weekly email newsletter called “This Is True.” It collected strange-but-true news stories from around the world, summarizing each in a short paragraph with a witty one-liner at the end. I subscribed to the free edition, and later to the full version, which had about twice as many stories. I even picked up a few of the books collecting past stories (at a con, I think, but I can’t remember which con).

Eventually I got too busy to read them, and the back-issues piled up unread, and I decided to let my subscription lapse. But earlier this year, I decided to re-up with the shorter, free version, and it’s still as good as ever.

This week’s issue included a disappointing story: even though they practice — in fact, probably helped originate — responsible list management, Yahoo is blocking them as spammers. Why? Because people are signing up for the list, then deciding they don’t want it anymore, and instead of unsubscribing, hitting the “Report as Spam” button. Yahoo has apparently taken those spam reports at face value, and blocked everyone’s copy of the newsletter.

Clearly, some people are unclear on what “spam” means. It’s not just “mail I don’t want.” It’s “mass mail I don’t want and didn’t ask for.”

That, and I’m sure some people don’t realize that their reports are being used to train everyone’s filters. I remember a co-worker explaining a few years ago that he’d trained Gmail to send the SourceForge newsletters (or something similar) straight into his spam folder. I commented that they might be using that data to train their sitewide filters, and he said something like, “I hope not.”

Using user feedback to train sitewide or network-wide (such as Cloudmark, or Akismet) filters is a powerful technique. Some people will catch the leading edge of a spam attack, and that data can be used to protect others as the attack continues. Some will check their mail sooner, and that data can be used to re-filter messages that have been received, but not yet viewed.

Unfortunately, it also can give a lot of power to people who are either unclear on the criteria being used or have an axe to grind, unless you include measures to (a) contain the impact or (b) keep track of each reporter’s reliability. I know Cloudmark factors in the reporter’s reputation, for instance. And I suspect that AOL does, at least in some cases, limit measures such as blocking to specific recipients, but I can’t be certain.

Anyway, to summarize:

  • Use the Report Spam button responsibly.  If you actually subscribed to it, it isn’t spam unless they refuse to remove you from the list.
  • Check out This is True.  You may laugh, you may groan, you may think, or you may get pissed off at the world — or all of the above.  It’s certainly worth a look.

(I really should have finished writing this yesterday, before someone submitted the original story to Slashdot. Posting about it to get the word out seems kind of redundant now. Heck, now that I think about it, I should have submitted the original to Slashdot. Oh, well.

Posted on
by

The IEBlog recently posted about their efforts to improve reliability in Internet Explorer 8, particularly the idea of “loosely-coupled IE” (or LCIE). The short explanation is that each tab runs in its own process, so if a web page causes the browser to crash, only that tab crashes — not the whole thing. (It is a bit more complicated, but that’s the principle.) Combine that with session recovery (load with the same set of web pages, if possible with the form data you hadn’t quite finished typing in), and you massively reduce the pain of browser crashes.

I’d like to see something like this picked up by Firefox and Opera as well. They both have crash recovery already, but it still means restoring the entire session. If you have 20 tabs open, it’s great that you don’t have to hunt them down again. But it also means you have to wait for 20 pages to load simultaneously. It would be much nicer to only have to wait for one (or, if I read the IE8 article correctly, three).

Edited to add:

On a related note, I’ve run into an interesting conflict between crash recovery and WordPress’ auto-save feature. If you start a new post, WordPress will automatically save it as a draft. If the browser crashes, it will bring up the new-post page, but restore most of the form data you filled in. So the title, the text of your post, etc will all be there. But WordPress will see it as a new post, and you’ll end up with a duplicate.

This wasn’t a major problem when I encountered it — I had to reset the categories, tags, and post slug after I hit publish (since I hadn’t noticed that they’d been reset to defaults), and I just deleted the older, partial version of the post — but I can imagine if I’d uploaded an image gallery, I would have been rather annoyed, since there’s no way (that I’ve noticed) to move images from one post to another. Reuse them, sure, but not such that the gallery feature would work.

Posted on
by

I mentioned a few weeks ago that I want some sort of mobile internet access for San Diego Comic-Con so that I can post at least some stuff from the convention itself, instead of waiting until I get back to the hotel. Since the con has never offered wi-fi (except, IIRC, in the press room — which I just realized I could have used last year, since I got a press badge for CBR/Comics Should Be Good), I was looking into phone-based solutions.

Phoning it In

I experimented with post-by-email (not sufficient), with post-through-Flickr (slightly better, but only really suitable for image posts and still missing things like, oh, titles), and with using WPhone to provide a stripped-down admin interface in the hopes that my phone’s built-in browser could handle it (no such luck). No, I was clearly going to need a better web browser — one way or another.

Yesterday I went into a T-Mobile store, partly to look at the smartphones they had, and partly to ask about what data plan would allow me to use Opera Mini on my current phone. The guy tried to sell me a Blackberry, but I have to admit the Wing looked really nice, if expensive.

Opera Mini - The free Web browser for nearly any phoneI asked about getting the Internet plan, and while the sales clerk was familiar with Opera Mini (he uses it on his own Blackberry), he was convinced it wouldn’t run on my RAZR V3t. I’d used an early version of it during a brief window in which T-Mobile allowed access even for phones with the T-Zones plan.  But he seemed convinced there would be no point, so I walked out without having changed anything.  30 seconds of Internet searching reveals that yes, Opera Mini is in fact known to work on the RAZR V3t.

Free WiFi

Today, the news started making the rounds that the con will have free wi-fi everywhere except the exhibit hall itself, sponsored by the film, Eagle Eye. (Which, now that I think about it, is oddly appropriate and somewhat disturbing.)   This is a huge relief, and makes the phone access much less critical. Though it would still be nice…

Sure, it’s going to be a very busy network. But I figure I’ll type things up in TextWrangler and load up the web just long enough to post. Gears will cut down on the amount of bandwidth needed for the admin interface.  And I’ll save any serious emailing or forum visits for the hotel room.  Actually, I’ll probably stay off the forums during most of the con, unless I have the opportunity to post “Hey, look what I just found out!”

»All pages site-wide with this tag