Block evasion edit

@Czar: @Ivanvector: Why is nobody doing something about it? 178.40.152.153 was blocked (and still isǃ

This IP address is currently blocked. The latest block log entry is provided below for reference: 15:24, 19 November 2019 Ivanvector talk contribs blocked 178.40.152.153 talk with an expiration time of 1 week (anon. only, account creation blocked) (Edit warring)

and evaded the block as 78.98.54.148 (other IPs previous to the block include 178.41.129.82 and maybe others). As I stated elsewhere,

Now this happened. I suspect that's the IP (the IP block also included the account creation block; and if that's really the IP, it violated that one too). The IP stopped editing or replying me and now suddenly there's this user, created seemingly on 23 November 2019, who supported the IP's edits. I'm afraid it's a sockpuppet of the IP, who isn't showing any good faith anymore, despite me explaining it to self-revert and notify the block evasion (why didn't anyone replied me here yet?

This is further proof Symes2017 is the blocked IP as the IP told me about "nominat[ing] this article for a peer review" here.

I wish the IP would have created an account, but this wasn't certainly the way to goǃ We have disrupting beahvior such as block evasion, edit warring multiple times while blocked and now sock puppetry as the blocked IP first evaded the block as 78.98.54.148 and now created an account when still blocked. All of this could have been avoided if the IP listened to me and my plea, not editing for the whole duration of the block and not doing what it did.--Davide King (talk) 12:17, 24 November 2019 (UTC)Reply

Registered edit

This user is now editing as Symes2017 (talk · contribs). czar 19:13, 24 November 2019 (UTC)Reply