From FavPal

This is the city for the development of FavPal. See the API too.

Contents 1 Core 1.1 Authentication Roadmap 2 Design 3 apps which use the FavPal API 4 ideas of apps, plugins and widgets

[edit] Core

• source code

[edit] Authentication Roadmap

• basic http authentication (user/password) (done, see the API)
• basic http authentication (user/encripted password) for the apps which need to store it (done).
• OpenID consumer. Users with an OpenID account won't need to remember the password for log in. However, it will be useful as API key for clients and external apps.
• OAuth.
• OpenID provider. Therefore, every FavPal user will be associated to an url.

[edit] Design

We need help with the design.

Some files which require a bit of CSS magic: layout, views.

[edit] apps which use the FavPal API

• Thks (Twitter app). "@thankyou @hecpeare!" (thanks) gives 1 fav to hecpeare (if hecpeare doesn't have an account, it would be created one in FavPal automatically).

[edit] ideas of apps, plugins and widgets

• Forums
• A Yahoo Answers with favs.
• FavPal stats.
• A Facebook app for sharing books (or other objects) among friends and friends of friends.
• An plugin for Wordpress which adds a "Thank" link. Maybe later, when we use OpenID.
• Objects marketplace. We can start in a wiki page Marketplace
• An app for a distributed profile (microformats, url based owned by the users when possible like OpenID,...). See the DiSo Project and dataportability.
• ...