Welcome to WordPress!

Hi everyone! Welcome to my new WordPress blog. I’ve switched from Movable Type because of the problems it was causing to my hosts, Textdrive, notably in dealing with comment spam. In addition, WordPress is much less intensive on servers.

I’m now on my third blogging system, my fourth blog and my fifth host, but I’m hoping to stabilize things at this point. I’ve got my domain name for the next ten years, I’m very happy with Textdrive’s service and I have high hopes that WordPress will prove to be the software I’ve been looking for.

As usual in a shift of this kind, some comments have been lost. I had to run in parallel for a little while to get things working. In addition, I’m still dealing with the blogroll. On previous occasions, I’ve promised an attempt to retrieve comments, but not delivered. This time I’m not going to make that promise, but I will try and find a way that those who’d like their contributions accessible can retrieve their comments and repost them.

I welcome comments, particularly from other WordPress users, pointers to designs I could pinch and plug-ins I should adopt, and so on.

UpdateThe MT version of the blog is still accessible here. As Tom DC/VA, the first commenter on the new version observes, mindless reposting of comments could cause trouble. For example, if your comment points out the fundamental logical flaws in a previous comment, reposting it alone may not be helpful. But I’m going to leave that up to the good judgement of my readers. If you think your comment should live a little longer, and makes sense on its own, feel free to repost it (or not).

35 thoughts on “Welcome to WordPress!

  1. Ah – Nick, you’ve found the original Arachne home page, now abandoned (it’s literally years out of date). Arachne is now supported by a user group. Try googling on “Glenn McCorkle”, or go directly to his home page – he hosts the latest release, which I think is 1.77 now (I’m still on 1.75).

    Robert, I don’t know what the codes being sent are. I have described the look and feel I’m getting, but I don’t claim to know what is causing it, merely that since two distinct browsers are rendering weirdly (and didn’t with the earlier blog) it seems to be more likely to be the fault of the new blog. It is precisely because the older officially accepted stuff is supposed to work that I suspect that the coders decided to do something else instead, maybe in some back end that intercepts and converts what is originally being generated. I think it’s worth raising this issue with the Arachne support mailing list – it may turn out to be some minore config file setting at my end, but as against that Netscape shouldn’t be responding the way it does either, if the codes being sent genuinely are standard.

    It doesn’t seem likely to be a javascript issue, which is the only non-enabled thing that I know both my browsers have in common.

  2. PM, as you guessed, WordPress substitutes plain punctuation for typographically correct punctuation. In doing so, it transmits numeric entity codes to your browser. These codes have been an accepted web (and non-web, such as desktop publishing) standard for many years. If your browser doesn’t display them, then it is because it does not support the standard.

  3. As a ratty typist late at night, I find that glitches creep in whenever I don’t use a preview button, so I really value it. And the space to type comments on Safari is now a thin letterboxy thing which is much less user friendly.

    I find the bullet point thingys for links a bit offputting too, and I am not sure about the numbering of comments. The testimonials section is occupying valuable real estate high on the right hand column, which may not be pulling its weight.

    In time, i think you will find a better banner too. Great to get away from corporate blue though. .. ah the pleasures of change.

  4. Speaking as another ratty typist…still it is the thought that counts, people can make allowance for the odd typo and even some awkward writing. As the box down below exhorts …..

  5. ‘…if your comment points out the fundamental logical flaws in a previous comment…’

    Easy to get around that one. Just repost all of Jack’s comments, then all the logical errors would be near to hand.

    Happy New Year to the Captain, crew and passengers of HMAS Johnquiggin.com.

    I support the call for comments preview and ‘recently commented’ to be included somehow. Both are indispensible.

  6. No, Robert, comment preview does not appear as you go, in two respects:-

    – It needs javascript, right? (I don’t use it).

    – It does not let you have a separate stage you can check, i.e. a frozen snapshot (which is true preview). Rather, it does an estimate – an estimate which could be upset by certain sequences of keying around (I’ve seen interactive responses go wrong this way before, and you can never test the facilities enough for confidence the way you can with a batch preview).

    And for what it’s worth, precisely because your attention is on the keying in box, you have to do what amounts to batch use to get the preview anyway, either scrolling to it or looking across if it’s short enough. There’s no gain in functionality and a loss of reliability with interactive preview.

    I know that’s “just my opinion”, but in the computer game, particularly interfaces, I do have quite some background; it’s an expert opinion, which you are quite at liberty to ignore.

    If the interaction screws up with strange use of keying around, I’ll give you the “I told you so” for free.

  7. I take your point. I don’t use preview buttons — occasional typos aren’t worth the effort, imo — so perhaps I’m the wrong person to listen to about this issue.

Comments are closed.