Outpost Packet Message Manager

Collaborative Messaging


 

Outpost v1.3 Release Announcement

Along with many new features, enhancements, and bug fixes, Outpost Version 1.3 introduced the concept of Collaborative Messaging using the existing packet infrastructure.

Up until now, Outpost operated in a stand-alone mode, that is, Outpost knew about itself, the TNC, and the BBS.  It operated seamlessly in a mixed client environment and didn't care what other packet client software was out there on the receiving end because all packet messages look alike.  When a message was received, it was the user who interpreted the message and acted on it.

The next logical step for Outpost is what I'm calling collaborative messaging.  

As before, Outpost knows about itself, the TNC, and the BBS.  However, Outpost is now "attentive" to other instances of Outpost that may exist out there as well.  As a result, messages received from the BBS are not only read and interpreted by the user, but also can now be interpreted and acted on by Outpost as well.  The message flow is still the same... Outpost -> BBS -> Outpost. The BBS is still the mail drop for all clients.

Outpost collaboration shows up in several new features in v1.3:

  • Urgent Message Flagging:  The sending station can flag a message as URGENT, and it will be indicated at the receiving station by showing up in RED text.
  • Request Delivery Receipts:  The sending station can request a DELIVERY Receipt.  This is a return message from the receiving Outpost station letting the sending station know that the message was downloaded off the BBS.  This return receipt happens automatically without any user intervention. 
  • Request Read Receipts:  The sending station can request a READ Receipt.  This is a return message from the receiving Outpost station letting the sending station know that the message was opened by the operator.  Again, this return receipt happens automatically without any user intervention.
  • Slot Timing:  This feature allows a group of Outpost users to coordinate when they will each access the BBS based on selecting specific times (slots) during a 60-minute period.

In all cases, these features work when a group of packet stations choose to implement an Outpost-only client environment.  Outpost can still inter-operate with non-Outpost stations, but these features will not work for those clients.

With the base collaboration approach in place, Outpost is positioned to implement other features where the clients are the same on both ends, such as handling message attachments.  There are probably other like capabilities out there; I look forward to hearing about them from the Outpost community.

Another noticeable  change is the look of the Message List display.  New messages will be displayed in BOLD type until they are read.  At that point, they are changed to unbolded.  This will assist Packet operators identify messages that have not yet been read.

As always, your feedback on this version is important to ensure that the integrity of the emergency response mission of Outpost is maintained.  Thanks for your support!


General Feedback

Please send any feedback to

updated:  April 07, 2007