Entity Info Box

Typically on hovering an user or a group's photo/nickname in a notice list, it will show show advisory info and actions to take. The following are some candidates (we should keep it lean):

entity_profile

• photo
• nickname
• fn
• location
• url (may be excess info but it is probably useful)
• bio
• tags (may be excess info but it is probably useful)
• Stats (probably just subscriptions, subscribers numbers) and link to those pages
• User subscription type: whether it is bidrectional or oneway
• Common Connections: This is more of a feature in and of itself. I think it might be good to show a short list of common subscriptions to give the viewer an idea. Probably should be implemented at a later date.
• Indicators: If the user is a featured user, or have a user role assigned, show an indicator

entity_actions

• Subscribe/Unsubscribe or Join/Leave
• Message
• Block
• Flag

Approach

• Do a single GET per profile
• Use object (or iframe) to GET the profile URL data (e.g., http://identi.ca/csarven#i would target the entity_profile), or;
  • A little tricky because we might have to disable or find a workaround for the clickjacking prevention script, otherwise, it will redirect. It also GETs the full URL content. The benefit is that, it grabs remote profile URLs easily.
• Use an XHR
  • Probably the best way to go at this. Minimizes XHR response's Content-length and can be customized. Would probably need to use Curl to GET the remote profile.

Notes

• Moderation: probably should only be visible from the profile page as it requires more attention by the moderator and give better context and full info about the user at hand.
• Latest notice: Not sure if this information is that vital
  • "it's about discovery. if the latest post helps the user determine whether they want to subscribe to the person in question, then it's good. If not, then it's not" -- Zach