PUBLIC MARKS from greut with tag xmpp

Many web resources provide mechanisms for subscribing to changes in their content. However, this change information is only made available via a polling mechanism.

A number of people have proposed mechanisms for subscribing to updates to pages or feeds, however, a missing element of all these proposals is a subscription mechanism. Sadly, this means that every site supporting this feature will likely end up with a different implementation.

Get Pingd pour la mise à mort de la syndication... (à coups de XRDS, d'Atom et de web hooks, tout un programme)

Building an XMPP-enabled Fire Eagle application is very similar to building a traditional web-based application. In fact, the XMPP componentry is intended to complement an existing application, simplifying it and imbuing it with real-time capabilities.

Piece of cake, not really. Nice usage of oAuth-over-XMPP though

Sμblog (pronounced sub-log) is is my attempt to combine ideas about microblogging, messaging and the sematic web into a practical tool ready for everyday work.

XMPP to RDF microblogging tool, quite nice and well documented.

Speeqe is a web based, group chat client that works with the XMPP/MUC protocol.

and open source since a couple of days.

how to build a fast and efficient XMPP bot that lives in ejabberd.

doing a bot as a client instead of a server module seems outdated already.

Punjab is a HTTP jabber client interface. It is a SOAP, XMLRPC, XEP-0025 or XEP-0124 server that allows persistent client connections to a jabber server. It can be used for many things, but its main purpose is to allow for stateless applications (ie web) a stateful connection to jabber.

let enter the BOSH era

Pubsub nodes are organized in a hierarchical tree, similar to a file system. mod_pubsub imposes a special structure on this tree. There is a special node, pubsub/nodes, that contains all other created nodes. Nodes of users have names like home/server/username/whatever. If you try to create a node whose name doesn't fit that pattern, you will get an error. If you don't specify a name (i.e. create an instant node), the server generates a name that fits this pattern

Some says that it's the future of feeds, at least server-to-server subscriptions.

As noted above, if a connected resource does not request the roster during a session, it SHOULD never receive presence subscriptions and the associated roster pushes.

finally know why my bot was an epic failure.