Need a non-persistent chat app

[KnowledgeGarden]

There are use cases where a simple linear chat room would be of enormous value in terms of facilitating "backchannel" conversations during game move decision making in guilds.
Ideally, it needs to be group wide within a guild, but it is also of interest to use @mentions to direct chat to particular individuals. Given that it's non-persistent, it may be that unanswered @mentions could be persisted in some way and find their way to an "Inbox" -- which, itself, might turn into another issue.

[mprinc]

One project that i am developing now is _TopiChat_ (TopicChat if it is not obvious enough :) ).
It is intended to be VERY-persistent :) but other project i am interested in is VERY-nonpersistent. So the code base supports both. It is about Topic-driven dialougue.

I have a very short info communicating the idea behind it. Here is the link: https://docs.google.com/document/d/1CLcm_afgulqF5gAClSqS6jt1snhkLNvGcqQzfgRSRn0/edit#

Sorry for some missing parts, it is pulled out of the bigger context of _KnAllEdge Toolset document_ that is basically my full focus.

If you are interested it will be open-source

[KnowledgeGarden]

I am thinking that TQPortal includes a ringbuffer. I used it for all the recents; set its size to 20 entries. Those are actually persisted; Admin has a button to SaveRecents for when the system is going to be taken down for maintenance. Of course, they are lost if the system blows up.
Said ringbugger could be attached to each incubator room, and all chat messages go there. Don't necessarily have to persist them; they are volatile, but doing so means that anyone joining the incubator can see what's been said if the chatroom is filled from the ringbuffer when first fetching the page. The page then refreshes itself by way of the chat app's long poling or whatever.