in reply to Re^3: Archived messages through xml ticker (reason)
in thread Archived messages through xml ticker
(such as the ";archived=1" I suggested) would be abused in such a way that people would still try fetching the entire list?
Um, I must be missing something. Based on what you've proposed, how would they manage to do anything else? Perhaps what you meant to ask was if I thought people would write clients that fetch the entire list of archived message instead of just the entire list of unarchived messages. "If you build it, they will come." In other words, I have no plans to try that experiment simply hoping that people don't use it.
I seriously doubt anyone here really needs to be capable of holding so many private messages for future reference. Surely if anyone has such a high number, it's because they archive every single messages they receive
Um, " • Plus 24 more, 1315 archived" and I assure you I delete plenty of messages. Messages sitting in the archive aren't a problem. A worse problem is that people could have tons of unarchived messages and be using a client that fetches the whole list over and over. So far I haven't noticed that happening, but that should be addressed before worrying about archived messages (which is what I mentioned already).
No. If we are going to add archived message support to the ticker, it will require a "since" so that we aren't repeatedly returning the same 10-15 messages. There will probably also be a limit imposed such that if you ask for all message (archived or unarchived) since "0", you'll only get the first N and have to make a second request to get the next chunk.