Closed GoogleCodeExporter closed 9 years ago
Another thing is that abuse reports should be sent to all admins.
Not sure if we can sort them into groups, e.g. reports from Ikamva users will
only be sent to Ikamva admins (and me), etc.??
Original comment by anna.wer...@gmail.com
on 13 Jul 2012 at 9:18
Report links should be back now (beneath items, with [like], [more], etc). All
admins have access to the same report queue - this is because there may not be
clear responsibility: suppose an Ikamva user reports a comment by a Kingswood
user on the blog post of a Nombulelo learner. It's probably not immediately
clear who should decide what is to be done, who has authority within the school
to take action, etc.
Thus all admins can annotate abuse reports, and all abuse reports show up
alongside the feed of all admins.
Original comment by dumbbuthappy@gmail.com
on 21 Aug 2012 at 10:48
Ok, great. I found it and like the new feature! It's great to discuss the
problem, if there is one.
Tested annotation. Can the original poster read the annotation, too, or just
all the other admins?
Original comment by anna.wer...@gmail.com
on 22 Aug 2012 at 6:25
> Can the original poster read the annotation, too, or just all the other
admins?
The person making the report cannot see the report or any annotations - only
admins have access to the report queue. It may be encouraged to respond to the
user who files a report by PM saying what was decided and if any action is
taken, but that is a procedural detail rather than a software one.
Reports of abuse may bring to light hate speech, illegal content, evidence of
offline bullying, etc and so must be handled discreetly, and may be subject to
legal discovery. This is why the person making the report does not have access
once they have made it, it may not be any of their business, and may have
privacy implications for victims of abuse.
Original comment by awarenet...@gmail.com
on 31 Aug 2012 at 10:18
This is good. Thank you.
Original comment by anna.wer...@gmail.com
on 3 Sep 2012 at 7:19
Original issue reported on code.google.com by
anna.wer...@gmail.com
on 13 Jul 2012 at 9:16