IdeaWazaWiki

Open-source software that should exist

Open-source software that should exist is a wish list of tools that would help people learn, teach, and do research. Each idea is checked against projects that already exist. These are ideas for learning and discussion, not products or promises.

Why a wish list

Open-source software is software with public source code, so anyone can use, study, modify, and share it.[1] A wish list trains a useful habit: find a real problem, search for what exists, and name the gap. The checks cover public project pages only, so test a project before you build.

Seven ideas

A wiki that mirrors itself

A wiki on one server can vanish when the server fails. This tool would copy each saved edit to permanent storage such as Arweave and IPFS, and serve a read-only copy if the host goes down. For wiki clubs, a first version is a MediaWiki extension that exports static pages.

Kiwix packs Wikipedia into ZIM files for offline reading.[2] A Wikipedia mirror on IPFS is archived, with snapshots from 2021 and 2022.[3] The ar.io gateway serves content from Arweave.[4] The gap is the automatic loop from edit to mirror to fallback.

A budget book for software agents

Agents may buy data and services, and owners need hard limits. This local-first ledger would give each agent a budget, a list of allowed payees, and a receipt for every payment. For developers, a first version is a command line program that checks each request.

The x402 standard lets a server answer with HTTP 402 and ask for payment.[5] The AP2 protocol has open mandates that carry the constraints of a user.[6] The gap is a plain budget book that any rail can use. See Agent allowlists for spend and publish.

An open ad slot standard

Small sites that want ads without tracking must join a network or run a heavy ad server. This tool would be a short standard for an ad slot, plus a snippet that shows an ad with no cookies. For publishers, a first version is one data file per site. This page makes no claims about earnings.

Revive Adserver is an open-source ad server.[7] EthicalAds publishes its ad server as open source and describes ads without all the tracking.[8] The ads.txt file lets a site list authorized sellers.[9] The gap is a slot description a buyer can read without a platform. Compare Decentralized self-serve advertising.

A public ledger for a basic income pilot

A credit union or nonprofit pilot must show donors and members that it followed its rules, without exposing anyone. This tool would record each payment batch as a count, a total, and a rule version, with no names. For auditors, a first version is a spreadsheet and a summary script.

Open Collective lets groups collect and spend money in the open.[10] OpenSPP is an open-source platform for social protection programs.[11] Mojaloop is an open-source reference model for interoperable payment platforms.[12] These are large. A small pilot may need only a summary layer. See Basic income through credit unions.

An evidence notebook

Students lose track of which source backs which claim. This tool would hold each claim with its sources, a confidence level, and a review date, as plain text files. For students, a first version is a folder of files and a checker for claims with no source.

Zotero manages references and annotations.[13] Argdown is a text syntax for arguments that draws argument maps.[14] The gap is confidence and review dates tied to sources.

A shared local AI box

A library or school club may want AI help without sending text to a company. This tool would be a ready image for a small computer with a model runner, accounts, usage limits, and no logging by default. For teachers, a first version is a tested setup guide.

The llama.cpp library runs language models locally.[15] Ollama manages models on local hardware.[16] Open WebUI is a self-hosted, multi-user interface that supports Ollama.[17] It may cover most of this idea. The gap is a privacy first bundle with classroom defaults. See Community-run AI.

A completeness checker for open designs

Open hardware files are often missing a bill of materials or license, so others cannot rebuild them. This tool would scan a repository and print a plain report. For makers, a first version is a script with six checks.

Open-source hardware means design source files, such as schematics and a bill of materials, are public.[18] OSHWA runs a certification program.[19] Kitspace is a place to share electronics projects.[20] This search found no free quick pre-check script. See Open design.

From idea to project

  1. Write a one page spec. State the problem, the users, and the first version.
  2. Ask first. Find the closest project and open an issue. A small patch may beat a new project.
  3. Choose a license. MIT is permissive and asks only that the license notice stays with the software.[21] Apache 2.0 is permissive, and each contributor grants a patent license.[22] AGPL 3.0 requires modified versions to offer source code to network users.[23]
  4. Build a tiny prototype. Make one thing work.
  5. Document it. Write install steps and limits.
  6. Invite contributors. Label easy tasks.
  7. Sustain it. Donations or grants may pay for upkeep, but neither is certain.

How to judge an idea

  • Is the problem real? Name five people who have it.
  • What exists? If a project covers most of it, join that project.
  • Is the first version small? Try a weekend prototype.
  • Who will maintain it? Software needs care.
  • Does it respect privacy? Collect only what the tool needs.

Discussion questions

  • Which idea here would help you most, and what is the closest project?
  • When should you join a project instead of starting one?

Essay ideas

  • Argue whether wish lists help open-source culture or only add noise.

AI prompt ideas

  • Pick one idea from this page, name the closest projects, and quiz me on the gap.
  • Help me write a one page spec for a tool I wish existed, and ask me questions where my plan is vague.

Readings from Wikipedia

See also

References

  1. ↑ Open-source software, Wikipedia
  2. ↑ Kiwix Reader, Kiwix
  3. ↑ distributed-wikipedia-mirror, GitHub
  4. ↑ ar-io-node, GitHub
  5. ↑ x402
  6. ↑ AP2 Agent Payments Protocol
  7. ↑ Revive Adserver, Wikipedia
  8. ↑ ethical-ad-server, GitHub
  9. ↑ Ads.txt, Wikipedia
  10. ↑ Open Collective, Wikipedia
  11. ↑ OpenSPP
  12. ↑ Mojaloop, Wikipedia
  13. ↑ Zotero, Wikipedia
  14. ↑ Argdown
  15. ↑ llama.cpp, Wikipedia
  16. ↑ Ollama, Wikipedia
  17. ↑ Open WebUI documentation
  18. ↑ Open-source hardware, Wikipedia
  19. ↑ OSHWA Certification
  20. ↑ kitspace-v2, GitHub
  21. ↑ The MIT License, Open Source Initiative
  22. ↑ Apache License, Version 2.0, Open Source Initiative
  23. ↑ GNU Affero General Public License version 3, Open Source Initiative
Retrieved from "https://ideawaza.com/index.php?title=Open-source_software_that_should_exist&oldid=92170"