Mickaël Rémond | 3 Mar 20:10 2008
Picon

64-bits installer for ejabberd update

Hello,

We have released a fix for ejabberd 2.0.0 binary installer 64 bits version.
It fix binary library problem that can prevent ejabberd from starting under some recent 64-bits Linux distributions.

The new 64bits is available from ejabberd download page:

-- 
Mickaël Rémond



_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Pedro Melo | 6 Mar 09:12 2008

pubsub god-mode

Hi,

is it possible to create an ACL in 2.0.0 that allows a specific JID  
to update my PEP/PIP nodes?

I was toying with the idea of writing a component that pools the new  
fire eagle yahoo service [1] for my users location and updates their  
own Geo loc [2] PEP nodes.

At least we could have a real notification service...

But without some ACL inside ejabberd telling him, that yes, my  
service is trusted to do that, I really don't see any way to mary the  
big wide web with the cool xmpp universe.

In a future universe, when pubsub support in clients, I could  
probably ask the user via XMPP to do this, but right now, I'm just  
doing this over the web, also because I need to do the OAuth dance  
that the API requires.

Thanks in advance for any kind soul that has a more erlang'iang brain  
than my own,

PS: I'm willing and eager to test patches ;)
--

-- 
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo <at> simplicidade.org
Use XMPP!
bryan rasmussen | 9 Mar 14:45 2008
Picon

XMPP specs appropriate for exchanging data, not instant messaging, and their implementation

Hi,

I'm just wondering if anyone can point to any specifications from
xmpp.org that are implemented in Ejabberd, or eventually in other
jabber servers, that are appropriate to data exchange.

Thanks,
Bryan Rasmussen
Pedro Melo | 9 Mar 14:48 2008

Re: XMPP specs appropriate for exchanging data, not instant messaging, and their implementation

Hi,

On Mar 9, 2008, at 1:45 PM, bryan rasmussen wrote:
> I'm just wondering if anyone can point to any specifications from
> xmpp.org that are implemented in Ejabberd, or eventually in other
> jabber servers, that are appropriate to data exchange.

data exchange is pretty vague... I could argue that everything in  
XMPP is data exchange.

What kind of data are you thinking off? Atom feeds? Images? URLs?  
other type?

Best regards,
--

-- 
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo <at> simplicidade.org
Use XMPP!
Christophe Romain | 10 Mar 12:12 2008
Picon

Re: pubsub god-mode

Hi,

> is it possible to create an ACL in 2.0.0 that allows a specific JID
> to update my PEP/PIP nodes?

by now, the only ACL usable in pubsub is access_createnode
it allows do deny some users to create nodes.
yes, it's possible to also add an acl for passing to publish_item  
function.

ACL is fetched from the configuration in init function. you can add  
here an access_publishitem acl.
see iq_pubsub function, it passes Access parameter to create_node.
Here it can handle Access as a proplists, and pass access_createnode  
to create_node function, and access_publishitem to publish_item  
function.

finally, in create_node function you see that the acl match is done  
by the create_node_permission plugin's function.
you should do the same with the publish_item, creating a  
publish_item_permission function in the plugin.
Pedro Melo | 12 Mar 14:14 2008

PEP and Filtered Notifications in ejabberd

Hi,

just a quick clarification: to use filtered notifications with  
ejabberd PEP implementation, the client must support XEP-0115  
capabilities, right?

Its not enough to place the proper features in the disco#info  
response, right?

If so, do you have a minimal xep-0115 version required?

Thanks in advance,
--

-- 
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo <at> simplicidade.org
Use XMPP!
Magnus Henoch | 12 Mar 17:03 2008
Picon

Re: PEP and Filtered Notifications in ejabberd

Pedro Melo <melo <at> simplicidade.org> writes:

> just a quick clarification: to use filtered notifications with  
> ejabberd PEP implementation, the client must support XEP-0115  
> capabilities, right?

Correct.  If the client doesn't support XEP-0115, it gets no
notifications at all.

> Its not enough to place the proper features in the disco#info  
> response, right?

Correct.

> If so, do you have a minimal xep-0115 version required?

Both 1.3, 1.4 and 1.5 should work.

--

-- 
Magnus
JID: legoscia <at> jabber.cd.chalmers.se
Pedro Melo | 13 Mar 11:34 2008

Re: PEP and Filtered Notifications in ejabberd

Thanks Magnus.

