Tractor~enwiki

tractor is NOT a logbot. See Wikipedia:IRC channels and m:IRC channels.

Important: A user, tractor may appear on certain IRC channels on Freenode associated with #wikipedia. It is User:CQ (a Human) using his long-established registered freenode nick. See the section, IRC servers and channels below for more information.

This is a Wikipedia user page.
This is not an encyclopedia article or the talk page for an encyclopedia article. If you find this page on any site other than Wikipedia, you are viewing a mirror site. Be aware that the page may be outdated and that the user whom this page is about may have no personal affiliation with any site other than Wikipedia. The original page is located at https://en.wikipedia.org/wiki/User:Tractor~enwiki.

Special account created by Quinobi

updated 08:28, 17 August 2005 (UTC) by CQ

refactoring began 15:10, 15 June 2006 (UTC) by CQ

checking...

deployed 12:57, 23 October 2014 (UTC) by • Q ^#o •

Shortcut

WP:CBTF

Shortcut

WP:NCH

The tractor is an IRC bot and Internet server built by CQ and the Community Builders Task Force that pulls references out of IRC and other chat channel activities, social networks, and online databases, building up an adaptive framework for what it sees. The cumulative relevance, if any is found, is compared against a list of lists. Open content is created, maintained and curated by a non-profit organization, OzoneFarm.

Wikipedia

References are built by linking sets of keywords into context chains to establish a useful presence in tractor's control panel. If no live people are about. Some of tractor's design philosophy and engineering methodology was developed in the Keywords project.

Caution: Very little useful information appears below this line.

Objectives

For Wikipedia to really "gel", a way to more effectively unify an insanely diverse userbase with an ever-expanding world of information ranging from scattered bits of incomplete factoids (stubs ) to jewels of well-formed knowledge (Featured articles) must evolve. For this to take place in a consensus-driven way, could require some fundamental architectural changes. The Portal namespace and Wikipedia:WikiProject schema were steps in the right direction, in my opinion. I think that soon, it will be time for a Project:namespace and some tools for advanced automation of project management tasks. One way to do this might be through a messaging system using bots. (done) • 12:57, 23 October 2014 (UTC)

Wikipedia 1.0 and beyond

The script may oneday be able to assist channel participants while working on Wikipedia articles for validation and certification purposes. The idea is to direct the vehicle's resources toward finding and catalogging a source-focused matrix of trusted sources that can be safely imported into the main namespace via a standards-driven framework that allows Human intervention all the way to the core processes.

Metaphors for traction

Phantom authority, self-selective recruitment and retention of members in virtual communities: The case of Wikipedia by Andrea Ciffolilli
"This paper employs team and club good theory as well as transaction cost economics to analyze the Wikipedia online community, which is devoted to the creation of a free encyclopaedia. An interpretative framework explains the outstanding success of Wikipedia thanks to a novel solution to the problem of graffiti attacks - the submission of undesirable pieces of information. Indeed, Wiki technology reduces the transaction cost of erasing graffiti and therefore prevents attackers from posting unwanted contributions."

#wikipedia #wikipedia-bootcamp #wikiproject

The other metaphors or human-readable mindset is that of the tractor in the locomotive context, where the tracks are IRC channels through which the engine is controlled in real time in an experiential field known only to those who have a frame of reference conversant with the netizenship required by IRC environments such as Wikipedia's chosen "switch yard" - Freenode. Everyone who knows freenode - at least the way I know her - understands that the PDPC is itself a good club with a club good theory. Facts support a realization that there exists between Freenode and Wikipedia an effective partnership of goals and driving principles within a friendly meshing of discourses toward a hopeful future - sustainable in every way - which we shall demonstrate in real time on the real cyberspace in a matter of months.

see http://freenode.net/catalysts and http://en.wiki.x.io/wiki/Wikipedia:WikiProject_Community

Modes and functions

Updated: 19:59, 9 June 2006 (UTC) by CQ after a brief but inspiring IRC exchange with PilotGuy and CommanderKeene in #wikipedia-bootcamp

The tractor (at least for the OzoneFarm prototype) has three modes:

normal (tractor) -- scoped use by a single group with informal protocols
beam (tractorBeam) -- constrained use by a pair of groups - host and guest
hyper (SkyTractor) -- directed use by an organization for policy-driven missions

Some functions in the normal mode might include:

extract and report (IRC channel bot)
crawl and search (database automaton)
verify (reference checking)
track (user activity percentile enumerator)

A couple of existing groups at Wikipedia that might use these might be:

The beam mode allows focused and filtered communications from one tractor-equipped group to another group that may or may not have, need, or want its own tractor. If say, the Wikipedia:Version 1.0 Editorial Team wanted to host one of the two groups above, as a guest group, they can "beam" over a few choice messages that serve as an invite function to "tow in" the other group. The guest group would then have temporary access to the host group's resources (including its tractor) but also subject to its policies. If things don't work out for some reason or the merger is no longer needed, the tractorBeam is simply turned off to effect a split (part) returning guest and host to a normal state.

