TolstoyDotCom
commented
1 year ago Any form of opinion-based censorship erodes trust and is used by those in power to silence those out of power. If you don't want to see tweets/replies about Alves, Twitter should give you the right to filter that out. The problem is when Twitter uses that to affect others. A lot of snowflakes are triggered by Trump and would block all mention of him if they could; look at all those who cheered Twitter banning him. You'd put those snowflakes in charge of what others can see and that's extremely dangerous.
aloiscochard
Use case 1: The user publishes his dissatisfaction with a football match.
Use case 2: The user publishes his repudiation about a scandal involving a footballer.
The system could internally identify the contextual themes of a publication. There would be an option for users to access what type of context was identified.
User clicks on "..." and then clicks on "Context" from the context menu. A modal with a list appears:
UC1: sport, football, Champions League, Real Madrid
UC2: sport, football, Barcelona, Daniel Alves, rape, sexual violence
Other users can access the "Context" modal. An "x" appears on each item when pointing with the cursor. By clicking on the "x", it is suggested to remove the theme. When more than 10 users click on the "x" of that theme, a suggestion is sent for voting in the Community Notes environment. In the Community Notes there will be a space for theme removal requests. People vote to remove or keep the theme in a post. If the vote confirms the removal, the theme is removed.
UC1: User asked to remove the Real Madrid theme from the publication, as the publication is not about Real Madrid.
UC2: User asks to remove the Barcelona theme from the publication because Daniel Alves is no longer from Barcelona.
There will be a "Suggest Contextual Theme" button in the "Context" modal. By clicking the button, you can enter your suggestion. As you type, existing themes will appear with the current number of posts tagged with each theme. If no related theme is found, a new one is suggested. Upon confirming the suggestion, a request is sent to the Community Notes environment, where a vote will take place to include the new contextual theme in that publication. Remembering that the system includes all contextual themes automatically whenever a user publishes something. The intervention of users will always be for later edition of the list of identified themes.
In the modal, when clicking on a theme, the user is taken to a page in the form of a feed. There it will show several publications related to the topic, as with hashtags and topics. At the top of that feed will be a "..." configuration button. When clicking, some of the options that will appear in the context menu are:
When clicking on "Mute context", a modal will appear written "Mute context by" and a list:
The user's account settings will have a silent contexts session in case the user wanted to undo the setting.
Silenced contexts will not appear in any feeds, will not generate notifications and will not appear in searches. Posts by other users tagged with that theme are hidden from the user.
The "Prioritize context" option works in a similar way, but will increase the display of publications related to that theme.
The name used in the configuration is irrelevant. It can be topic, context, theme, etc. Adopt whatever name suits you best.