Last modified: 2013-08-22 14:38:35 UTC
https://www.wikidata.org/w/index.php?title=Wikidata:Administrators%27_noticeboard&oldid=47599283#Should_we_block_10.64.0.127.3F https://www.wikidata.org/wiki/Special:Contributions/10.64.0.127 https://noc.wikimedia.org/conf/highlight.php?file=squid.php --- # eqiad '10.64.0.123', # cp1001, API '10.64.0.124', # cp1002, API '10.64.0.125', # cp1003, API '10.64.0.126', # cp1004, API '10.64.0.127', # cp1005, API '10.64.0.128', # cp1006 ---
Raising the importance of this bug as false attribution is a major issue. It can lead to horrible misunderstandings (cf. <http://wikipediocracy.com/2013/04/22/busy-day-at-the-wikimedia-foundation-office/>), in addition to dramatically undermining the credibility of page histories.
Just noting that it's currently blocked via AbuseFilter (out of fear that using a standard block could disrupt things). See https://www.wikidata.org/w/index.php?title=Special:AbuseLog&wpSearchFilter=23 for hits.
CC'ing Ariel, in the naive hope that I've picked the right ops person. :)
Adding Aaron, we discussed this yesterday and some emails went around today about it. One thing to bear in mind about the edits via IP is that it's extremely unlikely that bot bot actually logged out for those edits; you can see for http://www.wikidata.org/wiki/Special:Contributions/Rezabot if you go back a bit that some of the IP edits are right in the middle of the stream of logged in edits.
(In reply to comment #1) > Raising the importance of this bug as false attribution is a major issue. It > can lead to horrible misunderstandings (cf. > <http://wikipediocracy.com/2013/04/22/busy-day-at-the-wikimedia-foundation- > office/>), > in addition to dramatically undermining the credibility of page histories. I'm sure monitoring the rubbish on that site is a high WMF priority.
(In reply to comment #5) > I'm sure monitoring the rubbish on that site is a high WMF priority. Don't be silly. :-) It isn't about that site or its rubbish. It's about the integrity of page histories and edit attribution being compromised. This is bad for a number of reasons, not the least of which is that it can easily create misunderstandings (as demonstrated very clearly by that particular blog post).
Hmm, I see gerrit never picked up https://gerrit.wikimedia.org/r/#/c/66130/
Related URL: https://gerrit.wikimedia.org/r/66718 (Gerrit Change I350aca72c7a96ba3ec727324800612fc84e0e7a4)
Related URL: https://gerrit.wikimedia.org/r/66722 (Gerrit Change I350aca72c7a96ba3ec727324800612fc84e0e7a4)
Looks like Aaron's patches got merged but the Gerrit bot did not paste a notification here. Closing as FIXED.
