headers
Jonathan Dickinson | 1 Apr 13:52
Gravatar

APML and PubSub

Hi All,

 

I thought someone might want to do something interesting with this technology.

 

""APML allows users to share their own personal Attention Profile in much the same way that OPML allows the exchange of reading lists between News Readers. The idea is to compress all forms of Attention Data into a portable file format containing a description of ranked user interests.""

 

Given an APML binding for each PubSub node (e.g. “user interface”) a PubSub service could provide a user with a list of suggested nodes based on an APML document that they provide (via IQ or something): or automatically send them publications in any node based on each publications’ tags.

 

Furthermore, if the PubSub spec got a little ‘smarter’ the author could set the ‘affinity’ for each post’s tag: allowing them to indicate how well the post relates to the particular tag. This could be used to filter publications based on the “value” attribute in the APML. Thus:

 

Known APMLs:

Fred:

 Food 0.6

 User Interface 0.9

Jane

 Food 0.8

 User Interface 0.3

 

Subscriber Creates Publication:

 Food (3/5 = 0.6 – Invert = 0.4)

 Sends to  Fred and Jane

Another one:

 User Interface (2/5 = 0.4 – Invert = 0.6)

 Sends to  Fred

 

Just some hashing out of some ideas; I don’t have the time to really go at it. Just wanted to throw it out there and see what you all think: maybe someone will hop on it and write a XEP.

 

<http://www.apml.org/>

 

-- Jonathan

 

_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 0 comments |
headers
Matthew Wild | 1 Apr 18:58
Picon
Gravatar

[ANN] Prosody 0.4.0 Released

We are pleased to announce the release of Prosody 0.4.0.

It's no joke. We have spent most effort this release improving
Prosody internals, ensuring we have a solid base on which to build
future features. Numerous bugs have been fixed and we recommend
that all users of 0.3.0 upgrade.

That said, we do have a few new things in this release, namely
roster versioning (allowing clients to cache the roster, instead
of downloading it each time they connect) and support for external
components, allowing the use of gateways/transports and other services.

Prosody is a lightweight Jabber/XMPP server written in Lua. It aims
to be flexible, easy to extend, and simple to use for both users
and developers alike.

The following is a summary of changes since the previous version:

   * Numerous stability fixes (highly recommended 0.3 users upgrade)
   * XEP-0114 support for external components (experimental)
   * mod_xmlrpc: Allow RPC calls over HTTP/XMPP to command a server
   * Roster versioning, to allow faster logins (experimental)
   * Fix BOSH race condition with multiple idle sessions
   * Handle missing <priority> in initial client presence
   * Fix for correct pass-through of stanzas with prefixed attributes
   * Fix routing of some stanzas directed to bare JIDs
   * Config improvements, better error reporting, Include command
   * SASL ANONYMOUS support for anonymous login when enabled
   * mod_version now reports OS type (configurable)
   * MUC: Support PMs, vCards, and misc. reliability fixes
   * Module API: Add stanza.clone, timers, and more
   * Various logging improvements

We would appreciate feedback from those testing roster versioning -
we are aware of no clients that support it currently, but hopefully
that can soon change.

Testing external component support would greatly help too, there
are many different components, and we have only tried a couple.

All of the known issues listed in the previous release have been fixed.

Download: http://prosody.im/download/

Happy Jabbering,
  The Prosody Team
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 0 comments |
headers
Simon Tennant | 1 Apr 21:10
Favicon
Gravatar

Re: update on XMPP location (wherein beer is offered)

Stephen Pendleton wrote:
> I like this a lot. How does the "nearby" query work? Does it returned
> bookmarked places that are owned by the submitting jid, or any bookmarked
> place nearby? What is "cellpatternquality" mean?
A place can have one of two modes.

    * Public places are those that can be shared with other people. Eg
      my placemark for Starbucks would be useful to others.
    * Private places are those that will not be shared with others. For
      example my placemark called "Home sweet home" is probably not
      useful to others on the network (and/or I want it to be private to
      just me and only shared with my friends).

butler.buddycloud.com will only show public in a nearby query. These
will be public places from all users. Additionally you can subscribe to
a place which then places it on your own list of places that you are
placed at in the future.

CellPatternQuality reflects the certainty of the place.  How "distinct"
it is. For example when you are driving the location butler will be
seeing lots of new wifi and cell towers. Saving a placemark at that
point will save it but it will be a "blurry" pattern in the database. 
Better would be to wait a moment, submit a couple more location queries,
watch for the cellpatternquality to increase to 100% and then send a
placemark save stanza.  Then the butler will be far more likely to
accurately place you back at that point in the future.

