Clerk assistance requested: - I've blocked Desanimade without tags. Please move the case to Desanimade as they are older than the previous master. All accounts should then be tagged as confirmed except Desanimade. Pinging
Drmies as a courtesy in case they wish to check Desanimade.
Bbb23 (
talk)
13:48, 12 April 2024 (UTC)reply
Oh, shoot,
Bbb23, I didn't see you purposely didn't tag them. Sorry. No, I didn't check them--who cares at this point. It may well be a sock, rather than meat, given the poor quality of their writing, but it's all beside the point. I SALTed the articles they created. See you at the next one, I suppose.
Drmies (
talk)
18:01, 12 April 2024 (UTC)reply
For the sake of completeness, the following are Confirmed:
Erm, hold on a moment. Obviously RubyGillman and Rubygillman722 are the same person. But above,
Mz7 said RubyGillman was Unrelated to Desanimade, while
Dreamy Jazz blocked and tagged them as confirmed to Desanimade. What's going on here?
Spicy (
talk)
22:42, 19 May 2024 (UTC)reply
According to the CU data, the link between RubyGillman and Rubygillman722 using CU evidence is not as clear cut. I wouldn't call the link unrelated, but maybe more unlikely. My feeling is that either some proxy use was going on that isn't being indicated by bullseye (which would make the difference in CU data explainable), or that this sockmaster saw the previous report and made a new account in an attempt to get that account ignored as being the similar to the unrelated account.
Dreamy Jazztalk to me | my contributions23:41, 19 May 2024 (UTC)reply
@
Dreamy Jazz and
Spicy: RubyGillman is currently tagged as "confirmed by a CheckUser"
[7] and is also blocked using {{checkuserblock-account}}. I'm assuming that was a mistake and that we should have used "suspected" instead. My two cents is that, given the lack of a technical match, there is not enough evidence to block RubyGillman, which is why I originally closed that case without action. The only behavioral overlap is interest in the movie
Ruby Gillman, Teenage Kraken, which two separate people could be interested in. It is true that, in addition to the username similarity, both the sockmaster and RubyGillman have tried to add content speculating about a sequel:
[8][9], but I would point out that several other users have apparently been edit-warring over this same content
[10][11], so this isn't a big smoking gun to me. My personal feeling is that the RubyGillman account is somebody else and that the behavioral similarities are coincidental. (To be clear, the Rubygillman722 account is definitely Desanimade based on both behavioral and technical evidence.)
Mz7 (
talk)
03:51, 20 May 2024 (UTC)reply
I see what has happened. I tried to block the account in this report, but SPI helper preselects the most recent report. I then used the form for the wrong case and then blocked without noticing the difference.
Clerk assistance requested: - I've blocked Desanimade without tags. Please move the case to Desanimade as they are older than the previous master. All accounts should then be tagged as confirmed except Desanimade. Pinging
Drmies as a courtesy in case they wish to check Desanimade.
Bbb23 (
talk)
13:48, 12 April 2024 (UTC)reply
Oh, shoot,
Bbb23, I didn't see you purposely didn't tag them. Sorry. No, I didn't check them--who cares at this point. It may well be a sock, rather than meat, given the poor quality of their writing, but it's all beside the point. I SALTed the articles they created. See you at the next one, I suppose.
Drmies (
talk)
18:01, 12 April 2024 (UTC)reply
For the sake of completeness, the following are Confirmed:
Erm, hold on a moment. Obviously RubyGillman and Rubygillman722 are the same person. But above,
Mz7 said RubyGillman was Unrelated to Desanimade, while
Dreamy Jazz blocked and tagged them as confirmed to Desanimade. What's going on here?
Spicy (
talk)
22:42, 19 May 2024 (UTC)reply
According to the CU data, the link between RubyGillman and Rubygillman722 using CU evidence is not as clear cut. I wouldn't call the link unrelated, but maybe more unlikely. My feeling is that either some proxy use was going on that isn't being indicated by bullseye (which would make the difference in CU data explainable), or that this sockmaster saw the previous report and made a new account in an attempt to get that account ignored as being the similar to the unrelated account.
Dreamy Jazztalk to me | my contributions23:41, 19 May 2024 (UTC)reply
@
Dreamy Jazz and
Spicy: RubyGillman is currently tagged as "confirmed by a CheckUser"
[7] and is also blocked using {{checkuserblock-account}}. I'm assuming that was a mistake and that we should have used "suspected" instead. My two cents is that, given the lack of a technical match, there is not enough evidence to block RubyGillman, which is why I originally closed that case without action. The only behavioral overlap is interest in the movie
Ruby Gillman, Teenage Kraken, which two separate people could be interested in. It is true that, in addition to the username similarity, both the sockmaster and RubyGillman have tried to add content speculating about a sequel:
[8][9], but I would point out that several other users have apparently been edit-warring over this same content
[10][11], so this isn't a big smoking gun to me. My personal feeling is that the RubyGillman account is somebody else and that the behavioral similarities are coincidental. (To be clear, the Rubygillman722 account is definitely Desanimade based on both behavioral and technical evidence.)
Mz7 (
talk)
03:51, 20 May 2024 (UTC)reply
I see what has happened. I tried to block the account in this report, but SPI helper preselects the most recent report. I then used the form for the wrong case and then blocked without noticing the difference.