former projects
This article is a stub. You can help the IndieWeb wiki by expanding it with relevant information.
former projects are projects that were used by indieweb community members in the past and at least seem to be offline.
For unmaintained, abandoned, or apparently inactive (few if any updates or active users) projects that are still online and could be re-activated by someone in the community, see:
If you’re actively using one of these for your primary personal site, please add yourself to its specific page, and bring it up on the #indieweb-dev channel!
Offline
These former projects (alphabetical) are offline (none of their links work) and their use status is unknown. They may be recoverable from the Internet Archive. Feel free to dig up and document archive links if you like!
- Federated Community - The idea here was to use pop-based email, generic Python scripting, and static HTML to set up a dynamic microblogging and photohosting site. Workflow included sending an email to a pop email account. Then when the Python script finds the new email it downloads the email to my static HTML server and also sends out an email to my facebook and twitter accounts for syndication.
- The Python script was located at https://github.com/geo-gs/federatedcommunity/tree/python (404)
- An example of the static HTML was located at https://github.com/geo-gs/gcarlson.github.com (404).
- Plans were to add the ability to upload photo albums. After that, comments. Former user: George Em on geo.gs (dead link 2018)
- Glow
- ...
Brainstorming
Page Update
This page needs updating to provide a more useful sorting of former projects.
A few goals: (some ideas from 
Tantek Çelik, feel free to iterate/expand/refine):
- Kindness to creators of past projects. How can we improve documentation of past projects to be particularly kind to creators, especially to folks formerly active in the community, in the hopes that they feel welcome to rejoin at any time, and contribute at any level, not necessarily the way or form they did before, and in explicit consideration that life happens.
- Be easily navigable and understandable by casual readers. When a new person visits this page, can they easily browse it and understand why some project (perhaps a project they’ve heard about or maybe even used or been involved with in the past) is in a particular section, and/or what it might take to revive the project and make it active instead of former.
- Be transparent and direct about potential utility. Can we be very direct, real, and clear about which former projects were useful to how many people, for what kinds of use-cases, so that folks looking to solve similar problems can focus on browsing/re-using code accordingly. Or on the other side of the spectrum, make it clear which things were ideas/aspirations that didn’t quite get off the ground (which is also ok), or which maybe were useful to one particular person (who does or does not wish to be contacted about it — if we know).
- Projects where there is no sign of open source or project site (or it died) can go on this "former" page, since there's nothing that a new person can really do with them, and they’re historical at best.
Once we've figured out how to distinguish different former projects, then we go through the existing lists and reorganize them accordingly.
Unmaintained
These projects appear to be unmaintained, but they're still open source so you may be able to find something to re-use or a starting point for a new project.
Hello, world.
An open-source tumblr/blog/rss reader/wordpress-like thingy. Post your content easily and collect content from other rss/ostatus capable sites. Also, lets you syndicate what you post onto other sites like Facebook, Twitter, Tumblr and grab their content as well (backwards-compatibility ;) Technical-wise: it uses the Ostatus stack, passes SWAT0, BrowserID for authentication, written in Python but meant to run on shared servers.
- Code at Github.
Indie.js
Indie.js is an IndieWeb framework for Node.js currently being abstracted and released as a set of modules for building your own IndieWeb-compatible site.
Nucleus CMS
Nucleus CMS is an open source blogging platform. It allows maintaining multiple blogs and is quite extensible through its plugin system.
IndieWeb enthusiasts previously using it on their own site:
gRegor Morrill used it on gregorlove.com from 2002 to 2015, then migrated to ProcessWire
- Contributed several plugins and core developments.
- Given the current development status of Nucleus, I do not recommend using it.
Red Wind
Red Wind is IndieWebified blog software written in Python and running on Flask. It is intended to be clean, lightweight, and amenable to experimentation. Red Wind is open source and fairly new with minimal documentation.
Examples:
Kara Mahan (author) on kylewm.com (selfdogfooding)
Past examples:
Tent.io
- http://tent.io suite of distributed networking protocols, alternative to OStatus
No IndieWeb community members are using it on their own site.
Trovebox
Trovebox (formerly The OpenPhoto Project) is a server-side photo application that lets you store your photos on Dropbox, Amazon S3 or in your garage, and serve them from URLs on your own domain.
IndieWebCamp participants who are using it on their own site:
- User:Upon2020.com (Johannes Ernst) is running a private instance for his family pictures
- ...
Words
Words is an open source blogging tool (fork of nornagon/words)[1].
IndieWeb enthusiasts currently using it on their own site:
- None currently
Formerly:
Unreachable
These projects appear to be offline, unreachable, or have broken permalinks which need fixing and should be considered for adding to site-deaths.
StatusNet
StatusNet is open source software you can setup on your own server for real-time publishing.
IndieWebCamp participants who are or were using it on their own site:
- Evan Prodromou (2012): http://evan.status.net/ (2012(?)-2013 - being converted to pump.io)
- ...