Page ideas
Page ideas is a list of pages that could be written on IdeaWaza but do not exist yet. Each entry gives a working title and a short description of what the page would cover. Some entries are informational or persuasive articles. Others are project proposals, which describe something that could be built, tested, or organized. A red link here is an invitation, not a mistake.
The thread running through most of these ideas is simple. Knowledge, code, and money should be able to move between people and software agents without one company standing in the middle of every step. Wikis, Git, permanent storage, low-fee cryptocurrencies, and local AI are all pieces of that picture. The goal is a world with more abundance, more freedom, and fewer chokepoints, used for legal and ethical purposes.
How to use this page
Pick an idea, open the red link, and start writing. Keep titles short and in sentence case, with proper nouns such as Git, MediaWiki, and Arweave capitalized. Add categories at the bottom of the new page. When a page goes live, remove it from this list or move it into a "Created" note, and add it to New. Original articles can also go under Interesting ideas on Ideas.
If you have a page idea of your own, add it below with a one or two sentence description. Rough ideas are welcome. An idea can be refined later through discussion and editing.
Informational and persuasive articles
Why a small group is better off running its own MediaWiki with content-addressed mirrors than renting a closed wiki host. The page would argue that long-lived, shareable ideas deserve a home the group controls, with exports pinned to IPFS or Arweave so the knowledge survives any single host. It would cover cost, effort, and the real tradeoffs, and it would make the case that ownership is worth it for anyone who plans to keep thinking in public for years. Related: Local-first wiki and Git mirrors.
The case for treating open-weight AI models the way communities treat public libraries. Credit unions, co-ops, libraries, and nonprofits could run shared local models on hardware they own, so people get useful AI help without handing every question to a large platform. The page would cover privacy, cost sharing, what local models do well today, and where they still fall short. It ties into abundance and post-scarcity thinking, where useful tools become cheap enough to be a shared public good. Related: Post-scarcity economy.
How people and software agents could build reputation that travels with them instead of being locked inside one platform. Signed work records, commit hashes, federated forge activity, and short public notes on chain could add up to a track record anyone can verify. The page would explain why star ratings on a single site are fragile, what a portable record could look like, and how to avoid turning it into a surveillance score. Related: Agent-to-agent commerce.
A practical look at how to tell whether the world is actually getting closer to post-scarcity. The page would suggest simple measures, such as the hours of ordinary work needed to buy a unit of computing, storage, energy, food, or housing, and how those numbers change over time. It would separate goods that are getting cheaper fast from goods that stay scarce, so abundance talk stays grounded in evidence rather than hope.
Project proposals
A proposal for one shared configuration layer that controls what an AI agent is allowed to do with money and with permanent publishing. The same file would cap what the agent can pay on permissionless rails such as Bitcoin Cash, and what it can push to Git or MediaWiki before anything becomes permanent on Arweave or another durable network. Operators would get one place to set limits, review logs, and revoke access. Related: Publish gates before permanence and Permissionless rails for agent pay.
A proposal to let independent MediaWiki sites follow, discuss, and merge each other's edits over ActivityPub, the way ForgeFed does for software forges. A small wiki could watch a page on another wiki, comment from its own talk page, and offer an edit back without anyone creating an account on the other site. This builds on a long-running dream of peer-to-peer wikis and connects it to protocols that exist today. Related: Permanent wiki and Git forges on AO and P2P MediaWiki.
Created from earlier ideas
Some ideas that started as suggestions are already live. See Local-first wiki and Git mirrors, Publish gates before permanence, Permissionless rails for agent pay, and Permanent wiki and Git forges on AO. The full list of original pages is under Interesting ideas on Ideas, and more proposals are collected at Project proposals.