Please Update Feed

I've set up a FeedBurner feed for this site here: http://feeds.feedburner.com/artificarticles. Please update your subscriptions to point to this feed. More information about this update here: Meta: Please Update Feed Subscription.

By: Ed Costello at 04:25 on May 08, 2006. #. .

Site Redesign and Restructure

I have nearly completed a site redesign and restructure. I may write more at a later time, but the key elements have been:

Why did I eliminate PHP? I found that I was using PHP almost entirely as a smart template and file imbedding tool. This is not a knock against PHP, but I found it to be overkill for what I was doing. I restructured the templates used for the Articles and blog so that they emit clean HTML and XHTML, performing whatever includes I'd been using PHP for from within MovableType.

I had been using PHP's built-in gzip compression to serve up compressed files but as a performance-weenie felt that that was a poor optimization: the server had to compress data on the fly for each request.

So one of the major goals was to rely on Apache's own features more and less on hacks in PHP scripts. Ideally I'd use mod_gzip as well but that is not presently supported on Pair networks' servers.

There's now an informal blog on the site, 202 Accepted. The title comes from one of the lesser known HTTP status codes. I plan to make this section (Articles) more about reference content and move opinion and conference notes to the blog.

Back to Apache...all major index pages are provided in HTML and XHTML formats. They are also compressed. Apache's content-negotiation is used to serve an appropriate file back. Once I determine how to patch MovableType to compress data after writing a file then the MovableType generated content will also be served compressed.

Now, no, I don't get so much traffic that this is a concern, but I wanted to get a real-life demonstration going of what's possible with a generic web hosting setup. It's my contention that with the typical hosting package, anyone can run a relatively high volume content site (if the volume is against content and not applications).

The upgrade to MovableType 3.2 was almost flawless. One hiccup has been, and continues to be, using the SixApart provided JavaScript files with XHTML pages. In brief, they rely on document.write, which is not supported in the DOM model used on XHTML pages. I had previously rewritten the JavaScript to work on XHTML and just need to patch in the latest updates. For now, typekey authentication only works on HTML pages.

By: Ed Costello at 19:10 on March 21, 2006. #. .

On The Importance of Reverse DNS

