Indie Wiki Buddy

Indie Wiki Buddy is a browser extension that automatically notifies and redirects you from wikis on large, corporate-run wiki farms to independent wikis.

• Learn more at getindie.wiki.
• Download for Firefox
• Download for Chrome

---

Large, corporate-run wiki farms have enabled hundreds of great wikis and communities. Unfortunately, these wiki farms can easily overshadow quality independent wikis, especially in search engine results. Independent wikis often have the benefit of greater self-determination and fewer ads, but are easily missed by users who aren't aware of their existence.

When visiting a wiki on a large corporate wiki farm such as Fandom, Indie Wiki Buddy will notify and/or automatically redirect you if a quality, independent alternative is available. You can customize your experience per-wiki.

In addition, search results in Google, Bing, DuckDuckGo, Yahoo, Brave Search, Ecosia, Startpage, Qwant, Yandex, Kagi, SearXNG, and Whoogle can also be filtered, replacing non-independent wikis with text inviting you to visit the independent counterpart.

Indie Wiki Buddy also supports BreezeWiki, a service that renders Fandom wikis without ads or bloat. This helps give you a more enjoyable reading experience on Fandom when an independent wiki isn't available.

Adding wikis

Contributions are welcome and encouraged! You can either open a pull request to add a new wiki, or open an issue.

Criteria for inclusion

• The wiki should be editable by the public (that's what makes a wiki a wiki!)
• The destination wiki should be independent, meaning that decision-making and control of the wiki largely rests with the wiki's staff and volunteer editing community.
  • Factors include editorial independence, the editorbase's ability to request changes from their host, and any history of the host exerting decisions contrary to a wiki community's wishes.
  • Large hosts such as Miraheze and Wiki.gg may be considered less independent, but are included as they are community-friendly hosts, provide decent levels of control, and are popular destinations for forking wikis.
• The destination wiki should be of decent quality, ideally matching (or exceeding) the quality and size of the origin wiki. While we want to support all independent wikis, we also want extension users to be directed to wikis where they can find what they are looking for.
• When there are multiple independent wikis on the same subject, we will usually point to the wiki that is most complete and prominent in the community.

Data

Wiki data is located in JSON files in the data folder, one file per language.

Entries are formatted as follows:

{
  "id": "en-example",
  "origins_label": "Example Fandom Wiki",
  "origins": [
    {
      "origin": "Example Fandom Wiki",
      "origin_base_url": "example.fandom.com",
      "origin_content_path": "/wiki/",
      "origin_main_page": "Example_Wiki"
    }
  ],
  "destination": "Example Wiki",
  "destination_base_url": "example.com",
  "destination_platform": "mediawiki",
  "destination_icon": "example.png",
  "destination_main_page": "Main_Page",
  "destination_search_path": "/index.php",
  "destination_content_path": "/wiki/",
  "tags": [
    "official",
    "miraheze",
    "wiki.gg"
  ]
}

• id: A unique identifier for the wiki; should start with the two-letter language code for the wiki, followed by a hypen and the name of the subject/franchise the wiki covers.
• origins_label: A label that is shown to the user, identifying the non-indie wiki(s). This is usually just the name of the wiki, but in the case of multiple wikis, it may be something like "Example Fandom Wikis" (plural).
• origins: An array of wikis being redirected to the destination wiki. The vast majority of the time, there is just one wiki here. There may be multiple when a series has multiple wikis that combined into one destination wiki; when a Fandom wiki has archived alternatives; or when there are multiple non-independent wikis across multiple wiki farms.
• origin: Name of the wiki being redirected.
• origin_base_url: Fully qualified domain name of the wiki being redirected.
• origin_content_path: The URL path prefix for article links on the wiki being redirected. On MediaWiki wikis, it can be found at Special:Version. Fandom wikis are usually /wiki/.
• origin_main_page: The title of the main page of the wiki. This is used to direct the user to the corresponding main page on the destination wiki.
• destination: Name of the wiki being redirected to.
• destination_base_url: Fully qualified domain name of the wiki being redirected to.
• destination_content_prefix: A prefix that is prepended to article names before performing a search on the destination wiki. This can be useful if a wiki separates its content into different namespaces. For example, if we wanted to redirect a wiki about Super Mario Odyssey to a general Mario wiki that has Odyssey content in a namespace called Odyssey, we would set destination_content_prefix to Odyssey:.
• destination_content_suffix: A suffix that is added to the end of article names before performing a search on the destination wiki. This is typically used when a multilingual wiki separates its languages by suffixes (e.g. /es, /pt, etc.). Team Fortress Wiki is an example that uses this.
• destination_platform: The wiki's software. The current supported options are mediawiki and dokuwiki. If you are contributing a wiki that is on another wiki platform, please open an issue so that support for the platform can be added.
• destination_icon: The name of the wiki's favicon in the favicons folder.
• destination_main_page: The title of the main page of the destination wiki.
• destination_search_path: The URL path prefix for performing searches. On MediaWiki wikis, it is called the index.php entry point and can be found at Special:Version.
• destination_content_path: The URL path prefix for article links on the destination wiki. On MediaWiki wikis, it can be found at Special:Version.
• tags: An optional array of tags. We currently support official, miraheze, and wiki.gg (the latter two of which are hosts). If none of these apply, leave the tags property out.

Favicons should be uploaded as 16px PNGs inside the favicons folder.