devtrackers.gg
As most people have identified, this looks like the owner was back in control of the account, but the hijacker had set Authenticator which was still active. It's possible that the person Tweeting was the Auth setter but didn't have the current pass, but less likely because the owner can just set a new pass if they wanted to.
Often a 'hijacking' is actually a share gone wrong, and although I'm not saying that is the case here, it is common for 2 different friends to look quite similar in an account history, especially if they live close to each other.
It's not always really clear if we should remove the Authentication, as sharers often ask for the other sharer to be removed - and as there is no way for us to verify who someone is on Twitter, the advice to remove the Auth would guarantee that the person doing so has access to the active recovery email.
In fairness, although the advice is sound, we could have been a little clearer in our response, so we'll take that on board for the future.
I thought Jagex would ban the account if there is an account dispute like in your explanation. Given that Jagex is unable to tell who the actual account creator is and the fact that account sharing is still officially against the rules.
I understand that Jagex doesn't actively enforce the account sharing rule and uses a "common sense approach", but the situation you're describing doesn't seem to fit that criteria.
Maybe I misunderstood what you're saying. It just seemed that Jagex only looks at one specific thing instead of the entire situation.
I'm also hoping that Jagex doesn't just deny the 'fraudulent' appeal from this 'friend' but also cleans up the account if possible. It think it's important to clean up accounts where possible. We shouldn't remain vulnerable and be unlucky if another JMod decides otherwise and accepts a future recovery appeal.
Thanks for your considered post. We do undertake an element of account cleaning in clear cut hijacking situations, but it's also a fine balance between trying to make the account less open to malicious recovery, and making it so that it can never be recovered because of the depth of cleaning. Clear hijackers are always cleaned off, but if an account has (say) 3 passwords and all 3 are known by somebody else (so we clean them), that could make future recovery a real challenge for the genuine owner.