Re^2: Fast efficient webpage section monitoring

Hi,
I should have thought to say: this is not an auction or such, it is a website that I perform translation on, and basically, translations are handed out on a "first come first served" basis. There is no mention of automation in the ToS (which is public, located at legal/translator-agreement on their website : gengo.com if you care to verify).
Now, I understand if you consider it foul play to automate the accepting of translations, but the way I see it, is that I am located in Europe, and the servers seem to be in the US (according to geomaplookup.net) which I would expect gives people there a technological edge (to transfer the page it takes my browser 4.4 seconds) not very different from the one scripting the response would give.
The reason I took to writing this in perl is because there are other conditions to verify (several translations might appear and I want to chose the "best" one in that case, I am using HTML::Treebuilder to work through the html), and having tried in javascript I found it was too far out of the little I know about the language. I feel more comfortable in perl although I am by no means experienced with it.
As I said, I understand if people are not happy helping with this. It is not a very big deal for me, I am just using this as a "project" to practice my programming, as much as anything else. Although I do believe this is perfectly legal and fair.
Thank you for your input.

Comment on Re^2: Fast efficient webpage section monitoring

Replies are listed 'Best First'.
Re^3: Fast efficient webpage section monitoring by Your Mother (Archbishop) on Apr 02, 2016 at 18:00 UTC
I toured the site a bit. It seems to be a pay-for-play service. How are you finding free translations there?	[reply]
Re^4: Fast efficient webpage section monitoring by Marcool (Acolyte) on Apr 02, 2016 at 18:18 UTC
Oh I am a translator, not using it for translation.	[reply]
Re^5: Fast efficient webpage section monitoring by Your Mother (Archbishop) on Apr 02, 2016 at 18:58 UTC
That seems to make this a service auction site, essentially, and you are a seller / sub-contractor competing with others. I can appreciate the networking predicament / handicap but still, it feels like cheating; cheating for money. And if the handicap really is only network roundtrip speed then, as you already noted, scripting will not fix the issue. It will only remove the human response time from the equation; the cheat. I would contact the company and see if they have options to help you. Or ideas to ameliorate this kind of handicap for their translators like baking in self-adjusting throttling based on ongoing trip times. If you're bent on doing it the bent way, as it were, WWW::Mechanize::Firefox is probably the direction you want, not LWP stuff. Ajax messages will (almost certainly) be faster than full HTML pages.	[reply]