How To - Exchange Messages
From The Socknet
Messages are exchanged between friends and services and often presented on user profiles and services' websites in a tree or timeline format. These messages may be made public or kept private based on arbitrary criteria (there is a suggested criteria listed below).
The following docs describe the messaging system:
- Message Notification
- Message Collection
- Message Forwarding
- Direct Posting
- Recipients
- Private Messages
- Replies
- Updating Messages
- Deleting Messages
- Service Restrictions
- Finding Messages
Contents |
Messages
Messages are mainly transmitted via the notify_message and get_message functions. The get_message function defines the format.
Notification
A message is usually stored on the server of its creator. Recipients are informed of its existence via the notify_message function.
Direct Posting
There is also a post_message function for a creator to send the message to a recipient so that it will be hosted by the recipient. After this the message will appear to have been created by the recipient, and may be passed along via the notify_message function.
Message GUID
A message is shared by informing friends of the GUID of the message.
There are currently three types of message GUID's:
- a GUID containing an openid field and an arbitrary id field is used by Socknet users
- a GUID containing just a url field is used for "sharing" web pages from sites that do not expressly or completely integrate with the Socknet
- a GUID containing a serviceid field and an arbitrary id field is used by Services that have completely integrated with the Socknet
Considerations
Unlike most entities in the Socknet, messages are strictly controlled so that all users see the same text. Most entities in the Socknet system can tailor their data for the reader. IE, a friend may choose to present himself by his full name to business associates, but use his nickname for family. This would be a liability if a message were shared but had different text. (IE, when forwarding messages there are at least two people's reputations on the line, so the message must look the same for all recipients.)
