Reply To: JCCC4 Twit-arr post-mortem
@Icemage – That had to be a javascript issue, because I didn’t actually change any of the paging code during the cruise. That is a great data point for me for next year though – thank you.
@Thalandor – it was mentioned several times in the twit-arr thread, I think it was posted on the FB group, and it was in the known issues for the twit-arr instructions passed out in the Seamonkey newsletter on the first day. It could have been broadcast a little better, but I don’t think anyone really realized how much more people were going to be using Twit-arr this year (I had hoped). I think in the previous years it was more something on the side, whereas this year it seemed to be a crucial tool for much of the population.
Statistics (just got them):
511 user accounts
2820 seamails (including the %#@*ing duplicates)
2671 posts
671 photos uploaded
Considering as it was a six day cruise, the network was down for a full day, and many devices either weren’t compatible with the network or the site, I’m completely blown away by those numbers.
Having people use your software is what passes for applause when you’re a software developer, and I’m truly amazed by this. There’s certainly room for improvement, and I promise that it will be better next year, but for an initial software deployment, this is really good. 🙂