If, on the other hand, a small but well-developed group wanted to advertise its services and resources to a larger group, network of groups or even the Whole Internet it can switch to 'hyper mode (what OzoneFarm calls its SkyTractor). This is the equivalent of "going public" in Wall Street terms and may be dangerous, could be mission-critical, and should probably require a licence.

...But back down to Earth and Wikipedia...

FreenodeIRC

Conversation between tractor and lilo:

<tractor>	where's the latest policy for using bots on freenode, please?
<lilo>	tractor: please don't send clone or floodbots, op bots discouraged, useful and interesting infobots encouraged, please don't pad our user stats with bots 8)
<lilo>	tractor: did that cover it? 8)
<tractor>	pretty much lilo thanxaheap :)
* tractor ->	#wikipedia bot under development see http://en.wiki.x.io/wiki/User:Tractor
<lilo>	tractor: I'll go look but I'm sure you guys are fine :)
<lilo>	tractor: I get no information from that page so far, other than that you type "tractor: start" and interesting things happen 8)
<lilo>	tractor: knowing the well-deserved reputation of Wikipedia, I'm not worried :)
<tractor>	lilo: The "well-deserved reputation of Wikipedia" was way too kind of you, but Thanks for the VoC ;)
<lilo>	tractor: I'm going to stand by my characterization grin
<tractor>	hehe. me too

Abstract

The theory of Cyber-traction is based on goal-seeking tendencies of consensus-driven processes. The tractor invention is a test of real-time constraints observed in a live model of a Network of Actors: both Human and robotic that exists in an abstract-space - the Public Internet.[1] The policy directives that govern cyberspace are cited as having the characteristics of a Phantom authority [2].

Praxis and Pragma: working on a Live Model

The Human sensitivities inherent within online communities - both of interest and practice are mutually constrained with technology for machines and policy by Humans. This is an a priori condition that must be evaluated by the Human users of the network, if they are to remain in control. Most Humans are reluctant, for obvious reasons to hand over the network keys to a cybernetic agent of any kind. That is in my opinion, based on subjective experience at Wikipedia, a good stance.

Perhaps, my worth as an effective practitioner of community science can be effectively demonstrated by my sparce insights as a computer science enthusiast. The esoteric nature of my exploits within Wikipedia's Interior Wikipedia:namespace - an experiencial dreamscape for me, have allowed me to create - within my own mind, anyway - a framework for diatribe that allows me to pursue my own interests as a community development practitioner while I seek and find kindred spirits here in WikiLand. My radiator cap is off for anyone who has followed my trail of clues to this spot.

IRC gateway

It could be that realtime control, monitoring, and communications via the simple IRC gateway is one of Wikimedia's main strengths.

--- - *******************************************************
--- - This is the Wikimedia RC->IRC gateway
--- - *******************************************************

I'm not sure if the those with User_accounts on Freenode are fully aware of what raw power they posess to get large chunks of work done through direct interaction between and among themselves and through the interaction of scripts, bots and other tools working through the various gateways in the network. #mediawiki on irc.freenode.net demonstrates this quite well.

With a bit of understanding, and some cooperation, some nice tools could be developed for #wikipedia as well, that could streamline the processes for managing the front edge of Wikipedia and more significantly, the WikiProjects that reside at the core.

Sampling recent changes

Recent changes are available for read only use at irc.wikimedia.org/6667. My tractor client sits on #en.wikipedia and #meta.wikimedia. Tractor's job is to watch for edits to registered WikiProject elements. If and when there is interest in further development, Database_administrators could have some handy tools available through the Relational model I'm just going to keep plowing away at with my lonely little tractor. (Which btw is currently equippped with a PTO - Persistant Traction Object)

Sampling workgroup channels

Method: When both tractor and plow appear in the channel, This file is created and refreshed here, replacing the previous sample.

Notice:For ACADEMIC USE ONLY! 
Publishing logs of #wikipedia is against the Policy of the Administrators of Wikipedia.
source: m:IRC_channels
If you object to the publication of this brief sample, please notify an Administrator.

irc.freenode.net/wikipedia/topic
Tractor	7 July 2005 04:16 (UTC)

