Help - Search - Members - Calendar
Full Version: "Free content" but not on free computers
Wikipedia Review > Wikimedia Discussion > General Discussion
Abd
So an IP editor walks into a bar. I.e., into a block.

This meta discussion is a nice example of how the Wikipedia operating core has lost the vision.

If "anyone" in "the encyclopedia that anyone can edit," includes people who access the internet with school or library computers, it's pretty much a lost cause.

71.41.38.234 (T-C-L-K-R-D)
global contributions

The IP has edits on various wikis other than en.wiki:
Commons: two edits, no vandalism, no blocks.
es.wiki: 96 edits, no blocks.
meta: 2 edits, no blocks.

Then en.wikipedia: 498 contributions. I see roughly 64 warnings. I have not classified the edits into sessions, but sessions obviously exist. See four edits in the period 20:14 to 20:33 on February 1, 2010.

February 6, an edit that is good faith. Very possibly a child. I see a lot of edits from the IP that look like how children edit.

(I managed the case of an apparent 7-year-old who was editing Wikiversity, who was creating many accounts. Turns out some of these accounts were "vandalizing" Wikipedia and other wikis. I was able to guide the kid into doing his creative writing in user space on Wikiversity. The "vandalism" may have ceased. To a kid, writing your name on a wiki page is just doing what comes naturally. He was mostly using his school computer, apparently. blocking him would have meant blocking his school. But there was really no need to block this kid, just to engage him, and since part of the mission of Wikiversity is education, I did so. From what I've seen, looking around, he's writing more coherently. Normal development, but this is a smart kid.)

What I see coming from the IP is consistent with a public library. A floating home IP probably would not have so many edits.

Treating the IP as if it were a single editor (i.e., escalating warnings) is a very weird approach. On Wikiversity, I've taken to blocking IP vandals without warning, medium block length, i.e., a week. Seems to work. The talk page is left open so someone can complain if it's a problem. Doesn't happen (i.e., no complaints). I also block named accounts that begin with blatant vandalism, as distinct from what might be clumsy edits or test edits. Indef. But talk page open. My reason? Well, if they want to do some legitimate work, would they want the first edits to be vandalism? No, and if they want to use that user name, wait a while, and then ask for usurpation!

I'd be interested to hear from others on this.

Text
The situation can be anywhere from 1 IP = 1 PC = 1 User, to X IP = Y PC = Z Users.

Generally, in a library, it's 1 IP = X PC = Z Users, or maybe X IP = X PC = Z Users.

As long as there are Z Users, the whole system gets blocked. There is no filter which can tell which user of the Z pack is vandalizing. The only method is notifying the owner of the library, who then identifies the vandalizer, and then kicks him/her out.

This stuff has happened many times. Check Template:Checkuserblock-Synetrix and Template:Checkuserblock-Alto.

"You must use a stable email address issued to you by your ISP, school, employer or similar organization so that we may verify that you are a legitimate user. Free email accounts (like Yahoo! mail, Google mail, or AOL) are easily obtained and abused and requests from such addresses will not be honored."

What would the motivation to edit be, if the above would have to be respected?
EricBarbour
Meanwhile......

ProcseeBot is still blocking thousands of alleged open proxy IP addresses every day.
At least, they think those are proxies. (Did you know that ProcseeBot is an administrator?)

And TorNodeBot is auto-blocking hundreds of alleged Tor traffic nodes every day. (Yes, it too is an administrator.)

If the fools keep this up, I calculate they will have blocked the entire Internet....in about 1900 years.
Abd
QUOTE(Text @ Sat 12th November 2011, 9:21pm) *
The situation can be anywhere from 1 IP = 1 PC = 1 User, to X IP = Y PC = Z Users.

Generally, in a library, it's 1 IP = X PC = Z Users, or maybe X IP = X PC = Z Users.

As long as there are Z Users, the whole system gets blocked. There is no filter which can tell which user of the Z pack is vandalizing. The only method is notifying the owner of the library, who then identifies the vandalizer, and then kicks him/her out.

This stuff has happened many times. Check Template:Checkuserblock-Synetrix and Template:Checkuserblock-Alto.

"You must use a stable email address issued to you by your ISP, school, employer or similar organization so that we may verify that you are a legitimate user. Free email accounts (like Yahoo! mail, Google mail, or AOL) are easily obtained and abused and requests from such addresses will not be honored."

