Skip to main content
15 events
when toggle format what by license comment
Oct 20, 2020 at 16:31 comment added Stephen Just from a practical standpoint, I don't think it would be necessary to detect users on the same keyboard because there is precedent for actions undertaken 'by someone else using my account', which I feel answer that aspect of the question. What about a concrete example where we know that a user cannot possibly be the same person that created the account (suppose stackoverflow is operating 250 years in the future and the account has a similar age, unless natural human lifespan also increases to that milestone, we can safely assume a transfer has happened)
Oct 20, 2020 at 5:57 history edited Stephen CC BY-SA 4.0
added some additional scope to the question
Oct 20, 2020 at 4:22 comment added Rob Is it possible to detect different users at the same keyboard?: Yes and Yes. If your question is solely about "SE using detection": SE tries to detect: meta.stackexchange.com/a/231893/282094 (not very clear about it), but ultimately, impersonation is not allowed.
Oct 20, 2020 at 0:41 comment added Rob Except in the case of a single instance of actions by an Executor, it's forbidden - so this question is a dupe of this or that.
Oct 19, 2020 at 23:48 review Close votes
Oct 20, 2020 at 6:03
Oct 19, 2020 at 23:46 comment added Martijn Pieters @SonictheMaskedWerehogi think you meant to link to stackoverflow.com/c/charcoal/a/4/114 there; I know those two posts are cross-referenced, but that was confusing for a moment. And I can’t find more info on that alleged case, so can’t investigate further. I have worked with staff on several password-reuse-hijack cases, there are a few specific markers that good indicators that moderators can look for.
Oct 19, 2020 at 23:35 comment added Martijn Pieters @SonictheMaskedWerehog how do you know a willing transfer was made? Have you ruled out hijacking?
Oct 19, 2020 at 23:35 comment added Sonic the Anonymous Hedgehog @MartijnPieters That's generally the most common cause of spam/troll posts coming from high-rep accounts, but that's not always the case. See this post on the Charcoal team for an example case of my comment above.
Oct 19, 2020 at 23:32 comment added Martijn Pieters What I have seen is that accounts that have reused passwords across different sites on the wider internet, are vulnerable to having their account hijacked by someone with access to breached password databases. What usually happens is that the hacker uses such accounts to vote for their own posts, or, in one case, post bounties to be awarded to their own posts. Bad actors are generally not that creative or devious to do anything else with “extra” accounts, TBH.
Oct 19, 2020 at 23:29 comment added bad_coder @SonictheMaskedWerehog those issues are dealt with in posts about SPAM and identity theft, together with abuse of system. Rephrasing the title of the question merely changes the subject to other duplicates. In which case the original question becomes off-topic.
Oct 19, 2020 at 23:25 history edited Sonic the Anonymous Hedgehog CC BY-SA 4.0
Mentioning "inheritance" seems to be making others think of the death case specifically, and this gathered a duplicate vote for that specific case. However, there are other cases too, and so let's refer to the general case
Oct 19, 2020 at 23:22 comment added Sonic the Anonymous Hedgehog I feel that this question is relevant in spam fighting, because we've had a couple cases where a troll user has paid some inactive user with rep to use their account, to then spam and make troll posts without much hindrance. We initially suspected those accounts were compromised, but now we have reason to believe that that's what's happening.
Oct 19, 2020 at 23:21 comment added bad_coder Does this answer your question? How should a user's death be handled?
Oct 19, 2020 at 23:18 comment added bad_coder I can't find a link, but SE has given an official answer in the past about what actions are taken in such instances. Related thread here and also here.
Oct 19, 2020 at 23:10 history asked Stephen CC BY-SA 4.0