-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
Excessively penalizing accounts for being blocked or reported #658
Comments
I actually also thought of this, and was in the way of fixing it. I think we should stop penalizing blocks or mutes long term, and we can do that by stablishing a window count limit for the block and mutes. |
People that spam blocks & mutes should be penalized, not the other way around. |
Agreed! The current system means that someone aware of this, with flexible morals, can just block all their political enemies. |
Sorry, but can you point to where in the source this "penalty" is issued? |
obviously you are not a minority in any form |
This comment was marked as abuse.
This comment was marked as abuse.
I believe that there should be a credibility scale for accounts in principle. The level of credibility should be visible at least to the next user of the account. The scale could consider:
This scale should be used in various mechanisms of Twitter, including the application of penalties for blocking and muting. Accounts with a higher score on the scale have a greater impact on a user's reach when that user is blocked. New accounts, without verification, with few followers, few likes, many reports, and little reputation in Community Notes would have almost no impact on the penalization of third parties. |
From #660's pull file https://github.com/twitter/the-algorithm/pull/660/files#diff-026dfe956965210a79449841d84abe9fb9a4fd63ffc11f288f932ca3a8b6cc0fR53 Then rubber starts meeting road around L122 negativeFeatures.saveAsCustomOutput Line 122 in ac1aa2a
~L109 in original https://github.com/twitter/the-algorithm/blob/main/src/scala/com/twitter/interaction_graph/scio/agg_negative/InteractionGraphNegativeJob.scala#L109 |
Same, I'd think it does need to be clearly contrasted in how it's not a defacto "social credit" score because that's the type of semantics people like to latch on to for tools like that (i.e. conflate low ranking ~ being banned ). Alternative packaging: Curation (curation scale , score , or skill). Credibility is already very socially ambiguous , moreso once you mix in words like positive or negative in it's measurement. One can be perceived negatively and still have credibility and vice versa
That is a just another system of abuse in an attempt to prevent abuse that guarantees positions of power against dissent.
Just to clarify that should not be penalized against an account for how many other accounts they themselves block. Order Suggestion and splitting into categories
Behavior metrics (usage)
Penalties
|
Either you've experienced it or you're very lucky. Sometimes, even during civil conversation, someone will be in a bad mood and suddenly block you - even someone who you've regularly interacted with!
Please reduce the penalty for this. Also, shadowbanning and/or reducing account "reach" silently, without transparency, is wrong (but much appreciation for this major step towards transparency). Please show us exactly what we've done to be deboosted. That way, we can correct the behavior and remain allowed into the public square.
Please indicate which of our posts have been reported so that we can correct the behavior.
It's truly frustrating (and Orwellian) when a previously well-functioning account is suddenly extremely throttled. Please increase the speed at which an account can recover after being sent to the e-gulag.
<3 Musk and the new twitter. You're the good guys, and we all know it! You're saving democracy and so much more. Free speech is the bedrock of everything. "Freedom of speech, not freedom of reach" is the antithesis of free speech, however.
The text was updated successfully, but these errors were encountered: