Anchored conversations: adhesive, in-context, virtual discussion forums

A system for invoking anchored conversations having artifacts of applications as a context, comprising:

• an application conversation interface (ACI) having an application access mechanism that allows access and manipulation of application operations of each of the said applications;
• an anchor mechanism configured to identify and attach a conversation client to a selected anchor position in an artifact;
• and
• a communications device configured to route communications, from the conversation client to a communications network, and from the communications network to the conversation client,
• wherein said communications device is an IRC client configured to pass and retrieve communication to an IRC network;
• and
• at least one conversation database accessible by the conversation coordinator, said conversation database including a conversation history and access control data, wherein said conversation history comprises:
• conversation elements and metadata, including command invocations, anchor positions, anchor context, conversation state changes, and shared artifact version data;
• and
• wherein said access control data comprises access control lists, user accounts, and user privileges.

A system for anchored conversations, comprising:

• means for initiating and maintaining conversation clients at each of a requesting host and a recipient host, including,
• means for receiving an anchored conversation request from an application at a requestor host, said application having an artifact with anchor identifying a location of an anchored conversation;
• means for initiating a requestor conversation client associated with the application at a requester host;
• means for anchoring said requester conversation client comprising a means for maintaining a position of said requestor conversation client relative to said anchor of said artifact of said application at said requestor host;
• means for requesting startup of a recipient conversation client;
• storage means for at least one of conversation history data and access control data;
• means for starting said application at a recipient host;
• means for retrieving a copy of said artifact into said application at said recipient host;
• and
• means for anchoring said recipient conversation client, comprising a means for maintaining a position of said recipient conversation client relative to said anchor of said artifact of said application at said recipient host;
• wherein said means for anchoring further comprise:
• request means configured to receive conversation requests from a requesting conversation client;
• and
• a client mechanism means configured to initiate a recipient conversation client having an anchor position, application, and artifact equivalent to the application, artifact, and anchor position of the requesting conversation client;
• and
• an anchor identification means configured to identify other anchored conversations in the artifact of the recipient conversation client and to one of highlight, grey, and make invisible each identified anchor based on a predetermined access/privacy setting.

A system for placing and maintaining anchored conversations within an artifact comprising a file having a file type, the system comprising:

• an application configured to access the artifact, wherein the application is associated with the file type;
• a conversation client configured to access said anchored conversation and to receive communications regarding a portion of the artifact, while the artifact is viewed within the application, wherein the communications are received from a party having access to the file;
• an anchor configured to identify a location within said artifact with which said conversation client is associated;
• a conversation coordinator configured to maintain a relationship between the anchor, the conversation client and the anchored conversation
• at least one conversation database accessible by the conversation coordinator, said conversation database including a conversation history and access control data,
• wherein said conversation history comprises:
• conversation elements and meta data, including command invocations, anchor positions, anchor context, conversation state changes, and shared artifact version data;
• and
• wherein said access control data comprises access control lists, user accounts, and user privileges.