[opensource-dev] in-viewer translation is dead soon.

[Marc Adored]

I think the reason you think some book(s) might be more then what SL
would do to google translator is because you have no idea how much
text chat traffic SL has. It is way more text then and whole series of
books could have every few minutes really. I dont think anyone has
said it was SL that has caused google to do what its doing but merely
has contributed to it. Also what you need to understand is you
translating a book is 1 or 2 requests or a few more depending but SL
is a new request every line of text. Its much easier to handle 1
request with a lot of text then it is to handle tons of small
requests. I think googles problem is with the abuse like there
statement says but the abuse came from no regulation. One thing I am
not sure about is why google is just shutting it down instead of
making the throttling permanent...

On Sat, May 28, 2011 at 11:52 PM,  <aklo at skyhighway.com> wrote:
> Hey Everybody,
>
> i don't know if i misunderstood or not, but are you really talking about
> Google translation services particularly picking on SL access?  All the
> mail sounded to me like it was more of a policy decision at Google
> affecting everyone everywhere?
>
> It seems to me that way worse abuse has been stuff like i should be
> ashamed to admit, people like me stuffing through whole books from foreign
> languages into the translator for our classes.  It seems like if Google is
> complaining about stuff the few thousand one-liners from SL in a day
> aren't that much compared to even one of the books i uh, "know about."
>
> Actually, considering what SL is and all that, you'd think Google would be
> into supporting it.  What am i missing?
>
> - AK
>
> ================================================
>
> I think the main issue here is abuse due to bad coding. The real
> discussion should not be who it needs to move to or what other service
> can be abused next it should be how do we write better code to lesson
> the burden on whatever service we use. Secondlife has a LARGE userbase
> therefore any usage will be great but what can we do to make that
> usage more efficient.... Just think... right now every user who has
> machine translation enabled for google is translating every line of
> text they read. Even if someone else already translated it. Thats
> thousands of queries per second. None of that load makes any money for
> google or microsoft for that matter. So the service being abused on
> top of no revenue is kind of a slap in the face. SO maybe some thought
> into making the code a little better should be done first. Maybe some
> type of central caching service... I know security issues security
> issues but I am just throwing out ideas. Because to me 1500 different
> people translating the same line of text is just abuse and retarded.
> Maybe some kind of central proxy from secondlife can be setup so if
> the same line of text is queried it just spits out the translation
> thats cached to them. The cache lifetime should be short for security
> purposes but caching a translation for 5mins should be plenty of time
> for everyone receiving that text to get the cache translation. Just
> think of how much of a burden that will remove from google. I know it
> will put more of a burden on a secondlife server somewhere but not
> that much because its just spitting out cache its not like its
> translating any text or anything just serving cached data. You could
> even tell each TPV that if they want to offer translations they have
> to setup some type of caching. Hell it could probably even be some
> simple proxy with a decent cache time setup. I don't know the
> specifics but I know it can be done better. Sadly what has happened
> here is what happens when you don't put limits on a service. Crappy
> code is written and the service is abused. I am sure that google
> simply throttling the api will make quite a bit of better code emerge
> from the depths... That may even be Googles plan and why such a long
> period before its shut off completely. SO maybe the thought pattern
> should be "how can we do what we're doing better" instead of "who can
> we jump ship to next and abuse" Because like others have said google
> is a very big company, bandwidth is very easy to come by for them so
> if we are hurting them then its going to be worse for others. No body
> is better suited for such a task then google. Just my $0.02 :)
>
> On Sat, May 28, 2011 at 9:32 AM, Daniel <danielravennest at gmail.com> wrote:
>> > The problem as pointed out by Tateru Nino on her blog is that Google is
>> > huge, and their
>> > users will "fail over" to other services like you are suggesting,
>> > causing them to get overloaded
>> > also.  In that case, they may also decide it is too expensive to stay
>> > open, causing a chain
>> > reaction.
>> >
>> > Note that Google is not closing off all translation services.  They are
>> > moving to using the
>> > Translate Element within web pages (
>> > http://translate.google.com/translate_tools ).  I assume
>> > the reason is a freestanding translator page does not bring in any
>> > revenue, while a web page element
>> > on pages that carry their adsense ads increases how many of their ads
>> > can be read by people around
>> > the world (ie makes money for them).
>> >
>> > The question is can you incorporate that web element as a substitute for
>> > what you are using now?
>> >
>>> >> From: "Philippe (Merov) Bossut"<merov at lindenlab.com>
>>> >> Subject: Re: [opensource-dev] in-viewer translation is dead soon.
>>> >>
>>> >> Hi,
>>> >>
>>> >> It shouldn't be too hard to substitute with another service. Someone
> has an
>>> >> alternative service to propose?
>>> >>
>>> >> Cheers,
>>> >> - Merov
>>> >>
>> >
>> > _______________________________________________
>> > Policies and (un)subscribe information available here:
>> > http://wiki.secondlife.com/wiki/OpenSource-Dev
>> > Please read the policies before posting to keep unmoderated posting
> privileges
>> >
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
>
>