IRC log sample Acedemic use only!
You are now talking on #wikipedia
Topic for #wikipedia is Status: Probably up
Wikipedia:MediaWiki 1.5 bugs
Wikipedia wins 2 GRIMME prizes! [explitive delete]
if(editcountMay312005 >= 400)
{goto Special:Boardvote
goto Wikipedia:Criteria for speedy deletion/Proposal
goto Template talk:Merge#Request for comment
else buggeroff (wink)

Topic for #wikipedia set by:
cimon	Wed Jul 6 20:04:24
Tractor	7 July 2005 04:16 (UTC)

Building the Framework

The WikiProject_Keywords is the filesystem used for the three special user accounts:

user:group the registration panel
user:tractor a POE server
user:plow a POE client

How it Works: Keywords builds custom data types and query tables with definitions drawn from the WikiProject master template. Category:User_groups register at the registration panel by simply dropping a WikiProjectNotice onto the queue. The client script reads Group keys from the queue, resets the queue and delivers a message to #wikinode where tractor's administrator(s) reside persistantly.

If the tractor drivers think the project is valid, they open Wikipedia:WikiProject_Keywords and build a custom Spreadsheet for the new project:

scope & hierarchy
$cope	@hierarchy
%hash	spreadsheet

The members of the new project can elect to be either active or passive in the process of configuring the hash table, which is essentially a little tiny database that belongs to each registered project. These become Attachments and are stored as PTOs.

That's the basic framework. Now the fun part...

IRC servers and channels

You have to be there:

irc.wikimedia.org
- #en.wiktionary
- #en.wikipedia
- #meta.wikimedia
irc.freenode.net
- #freenode <-- just wait for +voice
- #mediawiki
- #wikipedia
- #wiktionary
- #wikipedia-bootcamp <--This project enter
- #wikiproject <--This project participate
- #wikinode<--This project administer

Behavior codes:

open You can type freely in these places
touch Ok to to watch - just don't touch anything
play People here may know about this project

Wikimedia Projects and Portals

The interaction between Wikimedia projects may need to increase its resolution to facilitate a more fine-grained approach. Local context encyclopedias and communities may need to create, sort and manage information that flows into larger contexts. This could solve or create several problems.

If you look at the Wikipedia:List of WikiProjects, you can see a natural relationship between ad hoc groups of users and a fairly orgainized topical outline of where their interests are. This phenomenon took place pretty much on its own and in many cases created high-quality, well-maintained portals with logically organized featured articles. With a Project namespace and good real-time collaboration, this trend could grow.

Lists for POE

Most tables are built from simple lists (arrays) with relevance to the protocols involved. These lists can grow into project timelines, activity percentiles, metadata charts, progress charts, and other dynamic records. Some of these functions exist in the Meta world and in individual WikiProjects, but with a bit more participation and a well designed POE-Component-MediaWiki they could go much further-faster.

IRC:

@Users
@Servers
@Channels

MediaWiki

@Users
@Projects
@Namespaces
@Articles

Table definitions and the Heap

POE is really good at scheduling and tracking events. MediaWiki users are really good at organizing objects. IRC Users are really good at thinking on their feet. There's your table.

Realtime control

sample-time has only two fields:

sample-time
$timeIn
$timeOut

group-thread has six:

group-thread
#channel
~~~ (user)
~~~~~ start sampling
{{IRC-sample\|time\|user\|text\|-}} nested table from the channel}}
~~~~~ stop sampling
~~~~~ refresh time

Trust metrics

current ..

Requirements

The Tractor implement must operate in a way that is complient to both Wikimedia and Freenode policies and guidelines for bots.

Guidelines

The bot is to operate within a well-defined set of constraints in clearly visible locations at all times and designed to withstand attempts to subvert the purposes stated below.

Purposes

To provide a 24/7 presence in designated IRC networks and channels for registered projects.
To perform a set of auxiliary functions for registered projects:
1. To greet new and returning users with a meaningful message
2. To continue constructive dialog in the absence of human members
3. To modify certain external content areas through commands:
  1. Append <list>
  2. Search <term>
  3. ...(other command) <argument>
4. To notify the channel when certain external events occur
To automate database functionality for registered projects
(edit me)

Licencing

Licence must be of a free and open source software type. (in progress - subject to consensus)

Documentation

The bot must also be easy to operate and the code fully documented. This shall be maintained in the Specifications document that follows this section.

NOTE:The tractor and driver both join #wikipedia-bootcamp on Freenode IRC. The channel's topic is changed to Identify the driver. At this time it is CQ (the developer). This is the control channel. The 'field' that the tractor 'plows' is #en.wikipedia on the Wikimedia IRC server.

A SourceForge project area is being set up for further development of this tool. Check here for progress.

Specifications

The Tractor implement is specifically an open source inturpreted script built from POE::Component::IRC with the Python Wikipedia Robot Framework in mind.

Edit me.

see

Wikipedia:IRC channels Instructions and discussion for Wikipedians
m:IRC channels policies and procedures for Developers and Admins

sources

http://www.firstmonday.org/issues/ from the First Monday journal
source: http://www.firstmonday.org/issues/issue6_1/tuomi/
source: http://www.firstmonday.org/issues/issue8_12/ciffolilli/
source: http://cpan.uwinnipeg.ca/htdocs/POE-Component-IRC/POE/Component/IRC.html