Account management system (and related topics)

The general topics:
1) in the current BOINC model, each projects is self-contained,
	and has its own community-related features
	(profiles, message boards).
	Some of this features would be better if they
	were centralized.
	How can we extend the AMS model to allow AMSs to provide this?
2) How can we enrich the community-related features to
	attract and retain participants better?
3) Other ways to make AMSs more useful

Examples of 1):
- For BOINC-related questions, projects shouldn't have
	their own message boards, but should point to a central forum
	(e.g. an AMS)

Examples of 2):
- Extend profiles to include "buddy list", where each buddy is
	name
	URL of image and thumbnail
	URL of profile (may be on another site)
- Extend profile to include
    "message bookmarks": URLs to posting by other people
        who this person this is interesting
    "external bookmarks": external URLs
- Extend profiles to include list of projects
	name of project
	URL of profile on that project
- Extend profiles to include
    - list of recent posts (on this and/or other projects)
    - OR list of threads this person has created
    - or favorite threads
    - or something like that
- Profile text is one piece.

Examples of 3):
- Add a web RPC to set forum preferences
- Add web RPCs to create/edit profiles
- Add web RPC to get title/time of last N posts
- Add #posts to user info RPC reply
- Projects should know when an account is being managed by an AMS,
	so that the user can be advised not to modify it
	on the project web site.
	May need to add a flag in user record;
	may also want to store URL of account manager.
----------------
There was a long discussion about an AMS being
able to tell the client to suspend (or no-new-work) projects.
There's a danger of getting confused about whether
such a command comes from the AMS or from the local GUI.
The conclusion was that these need to be maintained separately.