Slashdot Log In
A Hybrid Between Chat and Message Boards?
Posted by
Cliff
on Thu Oct 05, 2006 12:49 AM
from the not-so-instant-messaging dept.
from the not-so-instant-messaging dept.
qirtaiba asks: "Synchronous discussion software (in simple terms, chat) allows discussions to take place instantly and interactively, but asynchronous software (discussion boards, a la Slashdot) have the advantage that they allow people from different timezones to participate equally. Does anyone know of a hybrid? The closest thing I have found is a proprietary 'Commons Console' offered as a service by Conflict Lab. This is not just an idle question. The Internet Governance Forum (or IGF — you can find more information here) is meeting for the first time in Athens from October 30th to the 2nd of November, this year. A lot of people who might like to participate aren't going to be able to make it to Athens, so the IGF has asked for ideas on how best to enable remote participation. Can Slashdot help?"
This discussion has been archived.
No new comments can be posted.
A Hybrid Between Chat and Message Boards?
|
Log In/Create an Account
| Top
| 52 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Haha, nope. (Score:1)
Take a squiz at Campfire (Score:5, Interesting)
(http://tucuxi.org/)
It's not the instantaneousness (Score:3, Insightful)
Re:It's not the instantaneousness (Score:4, Interesting)
(http://www.mattowen.com/)
Mindalign is one of the major IM/collaboration players in the Investment Banking market, and is installed on the desktops of a lot of global banks.
(No, I don't work for Parlano)
-Jar.
Already done (Score:2, Funny)
tag boards? (Score:1)
LysKOM? (Score:2)
Chat logs get you partway there (Score:3, Insightful)
(http://dsandler.org/)
Many communities seem to get a lot of mileage out of publishing their chat history (e.g. public IRC logs).
This doesn't really solve the problem of equal participation for peers separated by timezone (or, more to the point, separated by waking hours), but it does address the following killer feature of message boards: searching past discussions for help. Public message boards often serve as organically-growing FAQs; for every question asked and answered, hundreds may get answers without ever having to ask. The same is true of published chat transcripts.
(It works in the corporate setting too: I've personally had good success, in terms of capturing ephemeral knowledge that would otherwise be lost, with behind-the-firewall publication of internal IRC logs.)
I like Slashdot (Score:1)
Simple is best (Score:3, Insightful)
The ideal way of doing this, is to make it so the user can post and get immediate results within a single mouse-click. Messages should be displayed in a linear fashion using a single page, rather than broken up into pages or nested by reply. A good example of such a setup is theFark.com [fark.com] website. Users can respond as quickly, or as slowly, as they like.
Just remember, any system that makes a user wait too long or makes it difficult for the user to find information will almost always fail in the end.
IRC? (Score:1)
(http://www.muftak.net/)
Chat == Forum (Score:3, Informative)
(http://www.vanderlee.com/)
The real difference is non-threaded forums (e.g. Bulletin Boards) vs. theaded forums such as NNTP or the slashdot comments.
If slashdot were refreshed every tenth of a second, it would be a threaded chatbox.
Now there _is_ a difference in how people communicate over chat vs. forums; chat typically contains a single sentence in each "post", whereas forum posts typically contain multiple sentences and even paragraphs. I'm willing to bet this behaviour stems purely from the (percieved) difference in lag; if you had a chatbox where messages would take longer to appear, people would probably start writing longer messages.
Metafoum - AJAX Forum Software (Score:4, Informative)
(Last Journal: Thursday May 04 2006, @10:41PM)
It works like phpBB or vBulletin but the active threads page, inside the thread itself and various other places are all built around Ajax so you get the realtime, non-refresh mode.
If someone posts the thread is bumped and everyone knows. In fact if you use FFx and move the forum to a background tab the tab blinks when a new post is there so you can go on with other work and only look when something has happened.
It's still beta but it's now quite usable. Plus... it has Ajax'ed Slashdot style moderation. Members can increase a post above the noise or sink it to oblivion. You set your floor with a fuzzy slider.
There is a working forum at http://www.planetblur.org/beta/index.php [planetblur.org] if you want to look.
what hybrid? (Score:2)
(http://www.the-h.net/)
The easy solution... both? (Score:2)
(http://www.fantasticdamage.com/)
Run a message board during the conference, as well as before and after. Encourage people in the conference (planners, attendees) to post.
Then, have specific "chat times" where someone from the conference is available to chat with others. The purpose of this is to get many interested people involved at once. Nothing is more dull than a chat with four people when you expected forty or four hundred. After the chat is done, simply post the log in a thread in the forum. The main ideas can be continued at a more leisurely pace.
There's plenty of free bulletin boards available, and IRC always works for chat.
You probably want to spend the bulk of your time informing participants of these modes of communication (and ensuring participation of key members) than setting up a bunch of software.
ja.zz (Score:1)
There's also a more extensible clone of it used over at Stoofoo [stoofoo.net] (may be NWS).
Usenet news and/or email lists? (Score:1)
Only problem is you'd have to implement a web-interface that translated bb-code to html to get anyone to use the thing these days.
I personally like mailing-lists with archives too -- but I suppose you'd want to opt-in on recieveing the archive for the past x days when you sign up as a new user.
I realize you really want something "snappier", such as a jabber-server with integrated web interface and chat-logging.
I think the main reason there's so many horrid web-forums is that a) it's dead easy to make one that works (not securly, but who cares about that, right?), and b) it's dead easy to get hosting for such a solution.
To deploy a *real* application server online, you generally need a different type of hosting environment than what most web-hosting companies provide.
Maybe we can hope that the growt of Virtual Servers (be it UML, xen, vmware or something else) in the low-end marked will allow people to start writing real programs again, as opposed to mutilated http-based stuff (You can scream about cookies and php-sessions all you want, but implementing a stateful app over a stateless protocol is going to be a pain, always).
Or; "Why is it that when you've got access to a webserver, everything starts to look like a http-request" ?
Altme (Score:1)
just an idea (Score:1)
I think the most basic thing you would need is a chat interface with 2 "Send" buttons. One would just transmit a "throw away" line to everyone who is viewing live, and the other would be a "for posterity" button that would actually post the comment. That would allow people to interact with the live community, but also prevent people from having to sift through tons of junk to get to the actual conversation.
If anyone actually does this based on my idea I want my name in there somewhere and a winter home in the Bahamas.
Citadel (Score:2)
(http://www.deepnines.com/)
keep in mind percieved differences (Score:1)
(http://www.pennyhero.net/)
Keep in mind that generally now, IMs are thought of as more 'disposable', and people write one or two sentence posts (as mentioned above) quite often. in informal discussions, the majority are pretty empty 'hahah' or 'lol' types of things.
additionally, people who are used to this culture of 'fast, short messages' in chat will be a little thrown off if you then ask people to post thoughtful and insightful messages via a chat medium. longer messages take time to read, and the constant automatic scrolling of text as messages come in will be really frustrating to participants.
Besides the advantage of easier readibility due to NOT having automatically scrolling text like in a chat system, an advantage to using a more "lagged" system or "asynchronous" system is the perception of more permanence to the messages. people will generally put more thought into their replies, and people used to the cultural difference between IM and forums won't be annoyed when a person sends a couple paragraphs in what most see as a disposable chat medium. forums "look" like websites, so the content in the forum looks/feels more permanent. EVERYONE can read it, even long after it's posted if the forum itself is kept visible. Even if it's disclosed early on that all forum messages will be deleted after the discussion, there's still the perception of permanence because it's on a solid "static" webpage.
so, technically yes, chat is a non-threaded forum, but there are differences in perception and the effect of those differences that could have a big impact on the quality of discussion by participants.
Just some stuff to think about.
IRC + forum linked by a bot (Score:1)
FuckedCompany's BBS was practically a hybrid... (Score:1)
php/mysql (Score:2)
You get to see what the previous people said (esp if they were having a conversation) or you can just make notes to everyone about whatever.
it's actually a really small program
Re:CAM (Score:2)
(http://telebody.com | Last Journal: Tuesday July 30 2002, @07:28AM)
Matt