[jitsi-users] Synchronizing contacts across multiple Linux machines (without LDAP or Google)


#1

Has anybody successfully found a way to synchronize the jitsi contacts
across multiple Linux machines ? I want to have my phonebook that I use
via SIP synced on my home machine and my netbook.
I do not have an LDAP server at hand and I do not want to use Google.
I was just trying it with Spideroak by symlinking contactlist.xml in the
.jitsi folder to a file in my synchronized Spideroak folder, but I got
file corruption (duplicate contacts etc.) the moment more than one
computer had jitsi running at the same time - and Spideroak was syncing
like mad.
Until jitsi supports at least one Linux addressbook (EDS?), integrates
with the Thunderbird addressbook etc., it would be great if:
- there would be an option to store manually created contacts in a
different location.
- the file would only be accessed for reading or while a contact is
added manually. No jabber buddies, Google contacts or other
automatically synced contacts would be stored in contactlist.xml. If
this is needed there could be a second "contactcache.xml" file.


#2

Hey Mark,

Using the same file instance would indeed not work. If you only need
this for SIP however, then you could probably get what you want with an
XCAP server.

Cheers,
Emil

···

On 13.01.13, 16:58, Mark Dammer wrote:

Has anybody successfully found a way to synchronize the jitsi contacts
across multiple Linux machines ? I want to have my phonebook that I use
via SIP synced on my home machine and my netbook.
I do not have an LDAP server at hand and I do not want to use Google.
I was just trying it with Spideroak by symlinking contactlist.xml in the
.jitsi folder to a file in my synchronized Spideroak folder, but I got
file corruption (duplicate contacts etc.) the moment more than one
computer had jitsi running at the same time - and Spideroak was syncing
like mad.
Until jitsi supports at least one Linux addressbook (EDS?), integrates
with the Thunderbird addressbook etc., it would be great if:
- there would be an option to store manually created contacts in a
different location.
- the file would only be accessed for reading or while a contact is
added manually. No jabber buddies, Google contacts or other
automatically synced contacts would be stored in contactlist.xml. If
this is needed there could be a second "contactcache.xml" file.

--
https://jitsi.org


#3

Hello Emil,
thanks for your reply and the good work that goes into Jitsi. How is the
situation regarding addressbook integration on Linux ? My proposal would
be to give priority to Thunderbird addressbook integration. I would like
this idea, because it would allow an opensource office system that could
run on Linux, Windows and Mac. This systems components would be:
Jitsi - VoIP and instant communication
Thunderbird - email and addressbook
LibreOffice - can use TBs addressbook.

BTW: The Thunderbird addressbook can easily synchronized via plugin over
IMAP / filesharing / Spideroak / Dropbox.

all the best,
Mark

···

On 16/01/13 03:27, Emil Ivov wrote:

Hey Mark,

Using the same file instance would indeed not work. If you only need
this for SIP however, then you could probably get what you want with an
XCAP server.

Cheers,
Emil

On 13.01.13, 16:58, Mark Dammer wrote:

Has anybody successfully found a way to synchronize the jitsi contacts
across multiple Linux machines ? I want to have my phonebook that I use
via SIP synced on my home machine and my netbook.
I do not have an LDAP server at hand and I do not want to use Google.
I was just trying it with Spideroak by symlinking contactlist.xml in the
.jitsi folder to a file in my synchronized Spideroak folder, but I got
file corruption (duplicate contacts etc.) the moment more than one
computer had jitsi running at the same time - and Spideroak was syncing
like mad.
Until jitsi supports at least one Linux addressbook (EDS?), integrates
with the Thunderbird addressbook etc., it would be great if:
- there would be an option to store manually created contacts in a
different location.
- the file would only be accessed for reading or while a contact is
added manually. No jabber buddies, Google contacts or other
automatically synced contacts would be stored in contactlist.xml. If
this is needed there could be a second "contactcache.xml" file.


#4

Hey Mark,

Hello Emil,
thanks for your reply and the good work that goes into Jitsi.

Thank you for your kind words!

How is the
situation regarding addressbook integration on Linux ? My proposal would
be to give priority to Thunderbird addressbook integration.

We were planning on doing that at one point but then had a look at the
situation and decide it to defer it. We didn't find any easy to use APIs
to access thunderbird's address book and it didn't seem like accessing
them directly would be that trivial either. In the end we decided to go
for Google Contacts instead.

