Thanks for your response, Łukasz! What I'm most impressed about at this stage is that at least some translation companies are aware of this problem. I am by no means the only person this has happened to, and will not be the last, but it is good to know that companies will make the effort to verify a translator's identity.
Łukasz Gos-Furmankiewicz wrote:
While you can't just hack into the account (it's kinda like burglarising a burglar to get your stuff back: you shouldn't really but you'll go to jail for it)
I know, right? I don't think I would stoop to that level, but believe me, I am certainly tempted by the idea. In the end it wouldn't actually solve anything, however - someone else might just open up another account with sarai_pahla and we're in the same situation all over again...
Łukasz Gos-Furmankiewicz wrote:
you can probably address Google with the problem.
Google's policy states that they do not intervene in cases of impersonation, for various reasons.
Łukasz Gos-Furmankiewicz wrote:
You might want to get a non-free e-mail address or at least an alias and put up a general disclaimer on your website and other profiles for people to check headers instead of taking the signature e-mail for granted (any kid with access to PHP can sign off as any e-mail address, including
[email protected]), plus the same in your ToS.
Yep, I have a non-free email address already and am adding the relevant data to my various profiles and to my website in between getting work done.