Database load.
In particular, there were people with hundreds of archived messages fetching the entire list every few seconds in order check if there were any new ones (that is the way all of the external chat clients that support displaying private messages work).
The ticker would first need to have a parameter added that says what the last message you saw was so that it would only show new messages and all common external clients updated to use that parameter.
However, archiving and unarchiving of messages are completely under the control of the user so there is no reason that external clients need to poll for changes to archived messages. So even supporting XML access to archived messages is a low priority.
Rather than wait for archived messages to be available via an XML ticker, you might want to write an external client that you use to archive messages and get the XML before you do so.
In reply to Re^2: Archived messages through xml ticker (reason)
by tye
in thread Archived messages through xml ticker
by Coruscate
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |