dnalounge update

DNA Lounge update, wherein there are photos, and the website overhaul seems to be done.

9 Responses:

  1. evan says:

    BTW, Chrome calls itself Safari, so that's (maybe?) why you don't list that in your stats. Mine is: "Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.1 (KHTML, like Gecko) Chrome/6.0.437.3 Safari/534.1"

    (Yes, that is ridiculous.)

    • jwz says:

      Right, I forgot that even existed. Looks like Chrome and Opera were both a couple percent.

      I have basically no web stats, so I had to do this by hand with the raw files. It looks like my ISP last updated their stats page in 2008. Way to go, guys.

      Is there some simple tool that will just tell me browser stats, given an apache log file? I tried installing awstats on my home box, but it was more complicated than the 10 minutes I was willing to spend dicking around with it. I just want some dumb script that takes a log file on stdin and gives me numbers on stdout.

      • evan says:

        Every time I've looked into it I have also only found frustratingly complex and underpowered tools.

        I eventually gave up and use Google Analytics, which is really thorough but pretty much the opposite of an offline log parser (you have to feed them your traffic to get any stats). I am not too happy about it, but I am happy I am not fiddling with awstats.

      • asjo says:

        I find Visitors pretty okay for casual webstats. The first example in the man page is:

        % visitors access.log | less

  2. aris1234 says:

    Most of the people using MSIE6 are corporate users where they have some application seemingly hard-coded to only work with MSIE6 - and their admins can't upgrade. Hardly the kind of person who will be browsing the DNAlounge pages.

    • jwz says:

      Well, we do strongly encourage people to goof off on company time by deciding where they're going to go dancing later.

    • gregv says:

      Yup, we have important IE-only sites (made by a NYC agency, not by us) that we need to deal with. Fortunately they're IE-only, not IE6 only. Also, none of the other browsers seem to give much of a shit about supporting corporate Windows environments. You can make Firefox work anyway, as I did, but it takes a lot of effort (I shouldn't have to write an entire blog's worth of instructions) and it still won't work if you need it super locked down, which I don't.

      On the other hand, it changed my opinion of IE-in-a-Firefox-tab extensions from "dear god why?" to "this is the most useful thing ever."

      • vsync says:

        For the record we've done a lot of work (including locking it down) with Firefox and other Mozilla products for Sun's internal users. Works fine for us on Solaris, Windows, Mac, etc. A coworker of mine has put up some good writeups on aspects of it and on general JavaScript tricks. I'm planning to do the same. Think I'll pass your site around to coworkers as a good resource.