Field of Science

Name That Bug # 3

Mr Greenslade, tell the masses what's the challenge:

Perhaps a little easy, but I'm feeling charitable. Size of image about ten centimetres across. Attribution, of course, to follow identification.

Update: The identification post for this image (from Engel, 2005) is now available here.


  1. Its the giant butterfly-like lacewing Meioneurites spectabilis from the Jurassic of Kazakhstan, as anyone who has a copy of Grimaldi and Engel could easily find out.

  2. Geeks! =P

    Lacewing was the second thing that crossed my mind, after a brief "moth....NOT moth!" moment. But I don't really work with dead stuff, and with my limited knowledge of zoology, couldn't be bothered to even try. In fact, I have no idea why this thing even reminded me of a lacewing - something about its head?

    I'm thoroughly ignorant about paleontology though. Like, nearly creationist level ignorant. (ok, maybe not that bad) Should probably fix that.

    Also should porobably stop procrastinating with quantitative imaging (ie shitloads of pictures so I can then sit down and fuck up that carpal tunnel thing with endless measurements. Oh joy)

    [/procrastination rambling]

  3. Sorry for being off-topic, Chris, but have you checked lately? For a while, any attempt to visit it using Firefox 3.5.4 has given me a "Content Encoding Error: The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression." Internet Explorer 8 simply complains that it can't display the web page, with no other useful information. I'm not having trouble with any other web sites, including

    Apologies if you've already explained this problem elsewhere.

  4. I've got no idea what happened to, sorry. I haven't been able to see it for some time either.

  5. Is there anyone else I should contact? Yours was the first name that came to mind.

  6. Try Alan Kazlev. His contact details are on

  7. Server seems to slap whitespace and two newlines in front of any responce for some reason. As the result, you get:

    client: "I want this page; oh, BTW, I can handle gzipped responce"
    server: "great, let me gzip it and send the result your way"
    server: vomits whitespace and a couple of newlines
    server: sends actual gzipped contents
    client: "bugger off; I don't know what you've sent, but gzip archives do not begin with whitespace"

    FWIW, firefox can be told to lie about accepted encodings, which makes "work". Emptying the setting for
    in about:config page will do it. Server is told that no compression is accepted, so it sends everything uncompressed. It *still* slaps the same junk in front, but an extra whitespace in the beginning of HTML document is simply ignored, so...

    Not a solution, of course, since that setting applies to *all* sites, not just

    NFI how does one misconfigure the server like that. I've just sent the above to Alan, let's see if that has any effect...

  8. Thanks, Al, that did the trick. I've passed your explanation on to the person Alan said was in charge of the server, as well as cc'ing Alan.


Markup Key:
- <b>bold</b> = bold
- <i>italic</i> = italic
- <a href="">FoS</a> = FoS