-
-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement a better system for keeping track of alternate accounts #1353
Comments
We had a small discussion in #mods-tools a couple of days ago, and our general consensus was that we don't need something as complicated as creating a brand new infraction type, we could simply have an That said, maybe we do want something more complicated? What does others think about that? |
In my opinion, we don't need something more complex. Maybe some would want at the top of an infraction listing something like
Having the alt command kind of act like an alias would work great in my opinion, I'd like it. |
I am in favor of making a new record type or infraction type for storing alt accounts, and not piggybacking off the note infraction as we have been doing. I'm envisioning this scenario: Now whenever we run the user command for any of the 3 users, there is a section on the profile (or a button leading to a new section) that there are 2 other users associated with this one. I'd also be in favor of storing and being able to edit the reason and justification that we've determined the relationship to exist. |
I agree with mina. Automating the adding of a note to corresponding alts may remove some of the potential error (like not bothering to add a note in the other direction), it still requires extra work to investigate anything to do with alts. Making this a formal relationship, this info can be displayed automatically and provide extra details "for free". For example, if I do |
I'm going to pick this up as a winter holidays project I think. The approach I'm thinking of:
More reasoning on the alt-info command...If we have the example of 3 accounts: id1, id2, and id3. id1 and id2 have already been marked as alts. If we mark id1 and id3 as associated, I'm specifically not going to apply an association between accounts id2 and id3 for a few reasons. I think avoiding doing that will make the overall implementation simpler especially for users with a large number of associated accounts and not all associations are guaranteed alts, so I'd rather not automatically run those associations. To cover the situation of a main account having 12 associated accounts and us looking at one of those alts in isolation (we would only see 1 associated account, not showing the true nature of how many total connected accounts there are), that's where the The output would look something like...
|
Currently, if we believe that two or more accounts belong to the same person, we issue a note infraction for each account stating which other account IDs we believe to belong to that person, which requires a series of relatively similar commands that are ripe for error. It also makes it more difficult to respond to incidents pertaining to such user.
I think we need some way of documenting which accounts we believe belong to the same person and why we believe this, as well as the option of viewing a joined infraction table when querying a given user's infraction history across all their alternate accounts.
I make this suggestion with the awareness that suspected alts are not the same as confirmed alts (and it's not necessarily possible to confirm an alt), so any functionality that we design as a result of this issue should not change the way we currently approach infracting people based on infractions from suspected alts.
This issue should also await changes described in #1189.
The text was updated successfully, but these errors were encountered: