Ideas?

Do we have a formal way of resolving duplicate entries? I can continue to send messages to Matthew pointing them out, but would be nice to know what the proper preocedure should be. e.g. currently have 1748 and 3226 - 2 entries for Army Hut in the Snowdon Forest.

How cool, I just put in Hut 500, was wanting to add it to my bagged list. Noticed afterwards. Though if you remove one of the army huts it #499. Oh Well.

I think we need multiple pages for forum threads... A few are extremely long now. Although they still load quickly.

Curses. I spend all day putting huts in and you get no. 500!

Just looked at the hut listings, you have been busy. Looks good.

Hi Madpom, There is a system for merging duplicates, but I needed to test it before opening up for public use. It's ready to go so I'll turn it on and let you know the procedure. It's quite simple. Matthew

Militaris, yes I think so too. I will look into that.

Hut Listings Is it ok to put in removed huts, eg Waiopehu Hut has had 3 versions, Powell Hut has had least 3 maybe more.

What do you think? I think it's OK as long as it's clearly marked. It's interesting for historical reference. We just wouldn't want people planning their trips around them...

Java: I notice an increasing number of features are becoming accessible ONLY with javascript turned on (e.g. ability to comment on items). Really was wondering a) if Matthew was aware of this, and b) if anyone cares. Only reason I noticed is I've had to turn java off to disable Yahoo Mail's annoying new javascript features which probably seemed like a good idea in a lab somewhere with 100baseT to the server, but simply don't work on an intermitant mobile broadband connection on the Capital Connection. After years of s/w testing (previous life: possuming is much more fun) with the rule of 'a non-java alternative must always be available', a requirement for java catches my attention as a BAD THING. But will anyone else notice? Probably not.