I was creating a cache file for webalizer and analog and came to the obvious optimization to select only hosts which received a "200" status code in response to a request (I suppose I could add 304s as well but I'm not sure that would add any value), and then strip out any hosts which made less than 10 requests in a 30 day period. This reduced the IP address list from about 3500 entries across the sites I maintain, to 470.

See updates below...

There appear to be about 140 unique organizations that hit the sites (mainly epcostello.net, frisket.org, and artific.com).

18% of the addresses do not reverse resolve.

Of the 387 addresses which did reverse resolve, 41 (11%) reverse resolve to an address which itself does not forward resolve to anything (that is: address 1.2.3.4 reverse resolves to something.example.com, but something.example.com itself does not resolve back to 1.2.3.4.

MSN has a number of hosts which reverse to a phx.gbl top level domain (64.4.8.113 through .118). That is to say, 64.4.8.113 reverse maps to by1sch4041904.phx.gbl, not .msn.com or .msn.net. I sent a note to the poc for the 64.4.8 network but it appeared to disappear into a black hole. Or they're intentionally reverse mapping to a nonsense domain.

Oddly, there's another 17 hosts which all reverse resolve to msnbot.msn.com, none of which are on the 64.4.8 network. That is to say: 17 hosts, across a number of networks and subnets, all reverse resolve to the same hostname, msnbot.msn.com, this hostname itself does not resolve to anything.

crawler.bloglines.com does not forward resolve to [65.214.39.151], though 65.214.39.151 resolves back to crawler.bloglines.com.

MSN seems to have the largest number of IPs and hostname mismatches or resolution failures.

One of the IBM gateways (I'm guessing in the Southbury, CT data center) reverse resolves [129.33.1.37] to bi01pt1.ct.us.ibm.com, which does not in turn resolve back to 129.33.1.37.

Nothing earth shattering here...most web sites turn off name resolution these days, doing it only in post-processing, or on a specific basis within an application. And no one who is remotely sane turns on HostnameLookups double in their server configurations.

Where it does come into play is if you are using hostnames in access control lists. Unlikely on a totally public site, but if you have a protected area, a semi-private extranet, and you add a Allow from .ibm.com, then anyone who's using that 129.33.1.37 gateway will get bounced, at least from Apache based servers since mod_access will perform a double lookup (at least according to the documentation).

I suppose there are other situations where you might use the hostname to allow access for search engine spiders, where otherwise you might require some other form of authentication (eg: set up a satisfy any block, add allow *.google.com, *.msn.com, *.yahoo.com and then a check for a cookie with a mix of Allow and SetEnvIf rules.

This article continues here: http://artific.com/articles/2005/12/27/a_practically_u/l#more

By: Ed Costello at 06:36 on December 27, 2005. #. Comments (14).

Technorati tags:

Thoughts on Cyber Monday

I thought I knew all of the buzzwords, but this year's cybermonday seems new to me. Cybermonday is (allegedly) the web version of Black Friday, the traditional kick-off to the holiday shopping season, except online.

Some advice, for users and the technology types who will be under siege:

If you're buying...

Keep a copy of notepad or textedit (or whatever editor you happen to like) open while surfing and buying items. If you’ve found something that you have been looking for a long time, copy the URL or product number or even the contents of the page to the open editor window. This is insurance. Insurance against your browser crashing before you complete the transaction. Insurance against the web site crashing before you complete the transaction. Insurance against spending even more time re-searching for the item.

When you are checking out, pay very close attention to the check out pages. Look out for additional marketing offers (which you may or may not truly be interested in) which default to being checked “yes” or “interested” or “please send me even more junk mail”. Look out for additional “features” which have been courteously added to your shopping cart and may be small enough to be misread as tax or shipping charge.

If you’re buying downloadable software, or music, or other content, make and save a copy of the receipt for the content. If there are product keys, print them out, add them to your Yahoo! notepad (or that open editor window, but then save!) or Gmail or elsewhere.

My personal preference for all receipts, or things which are like receipts (automatically generated passwords, product keys, etc.) is to print them to PDF using Adobe Acrobat (or save as PDF for Macintosh users). I set the “Author” field to the URL of the page with the receipt (which frequently encodes information about the shopping cart).

If a web site is slowing down or acting “funky”, stop shopping there. Save the information you’ve captured in your editor and either return later or find an alternate site. There are a million reasons why a site may slow down, none of which are under your control. You can sit and get frustrated, or you can move on to other sites and other tasks.

Don’t shop from work. I write this not out of an ethical, misusing the company’s resources concern, but out of a security and privacy concern. Your work or business network is likely filtered and monitored. This data is captured and logged somewhere. Many commerce sites do not encrypt their transactions until you actually start the checkout process. This means that at a minimum, the URLs of the sites you’re visiting will be logged by the great corporate logger, and possibly the content (if you are using a proxy server, and many times you may not even know that you’re using a proxy server). Once that data is logged, your privacy is dependent on the security of that data. It’s out of your control.

Make sure encrypted connections really are encrypted and make sure you’re using the website you expect to be using. An encrypted URL will start with https://. The resulting page should cause a lock icon to appear somewhere in your browser. If you’re shopping at a site for the first time, inspect the encryption (depending on your browser, you can double-click the lock icon and bring up a dialog box). You can check out the certificate for the site to verify it’s for the business you expect it to be (as far as I know, no known phishing/pharming sites have forged SSL certificates to look exactly as the expected site).

If you're under siege (aka, the webmaster, CTO, etc.)...

It's too late for my first bit of advice: don’t make any technical changes to the site for the month leading up to Cybermonday. Too often the marketing & sales guys want to do a big launch this week. I know you know that is stupid and risky, however just to go on the record, my reasons are:

Have a backup operations plan, a “plan B”. Not a disaster-recovery plan, but an operations strategy you can move to which retains the critical elements of your site (for instance: a commerce engine) but lightens the site (perhaps junking large interactive content, large images for small).

Running a large commercial web site is, unfortunately some times, a 24 hour a day job. Make sure you and your staff are set to provide coverage “off hours”, even if that means being off during a “normal” work day.

Be prepared with all sorts of statistics. Traffic in, out, number of shopping baskets created, items filled, number actually used. Whatever “transactional” activities occur, you should be able to slice & dice the data and present it. This is data you likely already collect and present on some periodic basis. When under “siege”, though, you’re likely to receive frequent demands for updates on traffic from the sales and marketing side of the house. Automate the collection and presentation of the information (ideally, let them interact with it directly, removing you from the path altogether). Furthermore it may have value to you. With the growth of broadband at home it takes people much less time to surf around a site, there’s less of a penalty to loading multiple pages. The result is that you may see more traffic as people browse around, vs. years ago when dialup pretty much limited browsing to variations on specific items.

By: Ed Costello at 05:00 on November 28, 2005. #. .

Web 2.0 effect on Ad Measurements

When I was at ad:tech earlier this month I was wondering about this: Will AJAX Scrub IAB Impression Guidelines?. The IAB is just now getting agreement around the web on measurement and auditing, a project I remember working on at IBM almost six years ago. With AJAX and other dynamic techniques, it's possible for a user to "sit" on a single page for quite awhile. Do you count that as one impression? Do you report the time spent on the page (not counted in the current IAB standard IIRC)? Do you rotate ads?

By: Ed Costello at 14:29 on November 22, 2005. #. Comments (1).

OPA '06: Forum for the Future

Received an invite to attend OPA '06: Forum for the Future, which is a conference put on by the Online Publishers Association. It looks interesting, possibly even amazing, but I can't justify going (mostly because I'm already set to go to the e-tech conference in San Diego the following week). I'm not the target audience and don't (presently) have any clients who are in the target audience.

Besides, the registration server only supports SSL 2.0, which I've disabled (and MSIE 7.0 will not support). SSL 2.0 is ancient, even SSL 3.0 is ancient but is the latest version (and TLS seems to be favored now).

Here's an open invite to the readers of this site, all three of them: if you are going to OPA, I'll trade in-depth notes from etech the following week for notes from OPA, or at least point me to a blog with decent notes.

By: Ed Costello at 02:12 on November 21, 2005. #. .

Web 2.0 2005 Recap

So, Web 2.0 2005 is over, I'm sitting in the AA lounge at SFO waiting for my flight back to Brooklyn and I'm trying to figure out if it was worth it.

No doubt, this was expensive for me as a freelancer. Was it interesting? Certainly. Was it valuable, did I learn anything? Not so much.

I learned that there's a lot of innovation going on, but much of what was demoed here I either knew about already from my insane Bloglines blogroll, or because I'd seen it at the 2005 eTech conference.

I learned that there appears to be a lot of money chasing projects around, which I'm not sure is a good thing. It's ironic for me personally, because three years ago I started out plotting various projects and learning the VC game to find out what I'd have to do to get seed money. At present I'm pretty much convinced that taking VC money would be the worst thing I could do. One of the speakers today talked about companies wrapped around products, that the logical exit strategy is acquisition, not the IPO that many VCs would expect or require.

On balance, while I don't regret coming, I don't expect to be back next year unless I've launched something and need to pick up buzz. I think part of the problem is that at heart I'm a server side tech guy, and Web 2.0 is geared to a different audience. I plan to attend eTech next year, and will likely look for a fall conference to attend.

I was disappointed in the production of the conference, especially with the first day. The organizers seemed overwhelmed with the attendance at the workshops as did the hotel (one speaker noted that we all now knew the "smell" of Web 2.0 as we steamed in the various rooms). I know what it takes to produce these events, and know that there's always glitches. But for US$3k I expected better.

I was surprised and dismayed at the absence of women, both on stage and in the audience. This last day we had both Kim Polese and Mena Trott, and the CIO of the city of Philadelphia, Dianah Neff. Earlier we had Mitchell Baker, but that's it as I can recall (and apologies if I'm forgetting someone). I don't know what I can do personally about the situation (well, I could fail to succeed in my upcoming projects but that's not in my best interests).

The conference was very US focussed, even West-Coast focussed. This is a general gripe I've had with the O'Reilly conferences, and I imagine that they make a satisfying profit staying on the West Coast and don't see a need to expand to the East or Midwest. As for the U.S. focus, while understandable, it seems contrary to the very idea of Web 2.0 of putting good, empowering technology out for anyone to use regardless of location.

My "net-net"? A lot of innovation is going on, using a variety of technologies under the Web 2.0 rubric. Combine data, broadband, web services (ignoring REST vs SOAP vs XML-RPC), AJAX and you've got Web 2.0. Web 2.0 is about simple projects that solve straight-forward problems. Web 2.0 is not large, complex applications (though really some of this code is complex and is large especially when you wire various services together). Web 2.0 isn't about the enterprise...yet.

Personally, my lesson learned (an aside and apologies to anyone new here: after leaving IBM in 2001 I spent the last few years sort of wandering in the wilderness trying to figure out what to do next), anyway, my lesson learned is to just get moving on some of the projects that have been stewing for the past couple of years. They all won't succeed, though hopefully a couple will at least recoup their costs, but enough sitting around trying to figure out the right thing to do: set out, stumble, get off the mat and try again. So I'll get back to work on Yet Another Social Bookmarking Tool and the other stuff that's piled up.

If you found value (or have criticism) in these notes over the past few days, could you either leave a comment or drop a note to inquiry@artific.com?

By: Ed Costello at 04:00 on October 08, 2005. #. Comments (1).

Technorati tags:

Web 2.0 2005 Day 3, Afternoon Session

A Conversation with Sergey Brin

This article continues here: http://artific.com/articles/2005/10/07/web_20_2005_day_4/l#more

By: Ed Costello at 20:23 on October 07, 2005. #. .

Technorati tags:

Web 2.0 2005 Day 3, Morning Session

Missed Stewart Butterfield

Dick Hardt from SXIP on presentation on identity 2.0

CIO of City of Philadelphia, Dianah Neff

ad for Philly played...ergh

UI Minute w/Seth Sternberg on Meebo

Conversation with John Highland and Vinod Khosla

From the Labs

HP, Yahoo...

Gene Becker of HP Labs

Usama Fayyad and Prabhakar Raghavan from Yahoo

Now Prabhakar on Yahoo! Mindset

Alan Eustace, VP Engineering of Google

This article continues here: http://artific.com/articles/2005/10/07/web_20_2005_day_3/l#more

By: Ed Costello at 18:03 on October 07, 2005. #. .

Technorati tags:

Web 2.0 2005 Day 2, Afternoon Session

Afternoon session Web 2.0 2005

Discussion: Will Gaming Transform the Web?

Mark Stevens , Greg Ballard, Mike Cassidy, Raph Koster

network capabilities of newer consoles

Discussion: The Future of Entertainment

Mark Cuban (hdnet, dallas mavericks) , Reed Hastings (netflix) , Michael Powell (ex-FCC, provident investors),
Evan Williams (ex-blogger, now odeo)

(mark cuban and michael powell embrace)

A Conversation with Jonathan Miller (JM) , CEO AOL

A Conversation With Jeff Mallett and Mickey Hart

interviewer: ?

[implies to me that via Snocap you can't d/l directly from artists but only throuhg approved retailer sites]

By: Ed Costello at 23:54 on October 06, 2005. #. .

Technorati tags:

Site navigation

Artific Industries Essays Archives

:
:

Feeds

We use Feedburner to distribute our web feeds:

Google
Web artific.com