(I sent this to a couple of lists already, but i though it might also be interresting for the research community)
Hi all! For a long time I wanted a decent push interface for RecentChanges-Events, so it becomes easy to follow changes on a wiki. Parsing messages on IRC is unreliable, and polling the API sucks (and is also unreliable, see Bug 24782).
So, I have written XMLRC http://www.mediawiki.org/wiki/Extension:XMLRC and set up a prototype on the Toolserver - have a look at http://meta.wikimedia.org/wiki/Recentchanges_via_XMPP for details. Basically, you point any Jabber client to the chat room enwiki@conference.jabber.toolserver.org to see the change events, like on IRC. However, if you use a client aware of the extra data attached to the messages, like http://www.mediawiki.org/wiki/Extension:XMLRC/rcclient.py, you will get all the information you can get from the API (in fact, you can get the exact same XML tag).
Try it out and let me know what you think!
-- daniel
nice one Daniel, this reminds me of a similar approach that we tried years ago with WikkaWiki called "WikiPing".
The idea was to aggregate recent changes information pushed from many wikis in real time via a standard protocol. The tool lived for a while on a server called recentchanges.net and received pings from several WikiPing-compliant wikis every time an edit was made. Unfortunately the idea didn't take off, the domain name expired and the project died within a few years.
http://docs.wikkawiki.org/WikiPing http://wikkawiki.org/WikiPingDevelopment
For the archeologists among us, that was in 2003 and WikiPing was one of the sources of inspiration for WikiTracer.
Dario
On 19 Aug 2010, at 20:09, Daniel Kinzler wrote:
(I sent this to a couple of lists already, but i though it might also be interresting for the research community)
Hi all! For a long time I wanted a decent push interface for RecentChanges-Events, so it becomes easy to follow changes on a wiki. Parsing messages on IRC is unreliable, and polling the API sucks (and is also unreliable, see Bug 24782).
So, I have written XMLRC http://www.mediawiki.org/wiki/Extension:XMLRC and set up a prototype on the Toolserver - have a look at http://meta.wikimedia.org/wiki/Recentchanges_via_XMPP for details. Basically, you point any Jabber client to the chat room enwiki@conference.jabber.toolserver.org to see the change events, like on IRC. However, if you use a client aware of the extra data attached to the messages, like http://www.mediawiki.org/wiki/Extension:XMLRC/rcclient.py, you will get all the information you can get from the API (in fact, you can get the exact same XML tag).
Try it out and let me know what you think!
-- daniel
Wiki-research-l mailing list Wiki-research-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wiki-research-l
Hello.
Nice work, Daniel.
The question may be weird, but it's something we have been thinking here for a while. Could we use recent changes to recreate the same info one gets from full XML dumps? Could it be the starting point for some alternative to the current dump process?
Thanks, F.
--- El jue, 19/8/10, Daniel Kinzler daniel@brightbyte.de escribió:
De: Daniel Kinzler daniel@brightbyte.de Asunto: [Wiki-research-l] Demo of RC-Events over XMPP Para: "Research into Wikimedia content and communities" wiki-research-l@lists.wikimedia.org Fecha: jueves, 19 de agosto, 2010 21:09 (I sent this to a couple of lists already, but i though it might also be interresting for the research community)
Hi all! For a long time I wanted a decent push interface for RecentChanges-Events, so it becomes easy to follow changes on a wiki. Parsing messages on IRC is unreliable, and polling the API sucks (and is also unreliable, see Bug 24782).
So, I have written XMLRC http://www.mediawiki.org/wiki/Extension:XMLRC and set up a prototype on the Toolserver - have a look at http://meta.wikimedia.org/wiki/Recentchanges_via_XMPP for details. Basically, you point any Jabber client to the chat room enwiki@conference.jabber.toolserver.org to see the change events, like on IRC. However, if you use a client aware of the extra data attached to the messages, like http://www.mediawiki.org/wiki/Extension:XMLRC/rcclient.py, you will get all the information you can get from the API (in fact, you can get the exact same XML tag).
Try it out and let me know what you think!
-- daniel
Wiki-research-l mailing list Wiki-research-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wiki-research-l
Felipe Ortega schrieb:
Hello.
Nice work, Daniel.
The question may be weird, but it's something we have been thinking here for a while. Could we use recent changes to recreate the same info one gets from full XML dumps? Could it be the starting point for some alternative to the current dump process?
In theory, one could process a dump covering revisions up to date X, and the process recentchanges starting from that date. However, this would require the RC-event to include the full revision text. This is currently not possible, due to technical limitations (in the case of XMLRC, the limitation is imposed by the limited size of UDP packets).
This can however be simulated, even if no so efficiently: for every RC-event, pull the corresponding revision text from the API. This would be a decent way to keep up to date, a way comparable to the deprecated OAI interface.
-- daniel
wiki-research-l@lists.wikimedia.org