Jaiku or Laconi.ca? • Hacker News Board

Re: Jaiku or Laconi.ca?

#11

Post by marnujra » Mon, May 04, 2009, 1:33 PM UTC

evanprodromou wrote: post #5

Hi. I'm the lead developer for Laconica. You're incorrect on one important point: you can license the content of your own server however you want. We use the CC Attribution license by default, since it so closely matches how most people share microblogging data (e.g., you can copy and reuse it as long as you credit the author). Jaiku will soon support OpenMicroBlogging -- we're working with the JaikuEngine team to ma…

All of my impressions are based on my analysis and hence the mistakes! I am happy to hear that the licensing can be changed. A big relief.

Well, most of our clients would like to make the site skinnable. By default the fonts dont look as pleasing as either twitter or jaiku. I have tried it on Camino, firefox & Safari. I guess its a matter of opinion.

I was referring to the XMPP Pub-sub support. I am happy to be corrected.

I would love to go with laconi.ca. Could we take this offline? Is there an email id I can reach you at?

Thanks!

Re: Jaiku or Laconi.ca?

#12

Post by adewale » Mon, May 04, 2009, 8:22 PM UTC

marnujra wrote: post #9

adewale wrote: post #8

Hi, I'm one of the Googlers working on JaikuEngine in my 20% time (BTW JaikuEngine is to Jaiku as Chromium is to Chrome) and I just wanted to add a few things. Firstly either Laconica or JaikuEngine would make an excellent choice. They're both open source and they're both built by teams who believe in the idea of lots of small microblogs that can talk to each other rather than everybody using one massive microbloggin…

Thanks for a detailed response. A couple of quick questions Is there any plan to support the twitter API for now so there is no need for an separate client? Is there a timeframe for support for XMPP & federation? They seem a while away. To us federation is not as important as XMPP. Also Are there any migration tools available? Just in case things don't pan out well.

We don't have any current plans to support the Twitter API. That's just because no-one's asked for it. We'd have no objections if someone filed a feature request on our issue tracker: http://code.google.com/p/jaikuengine/issues/list or sent us a patch to add Twitter API support.

We also have our own API which is supported by a few apps.

Open sourcing the XMPP support is dependent on the AppEngine team's release of the XMPP API. However their roadmap: http://code.google.com/appengine/docs/roadmap.html says they'll be launching XMPP support sometime before the end of June 2009.

We don't currently have any migration tools although the JaikuEngine API exposes the complete history of every post a user has made and so does the website. It should be relatively simple for a user extract all of their data out of any JaikuEngine instance. We'd like to make this even easier but we're still thinking about the most user-friendly way to do this.

If you set up your own instance of JaikuEngine then you can use the Remote API: http://code.google.com/appengine/articles/remote_api.html to easily extract all your data out of AppEngine's datastore.

In general my advice is that you sign up to both Identi.ca and Jaiku.com (as they're the single biggest instances of both Laconica and JaikuEngine) to get a feel for how the two systems work. Not only will this give you an understanding of how they compare to each other but you'll see how they differ from Twitter and be able to interact with the respective development teams.

Re: Jaiku or Laconi.ca?

#13

Post by csarven » Mon, May 04, 2009, 9:09 PM UTC

marnujra wrote: post #11

evanprodromou wrote: post #5

Hi. I'm the lead developer for Laconica. You're incorrect on one important point: you can license the content of your own server however you want. We use the CC Attribution license by default, since it so closely matches how most people share microblogging data (e.g., you can copy and reuse it as long as you credit the author). Jaiku will soon support OpenMicroBlogging -- we're working with the JaikuEngine team to ma…

All of my impressions are based on my analysis and hence the mistakes! I am happy to hear that the licensing can be changed. A big relief. Well, most of our clients would like to make the site skinnable. By default the fonts dont look as pleasing as either twitter or jaiku. I have tried it on Camino, firefox & Safari. I guess its a matter of opinion. I was referring to the XMPP Pub-sub support. I am happy to be corre…

Laconica is theme-able see http://laconi.ca/trac/wiki/ListOfServers for some examples. It can also integrate custom Plugins which allows you to do a good range of stuff. http://army.twit.tv http://bleeper.de http://todaysmama.com/connect are few of the larger laconica communities that have custom themes and plugins implemented.

Re: Jaiku or Laconi.ca?

#14

Post by evanprodromou » Tue, May 05, 2009, 1:28 PM UTC

adewale wrote: post #12

marnujra wrote: post #9

Earlier quoted context omitted.

Thanks for a detailed response. A couple of quick questions Is there any plan to support the twitter API for now so there is no need for an separate client? Is there a timeframe for support for XMPP & federation? They seem a while away. To us federation is not as important as XMPP. Also Are there any migration tools available? Just in case things don't pan out well.

We don't have any current plans to support the Twitter API. That's just because no-one's asked for it. We'd have no objections if someone filed a feature request on our issue tracker: http://code.google.com/p/jaikuengine/issues/list or sent us a patch to add Twitter API support. We also have our own API which is supported by a few apps. Open sourcing the XMPP support is dependent on the AppEngine team's release of th…

So, wouldn't it be awesome if this were the main question people were deciding right now?