We like the idea though, so if there's an easy way to access thunderbird
contacts, we can add it to our todo list again.

Cheers,
Emil

···

On 17.01.13, 15:07, Mark Dammer wrote:

I would like
this idea, because it would allow an opensource office system that could
run on Linux, Windows and Mac. This systems components would be:
Jitsi - VoIP and instant communication
Thunderbird - email and addressbook
LibreOffice - can use TBs addressbook.

BTW: The Thunderbird addressbook can easily synchronized via plugin over
IMAP / filesharing / Spideroak / Dropbox.

all the best,
Mark

On 16/01/13 03:27, Emil Ivov wrote:

Hey Mark,

Using the same file instance would indeed not work. If you only need
this for SIP however, then you could probably get what you want with an
XCAP server.

Cheers,
Emil

On 13.01.13, 16:58, Mark Dammer wrote:

Has anybody successfully found a way to synchronize the jitsi contacts
across multiple Linux machines ? I want to have my phonebook that I use
via SIP synced on my home machine and my netbook.
I do not have an LDAP server at hand and I do not want to use Google.
I was just trying it with Spideroak by symlinking contactlist.xml in the
.jitsi folder to a file in my synchronized Spideroak folder, but I got
file corruption (duplicate contacts etc.) the moment more than one
computer had jitsi running at the same time - and Spideroak was syncing
like mad.
Until jitsi supports at least one Linux addressbook (EDS?), integrates
with the Thunderbird addressbook etc., it would be great if:
- there would be an option to store manually created contacts in a
different location.
- the file would only be accessed for reading or while a contact is
added manually. No jabber buddies, Google contacts or other
automatically synced contacts would be stored in contactlist.xml. If
this is needed there could be a second "contactcache.xml" file.

--
https://jitsi.org


#5

Off and on for the past year or so, Mike Conley has been working on a new Address Book for Thunderbird. For details see:
http://mikeconley.ca/blog/2012/08/23/rambling-about-a-new-address-book-for-thunderbird/

I submitted a comment on Conley's blog post asking about address book APIs and linked to this thread.

David

···

On 1/18/2013 1:03 PM, Emil Ivov wrote:

On 17.01.13, 15:07, Mark Dammer wrote:

How is the
situation regarding addressbook integration on Linux ? My proposal would
be to give priority to Thunderbird addressbook integration.

We were planning on doing that at one point but then had a look at the
situation and decide it to defer it. We didn't find any easy to use APIs
to access thunderbird's address book and it didn't seem like accessing
them directly would be that trivial either. In the end we decided to go
for Google Contacts instead.

We like the idea though, so if there's an easy way to access thunderbird
contacts, we can add it to our todo list again.

Cheers,
Emil


#6

Does Jitsi support LDAP write or do I need another application to create
entries on LDAP ?
I understand the problems with TBs addressbook and the generic problem
of the addressbook diversity on Linux. I think I will try running an
LDAP server to solve the problem. Although I have worked with openldap
before I find the ApacheDS interesting - it is java based like jitsi but
might be a bit of overkill as a local addressbook store.

cheers, Mark

···

On 19/01/13 06:52, David Bolton wrote:

On 1/18/2013 1:03 PM, Emil Ivov wrote:

On 17.01.13, 15:07, Mark Dammer wrote:

How is the
situation regarding addressbook integration on Linux ? My proposal
would
be to give priority to Thunderbird addressbook integration.

We were planning on doing that at one point but then had a look at the
situation and decide it to defer it. We didn't find any easy to use APIs
to access thunderbird's address book and it didn't seem like accessing
them directly would be that trivial either. In the end we decided to go
for Google Contacts instead.

We like the idea though, so if there's an easy way to access thunderbird
contacts, we can add it to our todo list again.

Cheers,
Emil

Off and on for the past year or so, Mike Conley has been working on a
new Address Book for Thunderbird. For details see:
http://mikeconley.ca/blog/2012/08/23/rambling-about-a-new-address-book-for-thunderbird/

I submitted a comment on Conley's blog post asking about address book
APIs and linked to this thread.

David


#7

Does Jitsi support LDAP write or do I need another application to create
entries on LDAP ?

No, we only perform lookups in the LDAP Database.

