Jump to content

Wiki technology and democracy

From IdeaWazaWiki

Wiki technology and democracy is the use of open, collaborative editing tools for public deliberation, for drafting rules and laws, and for shared decision-making. A wiki lets many people revise the same text, records every change, and gives each page a discussion space. These features fit a freedom-first, decentralized view of self-governance in which participation is open, the process is transparent, and proposals grow from the bottom up instead of arriving finished from above.

How wikis work and why they suit deliberation

A wiki is a website that permitted users can edit through a web browser. Four features matter most for democratic use. Open editing lowers the cost of taking part, since participants improve a draft directly. Revision history records what changed, when, and by which account, so anyone can audit how wording evolved. Talk pages keep the reasons for a text next to the text itself. Consensus norms ask editors to settle disagreements through discussion and compromise instead of by authority alone.

Transparency comes from the public history, accountability from attributable edits, and inclusion from the low cost of contributing. MediaWiki, the free and open source software that runs Wikipedia, provides all of these and can be hosted by any group.

Real cases

Wikipedia is the largest example of wiki self-governance. Its volunteer community writes and revises its own policies through the same edit process used for articles, and handles serious disputes through an elected arbitration committee. It shows that a very large group can maintain shared rules with little central control, at the cost of steady volunteer effort.

New Zealand offered an early government test. In September 2007 the New Zealand Police launched a wiki where anyone could suggest wording for a new Policing Act, as part of a review of the 1958 Police Act.[1] The resulting text was kept as a record to inform the parliamentary process.

Iceland drew wide attention in 2011, when a 25 member Constitutional Council (Stjornlagarad) drafted a constitution while posting its work online for public comment.[2] In an advisory referendum on 20 October 2012, 64.2 percent of votes on the first question supported using the proposals as the basis of a new constitution.[3] The parliament did not adopt the draft, showing that open drafting needs a clear path to a binding decision.

Taiwan developed vTaiwan, an open consultation process started by the civic technology community g0v that blends online discussion with recorded public meetings. In its case on regulating ride hailing, more than 4,000 participants used Pol.is, a tool where people post short statements, vote on the statements of others, and see which statements win support across opinion groups. The administration pledged to turn the consensus items into regulation.[4]

Barcelona created Decidim, open source software for proposals, meetings, voting, and participatory budgeting. The city used it in 2016 to co-produce its Municipal Action Plan, and hundreds of organizations now run it.[5]

LiquidFeedback is software for proposal development and liquid democracy, in which members vote directly or delegate their vote on a topic to someone they trust.[6] The Berlin branch of the Pirate Party Germany first used it in 2010. Its use sparked privacy debate, because votes could be traced to named members.

Legal text is also moving into public version control. The Council of the District of Columbia, for example, publishes its laws in public GitHub repositories, where every change can be tracked line by line.

How to run a wiki-based consultation

The steps below suit a city, union, cooperative, nonprofit, or community group.

  1. Define scope and mandate. State the question, the deadline, and how results will be used. Say in advance whether the outcome is binding or advisory.
  2. Choose a platform. MediaWiki suits collaborative drafting of text. Decidim and LiquidFeedback add proposals and voting. Pol.is helps surface common ground on contested questions. Self-hosting keeps data under group control.
  3. Set editing rules. Publish a short policy on civility, sources, and moving disputes to the talk page.
  4. Plan moderation. Recruit moderators with different viewpoints and use rollback, edit filters, and account blocks against spam.
  5. Settle identity questions. Drafting can be open to pseudonymous accounts, but a binding vote needs one person, one vote. A common design lets anyone draft, while the final vote uses verified membership or voter rolls.
  6. Link deliberation to a decision. Close drafting on a set date, summarize agreements and disagreements, and send the text to the body that holds authority, such as a council or membership meeting.
  7. Publish the record. Keep the revision history and talk pages online, and report how major suggestions were used.
  8. Make it accessible. Offer plain language summaries, translations, screen reader friendly pages, mobile access, and in-person sessions for people who prefer to stay offline.

Challenges and safeguards

Open editing invites vandalism and edit wars, which revision history, watchlists, and temporary protection can contain. A subtler risk is capture by small, highly active groups. Outreach, fixed time windows, and opinion mapping that rewards agreement across groups help balance this. The digital divide can exclude older, poorer, or rural residents, so offline channels matter. Legitimacy depends on clear rules set before the process starts and on honest reporting of how input was used. Privacy matters because edit and vote records can reveal political views, so groups should collect minimal data. Wikis also scale poorly when thousands edit one sentence, so large processes split topics into separate pages and run staged rounds.

Readiness and possible time scales

Many democracies already have building blocks such as consultation portals and open data. Wider use depends on rules for weighing online input, digital skills, and public trust. Cooperatives and clubs can often adopt these tools within months, while cities have built them up over several years. National change is slower and less certain, as the Icelandic case shows. Any time scale is a judgment about conditions, not a forecast.

  • Which wiki features, such as revision history or talk pages, do the most to make a public process transparent, and why?
  • Compare the Iceland constitutional draft with the vTaiwan process. What made one lead to regulation while the other stalled?
  • Essay idea: design a wiki-based consultation for a local cooperative or union, including rules, moderation, and the final vote.
  • How can a group allow open, pseudonymous drafting while still protecting one person, one vote at the decision stage?
  • Is liquid democracy, with its delegated votes, more or less decentralized than direct voting? Give reasons.
  • AI prompt idea: "Summarize the talk page of a policy draft into points of agreement, disagreement, and open questions, citing revision numbers."
  • AI prompt idea: "Suggest plain language and accessibility improvements for this draft bylaw without changing its meaning."
  • What safeguards best prevent capture of an open process by a small, highly active group?

Readings from Wikipedia

See also

References

  1. ↑ Policing Act wiki launched, New Zealand Police, 25 September 2007.
  2. ↑ Constitutional Council 2011 (English pages), Stjornlagarad.
  3. ↑ Outcome of the counting of votes cast in the referendum on 20 October 2012, Government of Iceland.
  4. ↑ vTaiwan, official information site.
  5. ↑ Decidim, official project site.
  6. ↑ LiquidFeedback, official project site.
Retrieved from "https://ideawaza.com/index.php?title=Wiki_technology_and_democracy&oldid=92994"