Prevent people from replying to the same person more than once

VERIFIED FIXED in 2014Q3

Status

support.mozilla.org
Army of Awesome
P3
normal
VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: atopal, Assigned: rehan)

Tracking

unspecified
2014Q3

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=contributor c=AoA p=2 s=2014.13)

(Reporter)

Description

4 years ago
Show people a message that the tweet was already replied to and discard the message.
estimating at 2 pts
Whiteboard: u=contributor c=AoA p= s=2014.13 → u=contributor c=AoA p=2 s=2014.13
(Assignee)

Updated

4 years ago
Assignee: nobody → rdalal
There is only one issue with this, somebody like me may want to respond another time if the first response given does not satisfy the issue brought up by the user, I would want to make sure they get the correct info.
(Reporter)

Comment 3

4 years ago
Hmm, maybe this should be a warning then instead of a block? Andrew, how often do you encounter such situations? Is it reasonable to say, it barely ever happens and can be better handled using your twitter client?

This is Madalina's call.
Flags: needinfo?(mana)

Comment 4

4 years ago
(In reply to Andrew Truong [:feer56] from comment #2)
> There is only one issue with this, somebody like me may want to respond
> another time if the first response given does not satisfy the issue brought
> up by the user, I would want to make sure they get the correct info.


IMHO the proper way to handle this would be to let the original responder know that he/she should add extra info to their response. I believe that the credibility of the AoA members (for the sake of Firefox) should not be questioned by a second responder doubting the first or proving him/her wrong. If there is coordination between the AoA members (IRC channel? PM on SUMO?) then this should not be hard. (The extra benefit of this is that the original responder has a new piece of knowledge learned for future use).
(In reply to Kadir Topal [:atopal] from comment #3)
> Hmm, maybe this should be a warning then instead of a block? 
> ...
> This is Madalina's call.


Possibly the block could look at the users status.  Not discard messages from Mods and Admins or whatever groupings apply to AoA. 

AoA Action Plan from CAC 
(see https://dl.dropboxusercontent.com/u/21664531/Army%20of%20Awesome%20Short.pdf)
Any implementation of something at least partially along those lines may benefit from new groups in AoA, even as simple as AoA-New(untrained) vs AoA-Confirmed(trained)

Block Viewing
As a totally separate bug would it make sense to restrict access to *view* and post only to Sumo registered users. 
In a worse case scenario AoA tweeters damaging Sumo &/or AoA  reputation could have their accounts deactivated in minutes utilising existing facilities.  We need to block the viewing not just the posting for that to be effective otherwise users may view then use their own client.

Comment 6

4 years ago
I think we should go with the discard first and open it up for moderators/trusted users once we have these groups created (I believe everybody in this bug can be considered a trusted user :)
Flags: needinfo?(mana)
(Reporter)

Updated

4 years ago
Blocks: 1043431
(Assignee)

Comment 7

4 years ago
Landed:
https://github.com/mozilla/kitsune/commit/4f5657bd0d948d20331e7cc40277a8ecf430093a

Pushed to prod by me, right now.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Reporter)

Updated

4 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.