search

FreeTubeApp / FreeTube

An Open Source YouTube app for privacy
https://freetubeapp.io/
GNU Affero General Public License v3.0
13.48k stars 836 forks source link

Weblate's poor functionality (translation platform), Intent of original text #648

Closed maboroshin closed 4 years ago

maboroshin commented 4 years ago

The intent of this issue was to ask the developer a question.

Here the contributor asks the developer questions about access control and the original text.

Hi! Developper. What does it mean?

It has been changed to "bypass connection limit" on Japanese.

I've been translating for a year. kyotaro has rewritten hundreds of strings. His quality is not bad.

But, Practices not found in the Japanese translation guidelines of Wordpress (Or other, Wikipedia etc), for example

Strange notations have increased greatly.

What should I do? I think we might as well discuss it here. What do the developers think?

PrestonN commented 4 years ago

Hello! I'll try to help however I can.

At the end of the day, I have to rely on the translators of their respective language to make the right calls as I won't be able to check their work. So if there are problems with the translation itself feel free to take advantage of the features within Weblate to discuss changes with other translators.

As for your question, changing it to "Bypass connection limit" should still make sense. YouTube can sometimes block you if you make too many connections, and sometimes this block can occur depending on how you use FreeTube. Grabbing subscriptions is one of the main reasons that this block happens, so we'll enable RSS automatically if you have a lot of subscriptions, hence why RSS is "forced". In this context, "Bypass connection limit" should still work.

Hope that answers your question.

maboroshin commented 4 years ago

Thank you for the answer to my first question. I understand.

In a metaphor, he changed the code notation to his rules. The weblate commenting feature is poor for discussing this issue.

There are nearly 200 changes. So many to discuss individually. Also, weblate comments are difficult to use. We have to open them all individually.

maboroshin commented 4 years ago

@PrestonN I'm in trouble. These are more than constructive arguments.

Kyotaro is reverting back to a mistranslated version without checking the UI. This is after I explained it.

e.g.

Most of the discussion is about things like code notation and personal preference. He doesn't define right.

maboroshin commented 4 years ago

@PrestonN Kyotaro rpeated misinterpretations of the above. Also discussions like code notation.

He changes "distraction" to "eyesore" over and over again. https://hosted.weblate.org/translate/free-tube/translations/ja/?checksum=4f31aa2fe6ba3241 I don't think that was your intention.

You can read my arguments in English.

maboroshin commented 4 years ago

@GilgusMaximus

It means we will have a discussion on Weblate. But it's been massively from the start.

Rules like code notation will need to be discussed collectively. We've should view all each comments, so the discussions are scattered.

The explanations can also reflect, in part, the intentions of the developers: And, Developers can change the access rights of Weblate.

PrestonN commented 4 years ago

I've taken some time to look into this, and unfortunately it isn't looking too good.

Long story short, there isn't really anything I can do to prevent these changes from happening. Weblate does not offer any method to prevent select users from making changes to translations. The only limiting that I can do would be to lock out every single translation at once, which would obviously punish the other languages that don't have a similar issue.

I don't really have a good solution for this. Even if I leave a comment saying to take your suggestions over their own, there isn't anything I can do to them if they ignore my request.

The only thing we can do is ask Weblate themselves to add some better protections with their service, as it doesn't seem like they provide anything in it's current state.

Unfortunately I'm going to have to close this, as I won't be able to help. Really sorry for the inconvenience.

maboroshin commented 4 years ago

@PrestonN : Thank you for your research. I understand.

There are currently dozens of issues to discuss, and it will take several hours of response to discuss this. Weblate is not suitable for mass discussion (also can't use a picture for reference actual UI); We need 10 windows for 10 comments. A github to integrate this has been closed by the developers. I've probably spent 10 hours on this discussion.

For example, On Wordpress.org we can only do translation suggestions at first, but then we will be granted direct editing rights. If there are no problems, we will then be granted direct editing rights. If this kind of situation happens, we need an administrator.

Finally, I have attempted to report a decline in translation quality. The developer has closed this too.

Ultimately I also decided it was unproductive to spend a lot of time on it. Thank you.

maboroshin commented 2 years ago

In https://github.com/FreeTubeApp/FreeTube/issues/714#issuecomment-1286745418 : @absidue said:

we can't do anything to stop specific people translating. There is nothing we can do from our side. Please complain to weblate directly, not us. We can't fix the problem from our side.

I understand. I also understand some reasons.

There is also the issue of privacy. https://github.com/WeblateOrg/weblate/issues/3105

maboroshin commented 2 years ago

In https://github.com/FreeTubeApp/FreeTube/issues/714#issuecomment-1286807262, @absidue said :

Talking about guidelines, you've clearly not read our contributing guidelines:

Do not include non-free software or modules with your code.

We will not be switching to closed source proprietary translation platforms.

The purpose of this is to protect the free license. For example, using Transifex does not include code. It does not violate the free license. Transifex is the world's largest localization community for open source projects

absidue commented 2 years ago

As clearly stated in our contributing guidelines, we will not be using proprietary software for or in FreeTube. Please respect our projects guidelines. Please stop using multiple issues for the same thing, the other issue was closed because it's for the same thing.

Transifex is closed source, if you can come up with a good platform, that is open source we might consider it, until you do we will be sticking with weblate.

maboroshin commented 2 years ago

@absidue It is not the same issue.

You mandate the use of free software. That's a misinterpretation. Can you include code of Transifex? Many open source software use Transifex or Crowdin. This is because the code does not include them. The code of the EmEditor is not included, even if the contributor uses EmEditor Professional (payware). If you use Windows Notepad, the Notepad's code is not included.

And, Weblate also has a paid plan. These can also be used free of charge.

ChunkyProgrammer commented 2 years ago

Using something that is closed source would be a deterrent to a lot of FreeTube contributors (as we're a privacy respecting application). If you can find another open-source alternative to weblate, feel free to share it and we can look into migrating to it if it's a viable option but I think opening an issue for better moderation tools on the weblate repo and linking to your issues would probably be your best bet. Weblate repo: https://github.com/WeblateOrg/weblate/

maboroshin commented 2 years ago

What is Weblate doing about contributors' privacy? Have you ever investigated this issue?

I was most concerned Weblate about privacy. I am surprised that our email addresses are not protected. So I using a Weblate-only email address. Not explicitly stated. but this leads to the publication of the e-mail address (At 2019): https://github.com/WeblateOrg/weblate/issues/3105

For example, search for the following search terms : Weblate commit "Co-authored-by" . You will see that someone's email address are publicly available.

Open source is not about security. Weblate has published the email address. On the other hand, Transifex and Crowdin are committed to security measures, both physical and virtual. Weblate claims that one or more developers has knowledge about secure software. Weblate encrypt and store passwords. There is little implementation information on Weblate, Please tell me more info page.

(Addition in 2023) There is a Weblate initiative against hacking/spam : https://hackerone.com/weblate?type=team

maboroshin commented 2 years ago

but I think opening an issue for better...

I have already created an editorial problem on Weblate. Including not being able to see old comments. https://github.com/FreeTubeApp/FreeTube/issues/648#issuecomment-1286768296

If you stick to open source, Weblate also has access control features. But access control is a paid feature on Weblate. This is already implemented without creating an issue. Weblate is also a business. Did you request Weblate to make this free? This is the administrator's issue.

maboroshin commented 1 year ago

[REDACTED]

Reason: Offtopic/Spam

maboroshin commented 1 year ago

@FreeTubeApp I will report you to GitHub for the destructive removal of serious comments. To me it looks like an abuse of authority. Please don't repeat.

It also implies intentional neglect.