On Mar 12, 2008, at 4:03 PM, Magnus Henoch wrote:
> Pedro Melo <melo <at> simplicidade.org> writes:
>
>> just a quick clarification: to use filtered notifications with
>> ejabberd PEP implementation, the client must support XEP-0115
>> capabilities, right?
>
> Correct.  If the client doesn't support XEP-0115, it gets no
> notifications at all.
>
>> Its not enough to place the proper features in the disco#info
>> response, right?
>
> Correct.
>
>> If so, do you have a minimal xep-0115 version required?
>
> Both 1.3, 1.4 and 1.5 should work.
>
> -- 
> Magnus
> JID: legoscia <at> jabber.cd.chalmers.se
>
> _______________________________________________
> ejabberd mailing list
> ejabberd <at> jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd

--

-- 
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo <at> simplicidade.org
Use XMPP!
Taylor Laramie | 14 Mar 12:58 2008
Picon

Patch Submission for mod_ctlextra

I made some quick additions to mod_ctlextra and thought they might make 
a desirable addition to the module since in it's current state it 
doesn't really offer much in the way of retrieving info for shared rosters.

Name : srg-get-shared
Usage : ejabberctl ejabberd <at> localhost srg-get-shared <vhost>
Returns : a list of ':' separated values that represent all the Shared 
Rosters for that particular host e.g : Shared Roster1:Shared 
Roster2:somethingelse:

Name : srg-shared-info
Usage : ejabberctl ejabberd <at> localhost srg-shared-info <group> <vhost>
Returns : the values for of 'Name' and 'Description' for the provided 
SR. I was actually attempting to make this more verbose in that it would 
take another directive ('Detail') which would return either 
'Name','Description','Display','Members' or All though my skills with 
erlang are lacking at this point.

Being that, as I said, my erlang isn't that great I fully expect that 
these can be written better / more efficiently so feel free (the powers 
that be) to rework them accordingly if they could potentially cause 
issues. Attached is a diff made from the latest SVN though let me know 
if another format would be preferred.

--- mod_ctlextra.svn	2008-03-14 01:15:01.000000000 -0700
+++ src/mod_ctlextra.erl	2008-03-13 02:03:16.000000000 -0700
 <at>  <at>  -59,6 +59,8  <at>  <at> 
      {"srg-delete group host", "delete the group"},
      {"srg-user-add user server group host", "add user <at> server to group on host"},
      {"srg-user-del user server group host", "delete user <at> server from group on host"},
+     {"srg-get-shared host", "get list of shared rosters from host"},
+     {"srg-shared-info group host detail", "get list of shared rosters from host"},
 
      %% mod_vcard
      {"vcard-get user host data [data2]", "get data from the vCard of the user"},
 <at>  <at>  -179,10 +181,20  <at>  <at> 
     {atomic, ok} = mod_shared_roster:add_user_to_group(Host, {User, Server}, Group),
     ?STATUS_SUCCESS;
 
-ctl_process(_Val, ["srg-user-del", User, Server, Group, Host]) ->
+ctl_process(_Val, ["srg-user-del", User, Server, Group, Host ]) ->
     {atomic, ok} = mod_shared_roster:remove_user_from_group(Host, {User, Server}, Group),
     ?STATUS_SUCCESS;
 
+ctl_process(_Val, ["srg-get-shared", Host]) ->
+	lists:foreach(fun(SrgGroup) -> io:format("~s:",[SrgGroup]) end, lists:sort(mod_shared_roster:list_groups(Host))),
+	io:fwrite("~n"),
+    ?STATUS_SUCCESS;
+
+ctl_process(_Val, ["srg-shared-info", Group, Host ]) ->
+	io:format("~s",[ X || {name , X} <- lists:sort(mod_shared_roster:get_group_opts(Host,Group))]),
+	io:format("::~s~n",[ X || {description , X} <- lists:sort(mod_shared_roster:get_group_opts(Host,Group))]),
+	?STATUS_SUCCESS;
+
 ctl_process(_Val, ["add-rosteritem", LocalUser, LocalServer, RemoteUser, RemoteServer, Nick,
Group, Subs]) ->
     case add_rosteritem(LocalUser, LocalServer, RemoteUser, RemoteServer, Nick, Group,
list_to_atom(Subs), []) of
 	{atomic, ok} ->
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Peter Saint-Andre | 17 Mar 20:47 2008

MUC archives in .txt files?

Can ejabberd (2.0.0?) output multi-user chat archives to .txt files
instead of .html? I seem to recall that earlier versions of ejabberd
(e.g., 1.0) had this feature, but in 1.1.3 I see only the html option in
the room configuration and config file. I know a significant possible
deployment that needs this feature.

Thanks!

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/

Attachment (smime.p7s): application/x-pkcs7-signature, 9 KiB
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

Gmane