> Also, how does the component push my location to my PEP node if I am on
> another server? Would this be allowed by XMPP servers? I would be
> interested
> in seeing these stanzas though to test it out.
Indeed for non-buddycloud.com domains PEP would not work. There are two
solutions for this that we are looking at. Either:

    * having the remote non buddycloud node publish their own pep node
      after getting a reply to their location query stanza or
    * granting publisher rights to butler.buddycloud.com on your own
      pubsub geoloc node and passing the address to this node as part of
      the location query. The query results would then be published on
      your behalf in XEP-0080 (user location) format as well as being
      returned to the client.

> There is another application we are working on that involves XEP-0255. It
> currently supports what you are calling "beacon logs" stanzas to
> return back
> postal addresses. The system uses a combination of wifi access
> points/mobile
> towers to pinpoint your position and return back a lat/lon. It is very
> accurate in a populated area.
The butler does a best effort on the lookup of lat/long too and
publishes it as part of the XEP-0080 stack. I don't think we fill out
the post code for general locations (we do for known places) but this
could presumably be added with access to the right lat/long -> postcode
mapping tables.  It's not something that we have spent too much time on.
Our main efforts in butler development have focused on making location
something social by describing it as known places like home or work or
"on the road in munich" (travelling) or  "near  Jo's house" for example.

S.

--

-- 
Simon Tennant
Buddycloud
uk: +44 20 7043 6756               de: +49 89 420 955 854  
uk: +44 78 5335 6047               de: +49 17 8545 0880
email and xmpp: simon <at> buddycloud.com
http://buddycloud.com

_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 6 comments |
headers
Peter Saint-Andre | 3 Apr 03:23
Favicon

jabber.org account registration policy

http://www.jabber.org/index.php/2009/04/account-registration-policy/ says:

The Jabber.org IM service has instituted a new account registration
policy. Until further notice, IM accounts can be registered only via the
web at register.jabber.org, which means that our longtime practice of
allowing in-band registration using an IM client has been disabled.

You will notice that register.jabber.org requires you to complete a
“CAPTCHA” test in order to create an account. This is a security measure
to help prevent bulk account creation by automated processes. We might
deploy further account security measures in the future, and will
announce any such changes at the jabber.org website.

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Attachment (smime.p7s): application/x-pkcs7-signature, 6751 bytes
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 3 comments |
headers
Peter Saint-Andre | 3 Apr 06:17
Favicon

client developers take note: list of IM services

Because of yet another jabber.org website change, we've moved the XML
file that provides an automated listing of the public XMPP servers.

Originally it was here: http://jabber.org/servers.xml

Then it was here: http://jabber.org/basicservers.xml

Now it is here: http://xmpp.org/services/services.xml

HTTP redirects are supposed to be in place, but there is no guarantee
that they are working. Please verify and let me know.

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Attachment (smime.p7s): application/x-pkcs7-signature, 6751 bytes
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 2 comments |
headers
Robin Redeker | 3 Apr 10:44
Picon
Favicon

Re: client developers take note: list of IM services

On Thu, Apr 02, 2009 at 10:17:08PM -0600, Peter Saint-Andre wrote:
> Because of yet another jabber.org website change, we've moved the XML
> file that provides an automated listing of the public XMPP servers.
> 
> Originally it was here: http://jabber.org/servers.xml
> 
> Then it was here: http://jabber.org/basicservers.xml
> 
> Now it is here: http://xmpp.org/services/services.xml
> 
> HTTP redirects are supposed to be in place, but there is no guarantee
> that they are working. Please verify and let me know.

http://www.jabber.org/servers.xml redirects to http://xmpp.org/software/servers.shtml

which is a list of server software...

And http://jabber.org/basicservers.xml is a redirect to http://www.jabber.org/basicservers.xml
which is a redirect to http://www.xmpp.org/services/services.xml

And http://xmpp.org/services/services.xml is 404 Not Found.

Greetings,
   Robin

--

-- 
Robin Redeker                         | Deliantra, the free code+content MORPG
elmex <at> ta-sa.org / r.redeker <at> gmail.com | http://www.deliantra.net
http://www.ta-sa.org/                 |
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 1 comment |
headers
Peter Saint-Andre | 3 Apr 15:11
Favicon

Re: client developers take note: list of IM services

On 4/3/09 2:44 AM, Robin Redeker wrote:
> On Thu, Apr 02, 2009 at 10:17:08PM -0600, Peter Saint-Andre wrote:
>> Because of yet another jabber.org website change, we've moved the XML
>> file that provides an automated listing of the public XMPP servers.
>>
>> Originally it was here: http://jabber.org/servers.xml
>>
>> Then it was here: http://jabber.org/basicservers.xml
>>
>> Now it is here: http://xmpp.org/services/services.xml
>>
>> HTTP redirects are supposed to be in place, but there is no guarantee
>> that they are working. Please verify and let me know.
> 
> http://www.jabber.org/servers.xml redirects to http://xmpp.org/software/servers.shtml

