ejabberd cool coder required

If you want to get your hands dirty in ejabberd goodness and have a more erlang'iang brain than my own, here is a simple request: hack and slash into the PEP code, and allow the use of an ACL to decide which users (JIDs) can publish to the node. Bonus points if you limit the nodes/namespaces to which I can publish to.

I need to authorize a trusted external component to publish into PEP nodes hosted at my domain.

The final goal is to bridge Fire Eagle to User Location (XEP-0080). It goes like this:

• you use Fire Eagle to publish your location;
• you then visit a site I'm working on and tell me that yes, you want to publish your location into you PEP node. PEP nodes are only visible to your roster buddies BTW, so privacy issues should be ok;
• I start polling the Fire Eagle service (yeah, this is the sucky-part) and publish any changes of your location to your PEP node.

In an ideal world, I should be able to request permission to publish to the JID PEP node, you would get a nice little message with that, and you would give you permission. But support for pubsub in clients is still very poor, so we have to use this ACL-in-server-hack.

Mind you that this required cooperation of server operators to authorize publishing to PEP nodes. Again, its the best we can do right now.

Also, an ideal Fire Eagle API would also notify me with Web Hooks that the presence of users I subscribe to was changed.

(hey, and if you are reading this and are currently at ETech 2008, please talk to any Fire Eagle developer you can get your hands on and ask them politely to support Web Hooks).