Home
This is documentation for the pump.io social server. Nowadays the wiki is mostly used for project policies, but there's a lot of old documentation floating around.
For up-to-date technical documentation, please see ReadTheDocs.
Project policies
Cookbook
These are some "recipes" for doing interesting things with the server.
Installation details
Some details for installing pump.io on different systems.
- AppFog
- OpenShift
- Heroku
- Installation on Amazon EC2 (Ubuntu)
- Spam filter
- Rasperry Pi - Fewer details or More Details
Clients
- Clients (web, desktop, Android, iOS...)
- Client strategy
- Libraries
- Client porting
Proposals
Interoperable Servers
FAQ + Other
- User Guide
- FAQ
- Who to follow, most shared, most liked... (informal stats)
- Some tips for a better experience using the Pump.io network by @jankusanagi
- Getting Started With Pump.io by Stephen Sekula
- If your pump.io server is identi.ca... (info about changes after identi.ca migrated from StatusNet to Pump.io)
- Users-by-language. A list of some users, grouped by their main language. You can add yourself to it, or ask to be added.
- Other documentation: Understanding pump.io by Evan Prodromou
- Other documentation: Introducing pump.io to Montréal JavaScripters by Ryan Weal (with slides in PDF format)
- Talk in Spanish about pump.io @larjona: pump.ogg - mirror

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
