OStatus/Structure

Merged me  column: check!My brain spkepid over the ordering suggestion in your previous reply. Great thought this often annoys me, as well. One starting point could be a chronological conversation in context  view, a la Identi.ca  but I think this deserves more thought in general.Thanks heaps   awesome feedback.

Setting up info on discovery

 * if given a webfinger acct:, look up the profile page
 * extract last path segment of URI as a fallback nickname to pre-populate profile data
 * eg http://www.google.com/profiles/brion.vibber -> brion.vibber for Buzz
 * given the profile URI, load and parse it
 * is there hcard data on the page?
 * if so pull it to pre-populate profile data
 * is there an atom feed link?
 * does the feed link have a hub link?
 * if not STOP we can't subscribe
 * does the feed link have a salmon link?
 * if so, save for later -- we'll send a subscription notice to them when we're done
 * does the feed have an ?
 * if so, confirm it's either a person or a group as we expected
 * if so, pull it to pre-populate profile data

Requirements by entity type:
 * ostatus individual
 * MUST have PuSH-enabled Atom feed
 * feed MUST NOT have  listing it as a group (MAY have  listing a person)
 * feed MAY have salmon endpoint link
 * when receiving posts:
 * author URI/id MUST match profile URI
 * if profile info is changed, save to local profile?
 * notice content: use sanitized HTML (or text summary)
 * ostatus group
 * MUST have PuSH-enabled Atom feed
 * feed MUST have  listing it as a group
 * feed MUST have salmon endpoint link
 * when receiving posts:
 * author URI/id MUST NOT match profile URI
 * -> set up ostatus profiles for each new author we see
 * if profile info is changed, save to local profile?
 * if possible, verify profile ownership...?
 * notice content: use sanitized HTML (or text summary)
 * general feed subscription (later!)
 * must have PuSH-enabled Atom (or RSS) feed
 * or RSSCloud
 * or non-PuSH if polling ;)
 * when receiving posts:
 * authorship info is discarded
 * notice content: use title or summary and link