[Scarecrow]

Since the last update, whats new at OPS-Center:

- Site security wrapper improved to include IP blacklisting and XSS exploit blocking (damn script kiddies)
- Actively pursuing specific IPs who are attempting overt penetration behavior - yeah, we know who you are you mofo's
- Continued debugging and refinement based on user feedback and our testing
- Event and Field SEO optimization (optimized to Google Search better)
- Better initial IP user/geo-location management
- Editing an Event doesn't nuke the field selection anymore (sorry Brian)
- Better Field Selection options when establishing or modifying an Event
- Waiting List behavior refined based on host feedback - not perfect yet, more to come, soon to be completely automatic
- Minimum Age added to Event description and Join logic - control the age of those who Join automatically
- Comprehensive Warning/Banning System Version 1.0 implemented, designed to encourage dispute resolution
- Improved Side display logic manages screen real estate better
- Banner Ad (Vendor & Benefactor) system completed, instruction pages to be finished and posted by Monday
- Vendor and Benefactor Banner Ads are now live and working
- Ops-Center.co.uk now working (alias for .net - same app and DB)
- Early Events have run and gone into Archive successfully


Warning & Banning System Overview

We really struggled with this - not technologically, but rather trying to figure out the psychology of the problem and how to translate it to OPS-Center.

Based on our analysis and consultation with a number of Hosts, we've concluded that Warnings and Banning should be privately managed between the Host and the Player. We've based the design on something called "progressive discipline". A Host can issue a Warning - the warning is emailed to the Player and a notification appears in the player profile. Further, if the warned player tries to Join a Hosts's game who issued the warning, the Player will be reminded of the warning. A Host can also ban a player. Banning works almost the same as Warning, except the Player cannot Join a Hosts game who has banned them.

With Warning or Banning both the Host and the Player are encouraged to communicate privately through the message system to resolve their differences. With the progressive discipline model we hope that differences can be discussed and resolved so that Hosts and Players can both get their needs met. But we do understand there will be cases of irreconcilable differences, and bannings will help Hosts in preventing Players Joining their Events who they simply don't want there.

To be clear, Warnings and Bannings are between the Host and the Player. There is no mass banning feature and if Hosts want to mega-ban somebody, they`ll have to communicate with one another on that type of issue. Also, OPS-Center staff will reserve the right to mega-ban in very specific cases, cases where the public interest would be better served without that individual (ie: An Atreyu scenario for instance). It will be done reluctantly and carefully.

This isn`t the final word on how Warnings and Bannings work, but its the starting point. We hope we`ve struck a balance between Host and Player rights. As usual, feedback is welcome.


Features Roadmap

- Continue to refine the front page display
- New notification options, such as weekly email blasts of Events in your area, and Events and Fields your friends are playing at the next x weeks
- Invite Only Event Support
- Private Event Support
- Secret Players/Secret Sides
- "Chatterbox" dboard discussion autolinking - helps you find the dboards and threads game discussion is happening at
- Event "Jacket" - a printable Event summary for Hosts and Players
- Host Event-Fee collection system through OPS-Center
- Improved compatibility with mobile browsers
- Pre-Event discussion Wall/Pre-Event Bunker Walls