4 ms·
> They are all happened on the product server, not on staging server. I understand that this is mass destruction of our work and explicit violation to the Mozil
by barbazoo 1y ago
> They are all happened on the product server, not on staging server. I understand that this is mass destruction of our work and explicit violation to the Mozilla mission, allowed officially.
Could this have been a mistake rather than a malicious act?
- alcide 1y agoMozilla has offered to call the OP, too. I’m curious on the outcome.
- benatkin 1y agoThey said sorry for how you feel about it which is insincere and unhelpful.
- Incipient 1y agoMy partner has been picking me up on the specifics of wording. Is there a slightly different phrasing that would make this better, or is it the sentiment that's crap? "I'm sorry for how these changes impacted you"? Personally just the sentiment feels insincere to me haha.
- pseudalopex 1y agoThe sentiment is more important. But I'm sorry for how you feel suggests to many people the sole problem was their feelings. I'm sorry for how these changes impacted you suggests the changes could have been wrong.
- mewse-hn 1y agoI don't think it's the specific phrasing. They could have said "I'll contact you by email to try and understand your concerns" and it's still dodging the explicit, concrete list of grievances. However, "let's hop on a call" is just additionally dismissive.
- 4bpp 1y agoTwo things stand out, besides what has been already mentioned. * The infantile corporate-cutesy wording "hop on a call" is not appropriate when talking to somebody who feels that you deeply wronged them. It has the same vibes as cheery "Remember: At Juicero, we are all one big family!" signatures on termination notices, and Corporate Memphis. * In the first sentence, Kiki says "about the MT workflow that we just recently introduced". Why is this level of detail shoehorned in? Everyone in that conversation already knows what it is about. It's as if Kiki can't resist the temptation to inject an ad/brag about their recently introduced workflow for any drive-by readers. "I'm sorry you were dissatisfied with your Apple(R) iPlunger X(TM), which is now available at major retailers for only $599!"
- petre 1y agoThe response was likely also written by AI so there is no point analyzing it. It just ads insult to injury.
- kentm 1y agoDon’t use passive voice in an apology. “We’re sorry that we made the change without consulting your team or considering your circumstances.” The change did not fall out of thin air. It was something they did. If they do not own it explicitly then it’s insincere full stop.
- crazygringo 1y agoHow? They don't know what exactly has gone wrong. All they can say sorry for is for how the person is feeling. Then they want to get on a call to learn more. Which is the start of helping. The response is as sincere and helpful as it could be for an initial response from someone who wants to figure out what the problem is.
- rileymat2 1y agoBut he lists the problems? Pretty unambiguously.
- crazygringo 1y agoThe problems are nowhere near actionable. A lot more information is needed. E.g. literally the first bullet: "It doesn't follow our translation guidelines". OK -- where are those guidelines? Is there a way to get it to follow them, like another commenter says works? Does the person need help following the process for that? Or is there a bug? Etc. These are the things a call can clarify. It's the necessary first step, so why are people complaining?
- BrenBarn 1y agoThey are actionable by entirely canceling the machine translation operations in that community,
- handoflixue 1y ago> where are those guidelines? It's entirely possible that such information is well-known to everyone involved in the translation community. I would consider it outright insulting if someone who ostensibly "wants to help" doesn't know basic information like that - if the people making decisions about SumoBot are NOT aware of basic information like "where to find the local translation guidelines" then they are presumably not qualified to release a tool like SumoBot in the first place.
- kentm 1y ago
- deleted 1y ago[deleted]
- layer8 1y agoThe third, more likely option is that it was a careless act. Clearly a mistake in any case.
- small_scombrus 1y agoWhat's the saying? > Never attribute to malice that which is adequately explained by stupidity.
- bob1029 1y agoAt some point the rate of stupidity becomes suspicious again.
- omoikane 1y agoIf this was a mistake, the proper response might have been "sorry, we applied automation in error, those changes have been rolled back while we fix the process that allowed it to happen". And not "call with us to talk about this further".
- move-on-by 1y agoAt the very least, ‘we will discuss how this could of been handled differently’, not I’m sorry you feel this way.
- detaro 1y agoThen say so if someone complains about it? "Shoot, we accidentally ran it in the wrong mode, sorry about that, I'll look into someone fixing it ASAP" is a lot better than "We're sorry for how you feel".
- drtgh 1y agoBy one side, we all know[1] that automated translations are always inaccurate, and this is specially deep with translations into languages like Japanese. On the other hand, we all know that LLMs are guaranteed to introduce an error in the result, therefore always needs human supervision. Also there are other details like the 72 hours timeframe they comment... Therefore, to me, introducing LLMs without designing them just as an usable tool (UI/UX) to support the work -of the volunteer community- doesn't sound like a mistake, but sounds like an "I don't care at all, get out of the way". [1] who speaks more than one language at least.
- charlieyu1 1y agoThe damage is done when the mistake was allowed to happen.