I understand the problems with TBs addressbook and the generic problem
of the addressbook diversity on Linux. I think I will try running an
LDAP server to solve the problem. Although I have worked with openldap
before I find the ApacheDS interesting - it is java based like jitsi but
might be a bit of overkill as a local addressbook store.

cheers, Mark

Ingo


#8

o.k. thanks for the quick reply.
I love jitsi, but the lack of addressbook support on Linux is a problem
(for me). And to be honest I do not like the idea of GoogleContacts for
the same reason that makes me to migrate from Skype to Jitsi: Privacy
and transparency about data use etc. Google knows enough about me already.
Would it be very difficult to implement at least a simple (xml) file
based local addressbook as addressbook source so that it can be easily
backed up / replicated across machines ? As I posted before the current
xml file does not work as it is updated automatically by the XMPP based
accounts. So an option that would allow to choose the storage location
when you choose "local" as addressbook source (for a SIP account) would
be my feature request.
Sadly I am not very Java literate, otherwise I would love to help.

cheers, Mark

···

On 23/01/13 10:45, Ingo Bauersachs wrote:

Does Jitsi support LDAP write or do I need another application to create
entries on LDAP ?

No, we only perform lookups in the LDAP Database.

I understand the problems with TBs addressbook and the generic problem
of the addressbook diversity on Linux. I think I will try running an
LDAP server to solve the problem. Although I have worked with openldap
before I find the ApacheDS interesting - it is java based like jitsi but
might be a bit of overkill as a local addressbook store.

cheers, Mark

Ingo


#9

o.k. thanks for the quick reply.
I love jitsi, but the lack of addressbook support on Linux is a problem
(for me). And to be honest I do not like the idea of GoogleContacts for
the same reason that makes me to migrate from Skype to Jitsi: Privacy
and transparency about data use etc. Google knows enough about me already.
Would it be very difficult to implement at least a simple (xml) file
based local addressbook as addressbook source so that it can be easily
backed up / replicated across machines ?

Shouldn't be too difficult, but I'm afraid that we cannot afford the time to
do that currently. We really want to get out 2.0 and the focus there is to
fix broken or already begun stuff rather than beginning new features again.

We have a similar request to embed an external address book (e.g. from a
webserver) in our bugtracker. You might want to add your comments to it. I
don't remember the ID right now, but I think it was from the user "vieri".

As I posted before the current
xml file does not work as it is updated automatically by the XMPP based
accounts. So an option that would allow to choose the storage location
when you choose "local" as addressbook source (for a SIP account) would
be my feature request.
Sadly I am not very Java literate, otherwise I would love to help.

Contributions would certainly help. Java is not that hard :slight_smile:
If you want to take a look, the class
net.java.sip.communicator.service.contactsource.ContactSourceService would
be the starting point.

cheers, Mark

Regards,
Ingo


#10

I have just finished setting up Eclipse and got jitsi running. I will
see how it goes ....
cheers, Mark

···

On 23/01/13 16:16, Ingo Bauersachs wrote:

o.k. thanks for the quick reply.
I love jitsi, but the lack of addressbook support on Linux is a problem
(for me). And to be honest I do not like the idea of GoogleContacts for
the same reason that makes me to migrate from Skype to Jitsi: Privacy
and transparency about data use etc. Google knows enough about me already.
Would it be very difficult to implement at least a simple (xml) file
based local addressbook as addressbook source so that it can be easily
backed up / replicated across machines ?

Shouldn't be too difficult, but I'm afraid that we cannot afford the time to
do that currently. We really want to get out 2.0 and the focus there is to
fix broken or already begun stuff rather than beginning new features again.

We have a similar request to embed an external address book (e.g. from a
webserver) in our bugtracker. You might want to add your comments to it. I
don't remember the ID right now, but I think it was from the user "vieri".

As I posted before the current
xml file does not work as it is updated automatically by the XMPP based
accounts. So an option that would allow to choose the storage location
when you choose "local" as addressbook source (for a SIP account) would
be my feature request.
Sadly I am not very Java literate, otherwise I would love to help.

Contributions would certainly help. Java is not that hard :slight_smile:
If you want to take a look, the class
net.java.sip.communicator.service.contactsource.ContactSourceService would
be the starting point.

cheers, Mark

Regards,
Ingo