search

maboroshin / translation

Translation introduction. 日本語化の情報
7 stars 0 forks source link

Stats against Weblate spam #1

Open maboroshin opened 11 months ago

maboroshin commented 11 months ago

Spams are not related to the Weblate team. A reference to the data is needed. Because fantastic subjective expressions are used extensively. We need a way to quantify this.

(Aug 2023) Transifex Crowdin Weblate
Place USA Estonia Czech Republic
Projects 40,000
Nominal
(2018)		 166K
Nominal		 1,164
Nominal
Open project 16,000
Nominal		 16,869
Actual		 987
Actual
Users 0.5M
Nominal		 2.1M
Nominal		 0.067M
67,413
Nominal
Team 10 peples 8 Peoples 3 Peoples
Eemployees 84 117 4
+Contributors
Word limits No limit? 60,000
words		 10,000
strings
Display of translation rate Per peroject Per peroject 1 page
Integrity
Details		 1 page 1 page Per string
Access control Free Free Free
Participation Per project Per project anyone
Anti-Harassment Policy O O X
Leakage of personal data ? ? X

Service down

Many times in a month Weblate will not allow you to edit anything. maintenance mode for several hours for the whole Weblate.

Blocks of individual projects that can last as long as several days. It will continue until the administrator takes action. In some cases, it has lasted more than a month. Please search ```The translation is temporarily closed for contributions due to maintenance, please come back later'''

With other services I don't encounter this. In other services, at least, the frequency will be much less frequent.

Note for numbers

Description

Wordpress and Launchpad have translation guidelines. A large number of translations can be done with uniformity. Depending on the project, Transifex and Crowdin require approval to participate. And, These two are open to participants who are at least 18 years old according to the terms and uses. Many Weblate projects are open to everyone including kids.

Leakage of personal data

GDPR defines email addresses as personal data. Weblate has already output mail addresses to Github and it is difficult to erase all of it. This is worse when combined with the GDPR right to erase data. https://github.com/guardianproject/orbot/issues/858 See also detail

The project has been offered to migrate from Transifex to Weblate and the contributors' email addresses have been leaked. https://github.com/blueman-project/blueman/issues/1149

maboroshin commented 11 months ago

Repeatedly subjective spammed without data or citation. Transifex and Crowdin are bad. Weblate is the best. SponsorBlock has launched DeArrow. The goal is to correct hype. Thus, People are sensitive to this.

Since last time, Transifex updated their terms, which I found to be more egregious than what was previously pretty far fetched. Also, Weblate got a lot better, and has none of those problems. https://github.com/jonasoreland/runnerup/issues/907

Clearly rejected. Changing translation platforms could result in loss of existing history and contributors.

Transifex is broken ... I still discover new bugs, daily. https://github.com/rakekniven/Transifex-Issues/issues/19 (Locked)

Weblate has no bugs? I have also filed many bug reports for Weblate.

but can't use Transifex since it takes ownership in my work doing so. It is also a bad closed source tool. https://github.com/LibrePCB/LibrePCB/issues/615

It is countered that the ownership issues he mentions also occur in Weblate.

Crowdin has a very clunky UI for getting anything done, and things get held up in their voting system. With fewer libre software translators on Crowdin, and good ones fewer still. https://github.com/ajayyy/SponsorBlock/issues/343

Rejected. Crowdin's history listing and voting system is easy to use. Details. Strange translations are eliminated with a negative rating in Japanese Translation of SponsorBlock. Crowdin seems to have a lot of users. I don't know what he is based on any data.

Quality on Crowdin is poor, and it has few translators. https://github.com/microCOVID/microCOVID/issues/670

with very few libre software projects left on Crowdin. https://github.com/ukanth/afwall/issues/1184

maboroshin commented 11 months ago

There were a total of 60 Weblate spams, Nearly 90% have not migrated. He sees privacy as a problem. I don't understand why he would allow email address to be published.

Not creating an issue (No counting) * https://github.com/ferdium/ferdium-app/issues/185#issuecomment-1150312066 * https://github.com/danth/transfer/issues/9#issuecomment-1132800170
orangesunny commented 11 months ago

Hello @maboroshin, Benjamin from Weblate here.

I would like to offer essential information. The Weblate team do not have anything to do with this effort. I got a notification about your comment in https://github.com/blueman-project/blueman/issues/1149#issuecomment-1682179093 as I contributed to the discussion there. It guided me here, and I left a new comment there, too.

Suggesting a tool in an open-source project repository does not seem like a spam. The community and the maintainers can reject the suggestion, close the issue, even lock it or mark it as SPAM if they feel it.

Keeping a good attitude in discussions can be a tricky discipline sometime. Everyone should be respectful, no one should be forced to do or use something; it is not about winning. If someone’s offensive, you can tell them and/or report them.

@comradekingu is a translator, Weblate user, a fan of open source. They do not work for Weblate, and we never asked him to “advertise” Weblate this way; we do not advertise Weblate at all.

Everyone is free to use Weblate as it is a libre software. We welcome new open source projects the same way we welcome new commercial customers – by a word of a current satisfied Weblate user.

Signing commits by e-mail addresses is a feature, it is how Git works. Open repositories are a feature of open-source software. To top of that:

If you want, @maboroshin, we can connect and chat about anything Weblate, this topic included. Our care (at) weblate dot org address seems like a good place to start for that. We also use Discussions.

orangesunny commented 11 months ago

from the initial post:

... Weblate is open to everyone and there is no access control for free plans.

I am not going to fact-check all the issues in this comparison, but this is not correct. Access control is available in a free plan, but yes, you can’t limit the visibility of the project; it’s open-source after all. Any project owner/admin can prevent a user from contributing to their project, etc.

More here: https://docs.weblate.org/en/latest/admin/access.html#project-access-control

https://rocketreach.co/weblate-profile_b5ebc47af42e8635

This seems more like a collection of things randomly scraped from the internet than a reliable source. The information is incorrect, and we are not affiliated with it.

Weblate numbers in the sheet are not correct, you can’t count all projects using Weblate. There are instances of Weblate unreachable for the public, running in company intranets, etc. Even Discover Weblate is a voluntary, beta feature, not all Weblate instances hosting open-source projects are shown there.

maboroshin commented 11 months ago

Spam

I understand it. I guess it is not the Weblate team that is doing this. If there is a monetary award, it is prohibited by the state as stealth marketing.

Leak

At the end of 2022 we can choose not to have Weblate publish our e-mails. This is due to the following concerns about leaks. However, published emails are still published on each Github commit. Under GDPR, email addresses are personal data. Anyone can view that personal data. Personal data is exposed outside of Weblate and can't be erased.

pappasadrian said

This leads to leaks of personal information publically, by including addresses in public code. This is not respectful towards translators who contribute, and potentially illegal in some jurisdictions (Especially considering that there's no specific consent given. Everyone is opted-in by default, with no option to opt out). ... not a clear option for people who don't want their personal information leaked. WeblateOrg issue#6508

p0358 said

This way weblate instance owner could ensure no e-mails would get leaked by default. WeblateOrg PL#6508

However not everyone registering on Weblate with the will to translate might be aware their e-mail could leak in the commit metadata, as such someone could still do that accidentally, and the installation owner currently has no easy way of ensuring it doesn't happen. WeblateOrg issue#8451

(PS) The Weblate Terms of Service states:

The User agrees to use of own name and e-mail as authorship in the VCS commits. The User understands that this grant is non revocable due to nature of the VCS.

There is no mention about disclosure of email addresses. Before 2022, no one has selected the setting "make my email address public". There would have been no explicit consent.

(End of PS)

Access controll

Please read carefully the page you referred to.

Projects running the gratis Libre plan on Hosted Weblate are always Public. You can switch to the paid plan if you want to restrict access to your project. https://docs.weblate.org/en/latest/admin/access.html#project-access-control

Reliable source

I'm sorry. Please let me know if you have any reliable sources. I will replace it.

orangesunny commented 11 months ago

Feels to me like you are trying to solve problems when there are no problems. Thus, I am unable to help.

maboroshin commented 11 months ago

Leak: Anyone can see contributor's email address. Some call it a feature, some call it a leak. I quoted others' statements above.

Access control: The documentation should say that access control is available even with the free Libre plan. With the current documentation, many administrators would also conclude that access control is not possible.

Reliable source: It doesn't seem to have the information I need on it. I will try to search again later .

PS

It was possible to block users from the project after mid-2021 (version 4.7). It was mentioned in another heading scrolling down 3 pages. I will correction to the description. I appreciate your explanation.

comradekingu commented 11 months ago

No, only you call it a leak when it isn't. E-mail addresses in Git commits is the norm, hiding the real e-mail address is a feature. Zero admins have actual problems with access control. You convinced yourself instead of actually gaining the experience or listening to advice. Send patches containing the changes you want implemented, that is how it works. It is plainly obvious your numbers are wrong, and that is a Weblate employee telling you as much.

maboroshin commented 11 months ago

I'm not the only one. already cited.

Access control is a feature found in Transifex, Crowdin, and Weblate. Is this a feature that is not in demand? It's a feature used: https://github.com/WeblateOrg/weblate/issues/3548 https://github.com/WeblateOrg/weblate/issues/8470

If you know the correct information published, I will change to it.

https://rocketreach.co/weblate-profile_b5ebc47af42e8635 This seems more like a collection of things randomly scraped from the internet than a reliable source. The information is incorrect, and we are not affiliated with it.

All data has been changed to Linkedin data. Compared to rocketreach, the number of employees in Weblate remains unchanged at 4. The overall description is the same.

comradekingu commented 7 months ago

Why would it be strange for the last few libre software projects actually using C or TX may not be interesting in putting in effort to move? It isn't as if they are not finding the same limitations and came to the same conclusions I do. Similarly, there aren't any success stories that I know of.

Crowdin for example has lots of employees that only do marketing, while pretending otherwise. Somehow it is negative for me to counteract this sneaky marketing that prays on the good name of libre software…!? You would like to think projects shifting over is all my doing? It isn't.

To deal with what seems the remaining question you have: Weblate has lots of access control, not all of which is exposed on Hosted Weblate in the libre plan. Could it be that I have actually used all three platforms extensively?