ejabberd - Comments for "Ejabberd + msn transport acl restrictions not working."

Last month stats, and overall analysis

mfoss — Fri, 09 Nov 2007 10:18:15 +0000

teo wrote:

And for the last 6, 4, 3, 2, 1 months?

The only additional information I could get is this.

For the past month:

badlop		30 items
evadim		 8 items
syka		 8 items
snp		 5 items
zinid		 5 items
d.k.brazz	 4 items
jsMan		 4 items
owlmind		 4 items
yllsuarez	 4 items
teo		 3 items

I think the trend is quite clear: in the old days there were 3 people that answered all questions: Badlop, Sander, and Teo. In the last year both Sander and Teo has been completely inactive: no posts answering technical questions, only offtopic comments (like in this thread). While the other historic member (Badlop) has maintained (or increased a little) his comment ratio (and consequently the time invested in the project) to try to keep forum threads with at least an answer, as much as possible.

Another interesting change in the last year or so is that other people have started to answer questions. Looking at forum stats: Legoscia, Evadim, Mremond, D.k.brazz, Xram/Zinid, Bbrazell, K0NCTANT1N...

This trend is also visible in the mailing list and the chatroom: a lot of questions are nowadays answered by people that got involved in the last months, not by the people that was already present years ago. Unfortunately I don't know how to get statistics out of mailing list and chatroom logs.

teo wrote:

"ejabberd community" is now badlop only. So it's not surprising that it looks dead.

I have several comments for your analysis:

It's not surprising that it looks dead, as two of the three most old prolific participants left, and there isn't enough manpower to fill their absence.
In fact, it's not only me answering questions, there are other people. The stats show that nowadays there is more people actively involved in ejabberd than there were three years ago. The number of different people that help is greater now than before, but they don't answer all kind of questions, only the ones that they really know about. This ensures the quality of the answer. That's why I try to not only answer particular questions (Yes, No, Put this): I try to also explain the reasoning (Since, Because, Due to). I try to increase the public knowledge of how ejabberd/Erlang works, not only solve particular questions. And that consumes more time.
And most importantly: as ejabberd popularity growths, it's obvious that there are more questions to answer per week, in more strange operating systems, with more different topics of question. And the weirdness of the questions also growths. This means that the complexity of the questions increases, and consequently the time required to correctly answer them.

BTW, I think the intrinsic attractiveness that a software project may have decreases greatly when it doesn't get regular releases. And ejabberd doesn't get regular releases currently. The last feature release was a year ago. And I'm convinced this hurts ejabberd overall health. Not having a feature release reduces the number of support questions, but also reduces the interest of people that answer questions. Do you agree with me?

It's probably possible to get statistics from other time periods modifying Drupal source code. Are you interested in it? What interest do you have in those statistics?

And for the last 6, 4, 3, 2,

teo — Thu, 08 Nov 2007 06:35:09 +0000

And for the last 6, 4, 3, 2, 1 months?

Drupal statistics

mfoss — Wed, 07 Nov 2007 17:44:20 +0000

teo wrote:

"ejabberd community" is now badlop only. So it's not surprising that it looks dead.

Drupal provides some statistics about which users post more comments:

For All Time:

badlop		778 items
sander		399 items
teo		137 items
legoscia	118 items
mremond		 95 items
evadim		 58 items
xram@jabber.ru	 51 items
d.k.brazz	 35 items
breakevilaxis	 27 items
bbrazell	 23 items

For the past year:

badlop		273 items
legoscia	 65 items
evadim		 58 items
sander		 47 items
mremond		 39 items
d.k.brazz	 31 items
teo		 27 items
xram@jabber.ru	 26 items
K0NCTANT1N	 20 items
vinnitu		 17 items

"ejabberd community" is now

teo — Wed, 07 Nov 2007 17:04:27 +0000

"ejabberd community" is now badlop only. So it's not surprising that it looks dead.

I didnt have an opportunity

prozaker — Thu, 01 Nov 2007 01:25:48 +0000

I didnt have an opportunity to try that, i thank you for your help tho.

I moved to another XMPP server which i think will better serve my needs.

ejabberd's community seems great an all but, it doesnt seem as active.

Try removing the DEBUG code

mfoss — Fri, 21 Sep 2007 20:20:02 +0000

prozaker wrote:

=ERROR REPORT==== 2007-09-05 17:04:23 ===
E(<0.328.0>:ejabberd_hooks:187): {undef,
                                     [{ejabberd_logger,
                                          debug_msg,
                                          [mod_filter,
                                           32,
                                           "filtering packet...",
                                           []]},
                                      {mod_filter,filter_packet,1},
        ...
running hook: {filter_packet,[]}

For some reason erlang complains that a function in ejabberd_logger can't be found. The easy solution is to edit mod_filter.erl and remove this line:

?DEBUG("filtering packet...", []),

prozaker wrote: this server

mfoss — Fri, 21 Sep 2007 20:17:21 +0000

prozaker wrote:

this server is intended to be used in a local network, to restrict access to other msn contacts, and only allow those that are related to work.

all the people have their accounts as name@virtualhost.com

all of them are logging into the the msn service with their passport account, so they can use w/e domain they registered, in this case name@virtualhost.com

i can see the transport service on exodus and psi.

i can login with the admin account no problem, but i still see all of the passport users.

ACL and ACCESS in ejabberd_service is used to restrict which Jabber accounts can use the service. The fact that the service is a transport is not an ejabberd duty. If you want the transport to only show certain MSN contacts, it's a feature request in the transport.

As an update

prozaker — Thu, 06 Sep 2007 00:09:41 +0000

As an update

i tried mod_filter to see if it will work with this, but unfortunately i wasn't filtering any user.

its been almost a week without any kind of response, but it seems to me that this would be a common issue, and easily resolvable

can someone help me either with the acl's or with mod_filter to block certain msn users from being able to speak with the company's ejabberd users?

on the ejabberd log im getting several errors like this.

=ERROR REPORT==== 2007-09-05 17:04:23 ===
E(<0.328.0>:ejabberd_hooks:187): {undef,
                                     [{ejabberd_logger,
                                          debug_msg,
                                          [mod_filter,
                                           32,
                                           "filtering packet...",
                                           []]},
                                      {mod_filter,filter_packet,1},
                                      {ejabberd_hooks,run_fold1,4},
                                      {ejabberd_router,do_route,3},
                                      {ejabberd_router,route,3},
                                      {gen_iq_handler,handle_info,2},
                                      {gen_server,handle_msg,6},
                                      {proc_lib,init_p,5}]}
running hook: {filter_packet,[]}