Improve presentation of registered application

Well, it would definitely be a neat feature. If I get a good patch that implements (as a optional feature) it I will definitely commit it.

An application could be a node with fields such as:
- author (node)
- creation date (node)
- title (node)
- description (node)
- an image (cck file field)
- tags (taxonomy)
- website (cck link)
- privacy (private)
- statistics
and obviously a keypair.

This keypair could be exposed as a CCK field while still using it's own tables.

Examples

Flickr: http://www.flickr.com/services/apps/1141/
SoundCloud: http://soundcloud.com/apps/musescore

This suggestion very much sounds like something similar to Content Profile.

Like with Content Profile I think the representation of an application as a node should be a different project and that this module should only make sure that it is possible to alter the authentication pages enough to allow for that.

What do you think?

Yes, with some hacking this could be possible. However, I feel like this could be on the long term roadmap of this module. So rather than hacking, why not do it good from the start. When Flickr opened up their API and gave the option of making app keys, they listed it in the same way as what this module is doing right now. Today, Flickr has created a full blown solution which looks similar to a node with several properties. The advantage of it is that applications can be listed, rated, commented, ... becomes social. For websites with Open API's, this is a must have. Obviously, not everyone needs Open API's.

Setting this as postponed again to mark it as a longterm goal.

I think it is a great idea that should be realized some day, but with D7 and everything there's no time for this now - we need to focus on getting stable versions out for both D6 and D7.