It works for both XWiki and Confluence.

-Vincent
XWiki Developer

I Also am feeling that the more I work on different wikis the more I want to keep track of what I did and updated. For it was my perspective at that point in time. I saw a little of this in the WikiDashboard program shared at KMWorld, however, how do I bring my contributions back to my lifestream? If I don’t have a wiki participation program… little like delicious how do I keep track? Author updates / RSS, all popular wikis?

Here’s an example. You are in company x. They have a wiki and use WikiDashboard. All your work is on customers sites; so you have no presence on your company’s site. How do you share your work.. how does the company see your contributions? How do you aggregate it in with what you are doing?

http://decafbad.com/twiki/bin/view/Main/XmlRpcToWiki

I’d say wikis have gotten richer since then, and we have different ways to build APIs and provide data. That’s good, though it means I don’t think we’ll ever have a single API or editor that covers all or even most wikis - other than the browser, of course.

The SocialText stuff looks might keen, though.

I’m wanting something to make my life easy going between different wiki’s. I’m wanting that editor to link me with other users on each wiki. I’m also wanting it to keep track of my updates. Diigo integration may work. So I need an RSS output of my updates. Eg link to page when I was last there / changes / in a different color etc.

I’ll certainly commend efforts to make this happen. If not if it works for Wikipedia / MediaWiki then maybe it’s enough to go everywhere. It’s not always the best tool that wins; it is the default everyone can use.

I think we keep hoping that wikis will get easier. I think this is a mistake. What we have seen is walled gardens built with better and better editors. That’s faulty. When wiki is everywhere they will not all be the same. The barrier to participation must be lowered.

So much to respond to in your post. Yes, I agree, wiki world needs to catch up and get with a better editing program.

Long ago when I was still working on PurpleWiki Eugene and I hooked up some XML-RPC editing. It was pretty slick, but in the PurpleWiki context proved not all that useful: PurpleWiki is a very linking oriented rather than content generation oriented wiki. Being outside the context of the other pages was not particularly exciting.

Other wiki, like say Socialtext, are a bit more content oriented and various editing systems would be cool. Ross already pointed out Socialtext Unplugged: the offline editor for Socialtext. It is based on new functionality in TiddlyWiki which makes it possible to do offline editing for lots of different types of wikis. You can have content from various places all at once in the same HTML file on your own storage.

You can’t, however, edit the content in other tools, such as whatever your favorite editor may be. Lately I’ve not found this to much of a limitation. In the morning I gather up whatever content I care about into an unplugged artifact, get on my bike and go wherever, do some editing in a simple text area (with spell checking) and head out. There are extensions to Firefox that will allow a textarea to open in whatever editor you want to use, which is cool.

Unplugged takes advantage of Socialtext’s REST API to move content back and forth. It’s written in such a way that it is very simple to make adapters for a bunch of editors. One hack we did was to connect TextMate to a wiki via Ruby using the REST API.

Luke Closs created an awesome geeky tool called wikrad which is a terminal based wiki browser and editor. If you are a vim or emacs user it is awesome.

At the moment all these things just work for Socialtext, but we’ve had such a good time with the REST API that we are convinced it would make a good interface for most wikis. We hope to start a project called Amo to get some traction with that. If it did, then tools that use Amo would work with all that wikis that support it.

Another path is using Atom. There are a growing number of Atom editors and various wikis are experimenting with support for the Atom Publishing Protocol. I’ve done some work in the Socialtext code for such things. I have it basically working, all I really need is some time. Atom is far better than XML-RPC for this sort of thing.