WARNING! This plugin can generate huge unexpected charges. In seems to check every post to detect its language and that can add up to $$$. We were surprised by a $1000 charge by Google, maybe something the developers might want to keep in mind.
That’s a huge surprise! How many posts do you have?
1개의 좋아요
We have a rather big community, however the charges were not for actual translations, but for checking the language of each post. It seems the plugin will automatically check every post when a user views it. It sent about 50k such requests in less than a month 
1개의 좋아요
They charge $20 per million characters, which suggests you sent 50 million characters across the API, does that sound about right?
Whoever set this up would have been notified about charges and AFAIK translate is included in the services which qualify for $300 in free usage? Did they just “set it and forget it”?
1개의 좋아요
I haven’t looked into the character counts, sounds quite a lot. We do have topics with thousands of fairly long posts, so that might be accurate.
We haven’t received any notifications until the charge actually occurred and we’re over the free trial usage, we already have other services from Google Cloud.
Hopefully we’ll get a refund, just a caution notice for anyone using cloud services for this and in general, it feels a bit like the kid calling porn numbers 
3개의 좋아요
Fingers crossed, but they do make their API rates clear at the point of activation, so from their perspective they would have no reason to do this. The costs are right below the Enable button.
I would review who has access to the console and /admin if you have people turning on chargeable features without first estimating costs and seeking approval.
Apparently they do one off refunds, subject to investigation and bla bla bla…
The problem is just the plugin will run these language detections and it actually sends the whole content to check the language and see if a translation is actually needed. Most of our users are English speakers so very few (if any) actually translated the posts.
I think this language detection should be disabled (or disableable) or at least it should only send a small chunk of data.
1개의 좋아요
I think if this was a built in problem resulting in huge charges on every post load we would have others reporting it?
API v2 from Google is a paid tier, but they have API v3 that is free. Can the plug-in be migrated to v3 for Google as it was migrated to v3 from Azure?
The pricing page states that language detection in v3 uses the same prices as v2. However,
Google does not charge extra for language detection when you do not specify the source language for the
translatemethod; the Language Detection price applies todetectmethod calls.
Migrating the plugin to have category- or forum-level expectations of language and leaning on this might be better?
2개의 좋아요
Thanks for the clarification. It does seem that v2 has two charges, language detection and then text translation. v3 is charged for language detection, but text translation is free. So all things being equal, v3 is, at most, half the cost of v2. For that alone I think v3 would be the better choice.
As for going completely free, I do agree that having the ability to set a category-level language would be a great feature.
We can accept a PR with support for API v3. pr-welcome
4개의 좋아요
구글의 티어별 가격 정책 업데이트 안내.
Google Translation API 고객님께,
가격 구조를 단순화하고 더 많은 고객이 무료 사용 혜택을 누릴 수 있도록, 2019년 11월 1일부터 Cloud Translation API v2 및 Cloud Translation API v3의 가격 구조를 변경합니다.
알아두어야 할 사항은 무엇인가요?
현재 Translation API v3의 가격 정책에는 매월 텍스트 번역(SKU E205-31DB-F1F4)의 첫 50만 자에 대해 무료 티어(비용 없음)가 포함되어 있습니다. 2019년 11월 1일부터 무료 티어를 $10 사용 크레딧(텍스트 번역 50만 자와 동등한 금액)으로 대체하며, 이는 매월 고객님의 청구 계정에 적용됩니다.
사용 크레딧은 다음과 같습니다:
- 매월 청구 계정당 1회 적용됩니다.
- Translation API v2 및 Translation API v3의 기존 고객과 신규 고객 모두에게 적용됩니다.
- Translation API v2와 Translation API v3 모두에서 사용할 수 있습니다.
- 아래에 나열된 대상 SKU에 적용되며, 사용량 조합에 관계없이 최대 $10 한도 내에서 이 크레딧에서 차감됩니다. 한도를 초과하는 사용량은 정상 가격대로 청구됩니다.
- 사용하지 않은 크레딧은 이월되지 않으며, 매월 초기화됩니다.
- Translate의 SKU 설명에 표시되지 않습니다.
5개의 좋아요
잠깐, 벌써부터 헤매고 있어요.
지금 이 토론 내용을 다시 정리하면:
- 평소 사용하던 무료 google.translate로는 동시 처리(crowding) 능력이 부족합니다.
- 유료 API를 통해서만 번역이 가능한 건가요? 그렇다면 예를 들어 경쟁사로부터 공격을 받는다면 어떻게 되나요?
- AWS 번역 서비스를 사용할 수 있나요?
1개의 좋아요