Re: [prosody-dev] Re: Prosody LDAP plugins

> Can anyone point me in the right direction? > > Thanks for looking! > > > On Saturday, December 14, 2013 1:28:26 PM UTC-8, Rob Hoelz wrote: > > > > The change wouldn't actually be that bad; you just need to find the > > relevant portions of mod_ldap_

Re: [prosody-dev] Re: Prosody LDAP plugins

On Tue, 1 Jul 2014 09:28:36 -0700 (PDT) Stanislav Kopp wrote: > Not sure if this a right place to post, but does anybody have working > examples of "Multi-level fields" for vcard function? The > documentation >

Re: [prosody-dev] Re: Prosody LDAP plugins

> > I see all fields except "telephone" in jabber clent, so the mapping > works in general. No errors in prosody debug log. > > > Thanks for your help > > Am Dienstag, 1. Juli 2014 21:55:56 UTC+2 schrieb Rob Hoelz: > > > > On Tue, 1 Jul 2014 09:28:3

Re: [prosody-dev] Re: Prosody LDAP plugins

> telephone = { > { > work = 'telephoneNumber' > } > } >}, > > > I see all fields except "telephone" in jabber clent, so the mapping > works in general. No errors in prosody debug log. > > > Thanks for your help

[prosody-dev] Submitting new third party modules

Hi everyone, With the pending shutdown of Google Code, I have noticed that prosody-modules has moved to hg.prosody.im. What is the way for developers to submit new modules for Prosody going forward? Will some developers be granted push access to hg.prosody.im, or should we go with the "create

Re: [prosody-dev] Submitting new third party modules

On Thu, 30 Apr 2015 11:20:31 +0600 "Vadim A. Misbakh-Soloviov" wrote: > By the way, talking on module itself. > > I don't think tha way you did it is better than just putting the same > somewhere around pposix.c (or to use wrapper, as suggested in the > issue Matthew provided). > > Moreover, t