Open NathanBnm opened 3 years ago
You can already block user in your project. Having site-wide abuse reporting could be useful improvement.
This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this.
You can learn about how to get started in our contributors documentation.
@NathanBnm I don't like this idea, since it escalates conflict. It will get abused, and most often because of a misunderstanding between parties. Resolving matters in comments is likely, which isn't the case for admins having a go at trying to understand the specifics of any given language.
For the extremely rare cases of actually malicious users, there is no evident problem concerning reporting them being a bit more costly.
If you want to be malicious, why not abuse the report button? That resource is very finite, not suited to the task, and the functionality is an advertisement for possible and likely social engineering.
Edit: Erhm, I'd like to report NathanBnm ;)
Edit2: As a stopgap measure, maybe writing @projectadmin in the comments could notify all admins of a project?
Reporting to site admins does not have to escalate the conflict. At Hosted Weblate we review such reports and in case it doesn't look like obvious vandalism we let people discuss the problem instead of doing some immediate action.
It is by definition an escalation because it brings in more parties. It increases complexity, because site admins are going in blind. In turn that increases time spent, because now at least one new person has to read up on what is going on. That could make it disappear, or it could make it worse. It is also something that increases the amount of reporting, and shifts the balance of engagement. It increases potential for abuse by making it easy to exhaust the most limited resource.
For anything but obvious vandalism, why involve site admins? That is the only thing they can and should be involved in. Why should site admins tell anyone to use what is now the primary (and better) venue of engagement, (which is the comments).
When power is removed from per-user review and put into roles and hierarchy, you get a layer of non-solutions that is very apparent on other translation platforms. A way to solve one problem, opens up others. The problem to solve is rare, and the invoked problems are inevitable.
Having @siteadmin and @projectadmin available in all comments is all the extra functionality needed.
For user profiles I think a comment field there that allows hiding comments from others suffices. That makes it the same functionality everywhere. It also solves the problem of having to use the first string of a project to talk to project admins or reach out to users. User profile comments would probably work with the current terms and services.
for providing our services on the Service, to contact you in matters regarding our services (also by means of e-mails and messaging) and to ensure the technical functionality of our services fulfillment of contractual or pre-contractual obligations
I thought about a comment type in the dropdown that can be selected and goes straight to admins, but that is a bit too available. It also similarly junks up the UI.
Admins should look at the logs of people kicked out of projects, and then decide whether those are malicious. Don't think that should be a direct action either. I would require project admins to confirm, with activity suspended meanwhile.
I am here only because of one MNC. Because of that I lik eto contribute to it?. Any one can please guid me?
Would be great to allow users to report abusive behavior of other contributors from their user profile (like we can do it with translation suggestions).
I recently noticed some users who were damaging translations by putting nonsense in them and had to write to the support to report them.