But I've come to appreciate Twitter: the super-simple broadcasting aspect (which is not conversation by definition) and purely organic organization of messages by hashtags etc. is something fundamental for real-time news site of 21st century.
I've come to think Jaiku more as a (r)evolution of discussion forums, where as Twitter is something else.
Jaiku definitely has a plus on functionality (although I haven't explored all of it yet), but as Ade mentions the mass of colleagues, friends and people on twitter basically rule over the functionality I am afraid...
@adewale, I think the great old community is gone, unfortunately persuading people back is not way to go.
Instead, starting a few thematic Jaiku-clones for new audiences could be a great way to vitalize the platform. Pick a large enough topic (e.g. "cooking") and create a new modern discussion forum with Jaiku features for it.
Personally, I like the conversatonal nature of things here; but miss the rss aggregation that also spawned conversations. It was that part I enjoyed most; talking to a person is one thing, their reading lst is another nice layer.
@teemu: That would imply that Jaiku is open source and people could install it on their own servers. Unless that doesn't happen Jaiku is "limited" to it's current state and status against twitter as the audience will not just move to Jaiku just because...
@ecomba, Jaiku is open source, and you can run your own separate instances with your own modification, though in AppEngine only. Nothing of course stops to write an own database backend if someone wants to run it from own servers.
@teemu: And that is where is becomes interesting; if I am able to run it outside of AppEngine on one of my servers... Then the whole thing starts to be a real competition to Twitter...
Question though: If hypothetically I run an instance of Jaiku on a server of mine, would that instance communicate with the main instance of Jaiku (as in with this); aka does Jaiku do the federation to other instances (as per XMPP protocol)?
@ecomba, no federation (yet). But my main point is that I don't want Jaiku instances to compete with Twitter, I see them serving totally different functions: In my opinion Jaiku is a conversation platform, whereas Twitter is optimized for broadcasting thousands of viewpoints and adding better conversation support to Twitter would hinder that function.
@teemu: thats where #identica came in to win: its very similar to twit on noise^W ease, but (now) has threads like jaiku.
its also already federated (still missing some parts like groups and hashtags) and installable on any system.
@teemu I see the old Jaiku as a great way to discover the interesting conversations of your friends' friends, and making separate "cooking" etc communities would break that up, which would be a bit of a pity. Very few people only talk about one topic ever. Also it's a lot easier to organize a casual activity with friends here than on Twitter. @adewale once Jaiku becomes as easy and casual to "check into" as Twitter is on my phone, I'll check in more. Really miss mJaiku, even though it wasn't quite "finished".
@teemu I agree with @spongefile in that splitting the conversations on multiple servers or communities is not a good thing. Metcalfe's Law etc. The benefit of a disconnected community will not match the effort gained from keeping up with yet another separate source of information.
Federation of course has a chance to fix that by connecting the separate servers.
13 comments so far
Lots of people feel that way but they persist in using Twitter because it has the mass of other users.
The trick is persuading more of you to come back. Any ideas on what we can do to help?
5 months ago by adewale
But I've come to appreciate Twitter: the super-simple broadcasting aspect (which is not conversation by definition) and purely organic organization of messages by hashtags etc. is something fundamental for real-time news site of 21st century.
I've come to think Jaiku more as a (r)evolution of discussion forums, where as Twitter is something else.
5 months ago by teemu
That's a good point...
Jaiku definitely has a plus on functionality (although I haven't explored all of it yet), but as Ade mentions the mass of colleagues, friends and people on twitter basically rule over the functionality I am afraid...
5 months ago by ecomba
@adewale, I think the great old community is gone, unfortunately persuading people back is not way to go.
Instead, starting a few thematic Jaiku-clones for new audiences could be a great way to vitalize the platform. Pick a large enough topic (e.g. "cooking") and create a new modern discussion forum with Jaiku features for it.
5 months ago by teemu
Personally, I like the conversatonal nature of things here; but miss the rss aggregation that also spawned conversations. It was that part I enjoyed most; talking to a person is one thing, their reading lst is another nice layer.
5 months ago by arjw
@teemu: That would imply that Jaiku is open source and people could install it on their own servers. Unless that doesn't happen Jaiku is "limited" to it's current state and status against twitter as the audience will not just move to Jaiku just because...
5 months ago by ecomba
@ecomba, Jaiku is open source, and you can run your own separate instances with your own modification, though in AppEngine only. Nothing of course stops to write an own database backend if someone wants to run it from own servers.
5 months ago by teemu
@teemu: And that is where is becomes interesting; if I am able to run it outside of AppEngine on one of my servers... Then the whole thing starts to be a real competition to Twitter...
Question though: If hypothetically I run an instance of Jaiku on a server of mine, would that instance communicate with the main instance of Jaiku (as in with this); aka does Jaiku do the federation to other instances (as per XMPP protocol)?
5 months ago by ecomba
@ecomba, no federation (yet). But my main point is that I don't want Jaiku instances to compete with Twitter, I see them serving totally different functions: In my opinion Jaiku is a conversation platform, whereas Twitter is optimized for broadcasting thousands of viewpoints and adding better conversation support to Twitter would hinder that function.
5 months ago by teemu
@teemu: Which is absolutely true, I agree!
5 months ago by ecomba
@teemu: thats where #identica came in to win: its very similar to twit on noise^W ease, but (now) has threads like jaiku. its also already federated (still missing some parts like groups and hashtags) and installable on any system.
5 months ago by BUGabundo
@teemu I see the old Jaiku as a great way to discover the interesting conversations of your friends' friends, and making separate "cooking" etc communities would break that up, which would be a bit of a pity. Very few people only talk about one topic ever. Also it's a lot easier to organize a casual activity with friends here than on Twitter. @adewale once Jaiku becomes as easy and casual to "check into" as Twitter is on my phone, I'll check in more. Really miss mJaiku, even though it wasn't quite "finished".
4 months, 4 weeks ago by spongefile
@teemu I agree with @spongefile in that splitting the conversations on multiple servers or communities is not a good thing. Metcalfe's Law etc. The benefit of a disconnected community will not match the effort gained from keeping up with yet another separate source of information.
Federation of course has a chance to fix that by connecting the separate servers.
4 months, 4 weeks ago by spushnik