Either remove them or make them context sensitive. For example, if you click on help from the registration page it displays the help article on registering or if you click on help from the post screen it displays the article on posting a topic.
I have an iPhone 4 and won't be upgrading to the 4S. I did update to iOS 5 though, and I'm not impressed. The new features are nothing compared to the huge drain on my battery life now. I went to bed with 22% battery life the other night and my alarm failed to go off because it died. It takes about 35 minutes to blow through a fifth of the battery life by playing games.
It's aggravating at best. My iPhone's battery life seems to have been cut to 1/4th of what it was overnight by upgrading to iOS 5. I've Google'd it a bit and have turned off a lot of features that have seemed to help, but it's still no where near where it was a week ago.
Also, the fact that I can't put the ridiculous newsstand app in a folder without a hack is annoying. I like my home screen clean and organized! LOL
I think I've made one of these posts before, but I felt another was appropriate with 3.2 now released.
IP.Links was one of the (if not the) first 3rd party application released for IPB 3.0 utilizing not only the new application structure at the time, but also all of the various extensions available to add on applications. It was incredibly easy to integrate my application with IPB3 using these extensions making it feel like it was part of the core product.
Fast forward to today with the release of 3.2, and while I haven't been near as quick to adopt the new features as I was with IPB 3.0, it has been equally as easy to do so. So far I have implemented the "Like" system (note the reputation was already implemented in previous versions), following content, and tagging. Even though there wasn't any documentation (that I could find), I was able to quickly integrate those features by simply looking at the forums application. I look forward to tackling notifications within the next couple days, and from a first glance it seems it too is just a matter of implementing a file and a few lines of code here and there.
Point being, you guys introduced a great framework in IPB3 for modification authors, made only better by the fact that not only do your own 3rd party applications make use of it, but core functionality like the forums do too.
The mobile skin is designed to provide efficient use for its users. It is intentionally designed to be minimal to provide quick and easy navigation of your community. While IPS might consider it in the future, IMO a mobile skin is not intended to be used as a moderation or administration tool. I suggest you click the "Full Version" link available at the bottom of the mobile skin if you're determined to use those features.
When you view a member's profile you can go through a short list of their submitted topics, posts, and other content. If you want to see all of the member's content you can click on the "Find content" button. Currently, this button defaults to the member's topics & posts no matter what tab you're on. I think this should be content type sensitive, meaning if I'm viewing a member's recent Gallery images on their profile and click Find content it should default to the Gallery content type.
Space used would be greatly reduced by only keeping the relevant changed information. If a post is modified to make a spelling correction then it is not necessary to store to nearly identical copies of the post, just the original post and the information needed to know what modifications were made to it (position & what text was removed, position & what text was added).