Particracy Forum

There have now been 3 incidents over the last 5 days where Moderation has erroneously performed an early inactivation on a player.

viewtopic.php?f=11&t=8032&start=160#p144685

viewtopic.php?f=11&t=8032&start=160#p144711

viewtopic.php?f=11&t=4360&p=144862#p144858

Three questions:

1. Why is this happening?

2. How many other incidents like this is Moderation aware of which have taken place over, say, the last month?

3. What measures is Moderation taking to reduce the risk of mistakes like this occurring in future?

Aquinas wrote:There have now been 3 incidents over the last 5 days where Moderation has erroneously performed an early inactivation on a player.

viewtopic.php?f=11&t=8032&start=160#p144685

viewtopic.php?f=11&t=8032&start=160#p144711

viewtopic.php?f=11&t=4360&p=144862#p144858

Three questions:

1. Why is this happening?

2. How many other incidents like this is Moderation aware of which have taken place over, say, the last month?

3. What measures is Moderation taking to reduce the risk of mistakes like this occurring in future?

Hey, thanks for pointing it out. These have mainly been my mistakes but I will address this.

1. Like I said, this has been mainly me. By the time I log in to inactivate the party that has been brought up by other players, the party has logged in. So it's a matter of being consistent with time and double checking the party's log in record time see if the party is still up for inactivation or not.

2. These three posts were the only ones I've known of. I do not believe there have been any prior.

3. I kinda touched on it in #1, being more consistent in regards to inactivating parties and double checking if the party is still up for inactivation.


By the way, all the players that were accidentally inactivated were messaged already with an apology.

Hope this is a good response to explain this issue.

viewtopic.php?f=11&t=4447&start=3690#p144890

Luis1p wrote:

Auditorii wrote:classic.particracy.net/viewparty.php?partyid=36284

3 days+

http://classic.particracy.net/viewparty ... tyid=36290

Not recorded bug, need check on date of last activity.

Done

It's happened again.

http://classic.particracy.net/viewuser.php?userid=36127



This player's account was only created about 64 hours ago, so he's not up to the 72 hours mark yet.

Aquinas wrote:http://forum.particracy.net/viewtopic.php?f=11&t=4447&start=3690#p144890

Luis1p wrote:

Auditorii wrote:classic.particracy.net/viewparty.php?partyid=36284

3 days+

http://classic.particracy.net/viewparty ... tyid=36290

Not recorded bug, need check on date of last activity.

Done

It's happened again.

http://classic.particracy.net/viewuser.php?userid=36127



This player's account was only created about 64 hours ago, so he's not up to the 72 hours mark yet.

Well there's some more to back up my explanation. Player's been messaged and reactivated.

viewtopic.php?f=11&t=4447&p=146506#p146500

Auditorii wrote:Over 3 days
http://classic.particracy.net/viewuser.php?userid=36387
http://classic.particracy.net/viewuser.php?userid=29307
http://classic.particracy.net/viewuser.php?userid=35559

No changes, generic party name, 2 days or more
http://classic.particracy.net/viewparty ... tyid=36604
http://classic.particracy.net/viewuser.php?userid=36431 (not recorded bug)
http://classic.particracy.net/viewparty ... tyid=36488
http://classic.particracy.net/viewparty ... tyid=36566
http://classic.particracy.net/viewparty ... tyid=36580

http://classic.particracy.net/viewuser.php?userid=36431

Contrary to what Auditorii indicated in the inactivation request, the account above DOES have its party name & description filled in, so it is not eligible for inactivation after 48 hours.

As you can see, the account has the log-in bug account, which means that when it comes to inactivating the account, Moderation is supposed to try to make a reasonable judgement as to when the player last logged in, based on the player's activity patterns that are visible.

In this case, the player created a bill in September 4528. ie. about 48 hours ago. This means we can reasonably conclude the account is not eligible for the usual routine inactivation after 72 hours.

Respectfully, can we please try to avoid this happening in future? We do really risk putting players off if they are inactivated unduly and without following the proper procedures. Players need to be careful not to report accounts for inactivation until the inactivation criteria are actually met, and Moderators need to be careful about establishing the criteria have been met before they perform the inactivation.