_Current version:_ `0.1.1`
## Table of Contents
1. [Introduction & Overview](#introduction--overview)
2. [Pond as a Protocol](#pond-as-a-protocol)
3. [Pond as an App](#pond-as-an-app)
* [What's Missing for 1.0?](#whats-missing-for-10)
4. [Information for Contributors](#information-for-contributors)
* [Testing, Bug Reporting & Feature Requests](#testing-bug-reporting--feature-requests)
* [Protocol Definition](#protocol-definition)
## Introduction & Overview
Pond is a protocol that aims to standardize Atom+RSS syncing across the web. It's also a self–hosted alternative to the backend part of Google Reader, written in Go.
## Pond as a Protocol
Pond defines a set of [RESTful HTTP API endpoints](https://github.com/ArturoVM/pond/blob/master/api_doc.md) that receive and send data in a standardized format, while making it very comfortable for developers to use. Comfort, ease of use, minimalism and elegance are Pond's primary design goals.
Anybody can implement Pond using their technology stack of choice. It could be used in a multi–user environment (as is the case with the reference implementation), or a single–user environment.
Pond also aims to allow developers to build upon it: other protocols can be thrown on top (such as the Tent protocol), as long as the implementation satisfies all the API endpoints.
All of this allows for a (hopefully) bright future: if developers were to adopt Pond in their services, maximum portability would be achieved, without all the pain that comes with learning and implementing new APIs; let alone the mess that RSS is.
## Pond as an App
The Pond reference implementation does _not_ include a feed reader; it is just a backend that feed reading apps can use to sync your feeds and articles across devices.
It's worth noting that I aim to make the Pond reference implementation as high quality as possible so it can also be used in production, and it's not just there as a learning tool.
Because Go compiles and links all libraries statically, you can download the appropriate binary for your platform, and run it right away. However, you can of course always build it from source.
To build Pond, you need the following dependencies:
go get -u github.com/moovweb/gokogiri
go get -u github.com/bmizerany/pat
go get -u github.com/mattn/go-sqlite3
go get -u github.com/robfig/cron
go get -u code.google.com/p/go.crypto/bcrypt
git clone git://github.com/ArturoVM/pond.git
go build -o pond *.go
If you want cutting edge, before building, do:
git checkout develop
To run the Pond binary, simply do:
To specify a port other than the default one, use the `-p` flag:
./pond -p 8080
### What's Missing for 1.0?
#### First and foremost? Testing, testing, testing.
Atom is amazing and awesome and unicorns and rainbows. RSS is not. RSS is a messy pain in the ass—kinda like diarrhea. I need people to test the program and try to break it (bug reporting will be _very_ appreciated), so I can sort out all the little quirks and handle all sorts of use cases, and make the Pond reference implementation much more robust over time.
#### OPML Import and Export
Which will very likely be added in 0.2.0
#### Favorites API
Which will also very likely be added in a near–future minor version.
#### That's it?
No. I'm sure more things will be added to this section as time goes by.
## Information for Contributors
You can contribute in any of the following ways:
To contribute with a bug fix or to add a feature, fork the repo, create a new branch and add a pull request. If you're fixing a bug, name the branch after the issue ID.
You can very easily infer what's in each file based on its name (e.g. route definitions are in `routes.go`, the articles API is in `articles.go`, etc).
### Testing, Bug Reporting & Feature Requests
Just download the app, use it as much as you can (but, of course, don't rely on it just yet) and submit any bugs you encounter or feature requests you may have.
### Protocol Definition
You can contribute a lot just by giving your views of the protocol. If there's something you think isn't quite right, or know how it could be improved, submit it to the issue tracker.