Fixed.

> which is a list of server software...
> 
> And http://jabber.org/basicservers.xml is a redirect to http://www.jabber.org/basicservers.xml
> which is a redirect to http://www.xmpp.org/services/services.xml

Fixed.

> And http://xmpp.org/services/services.xml is 404 Not Found.

Fixed.

Thanks for testing!

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Attachment (smime.p7s): application/x-pkcs7-signature, 6751 bytes
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 0 comments |
headers
Sander Devrieze | 3 Apr 18:34

Re: jabber.org account registration policy

2009/4/3 Peter Saint-Andre <stpeter <at> stpeter.im>:
> http://www.jabber.org/index.php/2009/04/account-registration-policy/ says:
>
> The Jabber.org IM service has instituted a new account registration
> policy. Until further notice, IM accounts can be registered only via the
> web at register.jabber.org, which means that our longtime practice of
> allowing in-band registration using an IM client has been disabled.

Would it be possible to remove jabber.org from
http://xmpp.org/services/services.xml ? I think that list makes no
sense when it contains services which are not in-band registration
capable...

--

-- 
Mvg, Sander Devrieze.
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 2 comments |
headers
naw | 4 Apr 14:30
Picon

Re: jabber.org account registration policy

El Viernes 03 Abril 2009, Sander Devrieze escribió:
> 2009/4/3 Peter Saint-Andre <stpeter <at> stpeter.im>:
> > http://www.jabber.org/index.php/2009/04/account-registration-policy/
> > says:
> >
> > The Jabber.org IM service has instituted a new account registration
> > policy. Until further notice, IM accounts can be registered only via the
> > web at register.jabber.org, which means that our longtime practice of
> > allowing in-band registration using an IM client has been disabled.
>
> Would it be possible to remove jabber.org from
> http://xmpp.org/services/services.xml ? I think that list makes no
> sense when it contains services which are not in-band registration
> capable...

I think that it mades sense to have a list of federated servers. It can be 
useful for other things. But maybe there should be some aditional information 
about the servers (if they support in-band registration), or maybe several 
lists (e.g. one for all servers, another one for servers wich support 
in-band...)

Also, if in-band registration is going to be less used by servers until the 
implementation of XEP-0158 (captchas) in servers and clients, it could be 
also useful to provide the registration address as a child element in the 
list.

--

-- 

Jabber-ID: lambda512 <at> jabberes.org lambda512 <at> gmail.com
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 1 comment |
headers
Peter Saint-Andre | 4 Apr 21:13
Favicon

Re: jabber.org account registration policy

On 4/4/09 6:30 AM, naw wrote:
> El Viernes 03 Abril 2009, Sander Devrieze escribió:
>> 2009/4/3 Peter Saint-Andre <stpeter <at> stpeter.im>:
>>> http://www.jabber.org/index.php/2009/04/account-registration-policy/
>>> says:
>>>
>>> The Jabber.org IM service has instituted a new account registration
>>> policy. Until further notice, IM accounts can be registered only via the
>>> web at register.jabber.org, which means that our longtime practice of
>>> allowing in-band registration using an IM client has been disabled.
>> Would it be possible to remove jabber.org from
>> http://xmpp.org/services/services.xml ? I think that list makes no
>> sense when it contains services which are not in-band registration
>> capable...

Done.

> I think that it mades sense to have a list of federated servers. It can be 
> useful for other things. But maybe there should be some aditional information 
> about the servers (if they support in-band registration), or maybe several 
> lists (e.g. one for all servers, another one for servers wich support 
> in-band...)

I think it's best if services.xml includes only services that support
in-band registration (IBR), because this file is used by clients to
present a list of services for account registration.

> Also, if in-band registration is going to be less used by servers until the 
> implementation of XEP-0158 (captchas) in servers and clients, it could be 
> also useful to provide the registration address as a child element in the 
> list.

Given the recent (and growing) problems with automated processes
registering large numbers of accounts on public XMPP services, I think
that IBR will soon become unworkable without XEP-0158 support in clients
and servers. Until that happens, we will diable IBR at jabber.org (and I
expect many other public XMPP services to do the same). IBR was a great
idea back in 1999 when no one had ever heard of Jabber, but these days
it is very close to hazardous for the health of the network.

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Attachment (smime.p7s): application/x-pkcs7-signature, 6751 bytes
_______________________________________________
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: JDev-unsubscribe <at> jabber.org
_______________________________________________
Permalink | Reply | 0 comments |

Gmane