Battle Blog Support returns to the listserv model....

[Moderator]

If you're old enough (in Internet days) to remember what a listserv was you remember one as a free and fun place to discuss specialized topics with select individuals who had to subscribe.  Back in the earliest of days this tended to say something about them much like an operator's license and complex task barrier for a ham radio operator does.  Those who managed to subscribe were above all else slightly more technical than the average person and they were passionate enough to find the listserv and subscribe.  Something which took another rare component -- an e-mail address.

I like the listserv model for support and Google Groups comes as close in simplicity to that as is reasonably possible, while remaining easily accessible.  Listserv's are passe' and most likely most of you will access information here via the web.  However, that's good enough to support an open community approach to Battle Blog support, something I feel is critical to maximizing access to the full spectrum of coding talent and Battle Blog forkers.  As original Battle Blog author I simply do not have the expertise or mastery of programming well enough to provide the very best solutions over my very own product.  Yes it's ironic but honesty can be that way.

The most important reason to be on this list is for security related news.  If in the course of using Battle Blog you discover a security flaw, your one obligation if there is any for using the free product, is to rush immediately to this list to let everyone else know.  Solutions and precautions can then be discussed rapidly.

To make this list count I am only monitoring this list for support questions.  I will *not* reply to non-administrative questions via direct e-mail, nor will I discuss security or product issues privately.   Content from this list may be quoted at the Battle Blog support website, but I will not use screen names or other identifiable information in my citation of the source.

Thank you for participating in this support forum and for your diligence in reporting bugs and security issues here.

Regards, 

David Pinero