> Would it be possible to start logging and saving (and publishing) MP
> messages somewhere so a person with a grievance would have some hard
> evidence to show what happened. Right now when push comes to shove,
> we are
> in a "he said/she said" situation. But if we logged every "message
> + call
> sign + ip address" we could go back and review situations.
> Certainly it's
> possible the grieved party might have said something initially that
> was more
> controversial than they remember and started the situation
> degenerating into
> something worse than it would have been. Certainly it's possible that
> comments would be misinterpreted. We could also passively collect
> some
> stats on what portion of messages contain possibly offending
> language or
> what specific call signs might have unusually high percentages of
> matching
> words. Not initially to use for enforcement, but just to review the
> true
> nature of the situation so we can make a more informed decision as
> to if we
> have a real problem that needs to be addressed, or not ... ?
>
> I understand that "data free" discussions are the most fun, but if
> we logged
> and published MP messages, we could do some statistical analysis on
> all the
> conversations, and we would also have specific cases we could review
> to
> determine if there really is a problem or not. I'd hate to spend 6
> months
> developing an authentication system because one idiot one time said
> something stupid and it never happened again. But if stuff happens
> regularly, or if there are regular offenders, perhaps we would be
> wise to
> think more carefully about developing mechanisms to deal with it.
Hi Curt,
I'm sure that I am not the first person on the receiving end of
trash on mp. I have seen pilots attacked before, and the the best
thing I could do was notify the recipient of the ignore function,
which works good as a defense after an attack has taken place. I don't
think we need anything too advanced, but some sort of preventative
measure is necessary to keep a calm, welcoming multiplayer
environment. I think that storing chat logs would be a good start. I
don't know that the logs would have to be stored publicly, though.
Possibly we could set up a email such as ab...@flightgear.org, where
pilots could email a report in that specifies the time and other
details about the abuse that took place. The report handler could then
go to the chat log, jump to the time that the abuse occurred at, and
read the logs until they come across the abusive messages. They could
then identify the sender of those messages by their IP, and block that
IP from connecting to the server network. This wouldn't be as
complicated as a account system, but just as effective.
I would also like to thank everybody for showing that they care. I can
already tell that we are going to make much greater progress than I
would have on the forums. I am really glad that everybody is willing
to get to a solution and compromise on what we can do to make
flightgear as great as possible.
Semper Fi,
Jack
------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