What would the motivation to edit be, if the above would have to be respected?
Right. If you are poor, you have only free email and free access at a place like a library. The edits coming from such an IP are generally representative of the population of the poor (plus others, such as real vandals and other disruptive editors who have been blocked from using their regular paid access).

Looking at the cross-wiki edits of the IP that was blocked for a year, none of the non-Wikipedia edits were disruptive. I did not examine all the WP edits, but many were not disruptive. So many are being blocked because of the actions of a few. This is being made necessary, partly, because of the rejection of Pending Changes. A more efficient method of reviewing Recent Changes -- which is astonishingly inefficient, but the cost of it is spread out so that individual editors don't really feel the pain -- could make it possible to filter out the bad stuff, quickly. It usually takes more time for most to make even a vandalism edit than it takes for a skilled editor, using assisted editing tools, to scan it and reject it.

Further, in connection with the Self-Reversion proposals, I suggested years ago reversion by bot. That was intended to enforce topic bans, i.e., there would be a list of topic banned editors, with, for each, a list of articles -- or article categories -- that they are not permitted to edit. Each to maintain, enforces a ban, and then allows editors to make reasonable suggestions even if banned, without a block being necessary.

And that could be done with IPs, which would only be hard-blocked for edits that create serious problems.

This would work fine with library IP. The reversion notice would explain, and editors who want to rescue this stuff could review it at leisure. Basically, the bot would create a log, and respected users could check off each entry as reviewed.

Wikipedians rejected Pending Changes because .... none of those voting, who were accorded any respect, were IP editors. The "free content" goal is lip service, not the provision of real access to people without funds.

In working with image licensing issues, I found that the deprecation of "fair use" arguments (it's considered that fair use reasons must be strong) was based on "free content." It's a misappropriation of the term "free." A fair use rationale would apply to any site copying the content for non-profit purpose. "Free use" really refers to "free for profit-making re-users," because they may, indeed, need a stronger rationale.

"Free" sounds great, though. Yeah! It should be Free!

Case in point: Wikiversity users, students, as a class assignment, upload a photo of themselves. They don't want anyone and everyone to be able to republish their photo. They can't put it on Commons, because Commons content must be "freely" usable. Now, there is a rationale for allowing fair use of photos in such a situation, it's the development of community. But the WMF and our local EDP don't allow fair use in user space. Which is crazy. That's not the content that would normally be re-used, it's quite reasonable to allow extensive fair use in user space. That would allow users to develop work without having the license police looking over their shoulders. So I started a Wikiversity:Assembly topic to examine the issue. The Assembly will be slow, but it's intended to be careful and thorough, and to develop reports on topics, to advise the community (and others).

However, the moves from meta to establish and enforce global bans, I see as a major storm cloud gathering on the horizon. Without any rational justification, it is becoming possible for Wikipedians, massing at meta, to arrange the declaration of a global ban, to be enforced at all wikis. Oh, reasons will be given. But there is no end to the possible invented reasons, and people who dominate and control others always have reasons.

While this is starting with Poetlister as poster boy, it can and will be applied to other "undesirables." It's more than a toe in the door, it's a whole jackboot.
Abd
Ottava Rima dove into this one, claiming that the IP notifying meta about a login problem is a banned editor. The new discussion.

The checkuser blocked the account, calling it a checkuser block, but shows no sign of understanding that it's a public computer. Perhaps a banned user did use that computer, more than once. It wouldn't be surprising at all. But the bulk of contributions from that IP don't seem related to each other, and the picture gets stronger if we look cross-wiki.

Ottava's always calling for someone to be blocked or banned. Seems to happen every day. It's become obvious that he wants to be banned himself, he's been pretty explicit about this, writing about the Poetlister ban. He's arguing for strict enforcement of all bans, globally. I think he wants to make it happen that he can't edit any WMF wikis any more. Why, I don't know, though he may be sensing something about his editing.... he did sense that before, apologized here, and stopped editing for many months.

Then he came back and returned to the same patterns.
The Joy
But... but... Wikipedia loves libraries! dry.gif rolleyes.gif

http://en.wikipedia.org/wiki/Wikipedia:Wik...Loves_Libraries
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.