Sense or Nonsense!?

09.10.2009

XEP-0016: Privacy Lists; for Prosody

Filed under: Jabber — Ephraim @ 22:48

I currently finished work at the mod_privacy module for prosody!!
It’s far from being stable, but AFAI have tested it, it worked as I expect it to!
So have a look at: prosody-modules
or a direct link to mod_privacy.lua: here

Have a look at mod_adhoc and commands too! There is a “XEP-0133: Service Administration” implementation growing :)

Have fun! prosody rocks!!

ciao Ephraim

28.07.2009

Migrated to prosody

Filed under: Jabber — Ephraim @ 09:39

So, yesterday I heard about prosody, a jabber server implemented in Lua. After some ground testing, I connected to the room of prosody and found a nice small community with friendly people, who answered all my question very nicely.
After that and the result of my testing, I decided to give prosody a try. Cause of the migrate script from ejabberd2 to prosody, it was easy as hell to migrate everything to prosody. I think it took me less than an hour to migrate the jabber stuff.
Later the day I migrated my transports. This took most of the time, but only caused by me, doing it not how the docu says to do it.

Now I’ll see if it is as nice as I think it is. One argument for me to migrate was the thing, that I’m able to develop modules with a script language (remember, it is build totally in Lua) and that I’m able to re/load the currently developed module on the fly while the server is online. Thats really nice, so I can learn Lua without any problems e.g. need to restart the server or so.

If you want to migrate or setup a jabber server with prosody too, I think I can say don’t hesitate to ask your questions at prosody@conference.prosody.im or ask me at ephraim@0×10.de.

Ciao Ephraim

05.12.2008

add multiple Spellchecker Languages support to Psi

Filed under: Jabber — Ephraim @ 11:22

Currently Psi supports that the messages you type in, are checked against a spellchecker.
But only for the from the system defined language, even the spellchecker would support more then that language.

So there is a  need (IMHO) for a selection while typing the message, cause the most user of Psi will min. speak two languages (english and the mothertounge).

Here is a alpha implementation of this, it will let you choose the language in the chatdlg. It’s far away from being tested overall, rather than it worked for me in the first view. It is worked out against current devel version of Psi (0.13-dev) from git.

Here is the patch:
multiple_spellchecker_languages_support.tar.gz

And here a image how it should look like if it has compiled successfully, of course with the languages  you have installed on your system ;)
example_multi_lang_spellchecker_lnx.png

The current implementation works only with aspell, which is used on windows and linux. But windows I never tried ;) . Build and quick try, worked for me:
example_multi_lang_spellchecker_win.png

So mac os x (10.5 or later only) is now supported too.
example_multi_lang_spellchecker_mac.png

And the patch which includes everything about multi language support for Psi spellchecker is here:
0001-overall-multiple-language-support-for-spellchecker.patch.zip


Constrains that I know are:

  • the patch only includes ui support for the chatdlg, muc I haven’t done yet.
  • the language combo box needs to recognize language changes / or on startup too,
    so it displays always the correct current language.

Ciao Ephraim

04.11.2008

Make Psi Deb Package

Filed under: Jabber — Ephraim @ 14:40

I always wondered howto create debian packages and always needed psi deb packages, so I just tried to create one package for psi. Two things done by one research :) .

And a step further; create a script which does the job for me. Just give it the source and the destination and it will bring me a psi deb package to my desktop.

For all who want to do this too, here is my script: mkpsideb.tar.gz

The usage is easy, as I said, the source directory and then the configure prefix directory and you are done. If some additional configure options are needed to compile psi on your desk, the third parameter is a direct passthrough to configure.

Example:
psi source is at ~/Desktop/psi-0.13
Script is placed at the Desktop.
so open up a terminal and do the following steps:

cd ~/Desktop
./mkpsideb.sh psi-0.13 /opt/psi-dev/0.13

And then you have a psi debian package right at your desktop.
But please, have a look into the Script before! You should min. change the maintainer setting at the very top variables.

Prerequisite is, that you can at least build psi manually.

ciao Ephraim

Powered by WordPress