I agree that the different public channels are probably overkill, and too complicated. The alternative would be, having group channels which can have different settings, and a public channel with the 24h flush.
For the start, we can obviously begin with a 24h flush solution.
For the group channels: How else would you do it, if not with checking membership periods? How do you find out who is allowed to read something or not?
I think skype and gtalk showcase the perfect answers to all of these questions.
@midsch:
> And you really use chatlogs for storage of useful stuff? Come on. I can't really believe it. Results, even if only rough notes should go to wiki/forum. midsch
I think you focus on the wrong area. The main purpose of the chat will be to let members talk about activities such as a barbecue, meeting up somewhere, etc. Often people will forget to put the information into another medium, or, even worse, there is no other medium easily available.
Or, imagine a traveler who wants to discuss meet-up details in chat - how irresponsible would it be to flush this valuable information? "Haha, too late! Did you not write it down on paper? I hope you have a tent!"
And even for work chats, I often use the skype or gtalk chat logs to read back on things from last week, or earlier. For instance, if people have posted code snippets, urls, usernames, contact details, often this stuff is not copied to any other medium.
And, sometimes I simply want to read back a chatlog of some other people, for instance in our skype dev channel. Noone can be expected to waste his time and bloat any wiki/forum with information extracted from chats, to save it from the 24h flush.
The user's content is sacred. Be careful with flushing.