Thanks for listening to all our complaining about the iOS app. Making it available for free is a good start; however, the app needs a lot of work. Have you considered acquiring a small company that is proficient in this area?
I apologize, I haven't read all 6 pages of postings made here.
I personally do agree that IP.Board will be dead within some period of time. I actually give it 2 years.
For me, this isn't about Facebook, Twitter or Google+. Rather, it is about the App. The web as we know it is dying, a very very quick death. Google knows and and so does Facebook, ie: spending $1B on Instagram is proof that the $$ is in the App business.
I have been running forums since 1996 and I have seen lots of ups and downs. This time is very different. Yes, I am getting very good traffic today. Yes, I am making very good revenue. But, that's going to change rather quickly.
Unless IP.Board can become a *real* App where we can monetize our forums, we're doomed. Plain and simple. The end is near. Using a browser on a computer or tablet is no longer enough.
I'm personally continuing to pay my IP.Board renewal license fees and trusting that the good folks at IPS are using the income they make from me to come up with a solution. Otherwise, In my humble opinion, theirs and our livelihoods are doomed.
I am really puzzled as to how a major release of IP.Board can be made available without an accompanying mobile app. I appreciate that there is something in the works in the mobile app department; however, in this day in age where we are losing so many of our visitors to apps, I truly hope that an iOS app is on its way.
Also, a mobile app is not an extra, where the forum for it currently resides. It should be part of the core platform.
I installed it and ran it all day yesterday on our production server. I found that it forced over 200+ httpd processes to be forked at times. Normally we only have 10-20 processes. It caused our Apache to freeze several times over the last 24 hours. It also logs every Apache NOTICE and WARN in the error_log because it does not respect the LogLevel in httpd.conf. This is a known bug.
I think it's a great idea, but it's not ready for primetime just yet.
Is there an explanation somewhere that can be given to Endusers as to what the Reputation System is and how do Endusers use it? I have reviewed the ACP Manage Member Reputation docs page; however, I am looking for something that explains more at an Enduser level.