Has anyone done any work to make a mediawiki wiki usable off-line? Specifically, I'm thinking of tweaking it so that it can (a) fetch pages statically out of a dump file, (b) keep a log of page edits, and (c) submit those edits later, once on-line again. But of course I'd like to use / build on previous work, if any.
I've been thinking about doing an extension for that, but haven't decided on the best way for handling edit conflicts that occur when synchronising a queue of offline edits with the server. Do you have any ideas for how to deal with them?
Steve Summit wrote:
Has anyone done any work to make a mediawiki wiki usable off-line? Specifically, I'm thinking of tweaking it so that it can (a) fetch pages statically out of a dump file, (b) keep a log of page edits, and (c) submit those edits later, once on-line again. But of course I'd like to use / build on previous work, if any.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Aran wrote:
I've been thinking about doing an extension for that, but haven't decided on the best way for handling edit conflicts that occur when synchronising a queue of offline edits with the server. Do you have any ideas for how to deal with them?
I was thinking of doing a regular edit submission of each offline-edited page, with the edit token faked to refer to the revision id of the version as previosuly dumped and as offline-edited. That way, I figured, I could piggyback on the regular old edit conflict resolution mechanism. (I had an idea that the edit token was basically the revision id and that it could therefore be easily faked; though I'm not sure that was a valid assumption.)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Steve Summit:
I had an idea that the edit token was basically the revision id and that it could therefore be easily faked; though I'm not sure that was a valid assumption.)
the edit token is a secret value associated with the logged in user's session, *not* with the page being edited.
once a user logs in, the token is the same for all pages (and all revisions) that user edits. if they log out and in again, the token will change.
so, this probably won't do what you want. if the token has changed, you won't be able to submit your edit; and even if you do, the token won't prevent you overwriting a later revision.
you would probably do better to use the wpEdittime value, which is the timestamp of the revision being edited. if you submit an edit with the wrong edit time, you will get an edit conflict.
- river.
River Tarnell schreef:
you would probably do better to use the wpEdittime value, which is the timestamp of the revision being edited. if you submit an edit with the wrong edit time, you will get an edit conflict.
It would be better to use wpEdittime, but you should still fake it. Submitting an edit with an outdated wpEdittime *usually* results in an edit conflict, but MediaWiki will attempt to merge your edit into the conflicting revision(s) first. You'll only get an edit conflict when the merge fails.
Roan Kattouw (Catrope)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2008/10/27 Roan Kattouw roan.kattouw@home.nl:
River Tarnell schreef:
you would probably do better to use the wpEdittime value, which is the timestamp of the revision being edited. if you submit an edit with the wrong edit time, you will get an edit conflict.
It would be better to use wpEdittime, but you should still fake it. Submitting an edit with an outdated wpEdittime *usually* results in an edit conflict, but MediaWiki will attempt to merge your edit into the conflicting revision(s) first. You'll only get an edit conflict when the merge fails.
So where is the problem? I think it 'd be better to manually merge only if necessary.
Marco
Marco Schuster schreef:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2008/10/27 Roan Kattouw roan.kattouw@home.nl:
River Tarnell schreef:
you would probably do better to use the wpEdittime value, which is the timestamp of the revision being edited. if you submit an edit with the wrong edit time, you will get an edit conflict.
It would be better to use wpEdittime, but you should still fake it. Submitting an edit with an outdated wpEdittime *usually* results in an edit conflict, but MediaWiki will attempt to merge your edit into the conflicting revision(s) first. You'll only get an edit conflict when the merge fails.
So where is the problem? I think it 'd be better to manually merge only if necessary.
No problem, just pointing out that wpEdittime's semantics are slightly different from what River said.
Roan Kattouw (Catrope)
Steve Summit wrote:
Has anyone done any work to make a mediawiki wiki usable off-line? Specifically, I'm thinking of tweaking it so that it can (a) fetch pages statically out of a dump file, (b) keep a log of page edits, and (c) submit those edits later, once on-line again. But of course I'd like to use / build on previous work, if any.
I'm working on (a) (dump-based off-line mediawiki). b & c would be nice additions, but I do not have any time slot assigned for them in the near future.
2008/10/27 Keisial keisial@gmail.com:
Steve Summit wrote:
Has anyone done any work to make a mediawiki wiki usable off-line? Specifically, I'm thinking of tweaking it so that it can (a) fetch pages statically out of a dump file, (b) keep a log of page edits, and (c) submit those edits later, once on-line again. But of course I'd like to use / build on previous work, if any.
I'm working on (a) (dump-based off-line mediawiki). b & c would be nice additions, but I do not have any time slot assigned for them in the near future.
I'm working on an offline Wiktionary reader extension for Firefox which works with dump files. It also emulates certain API functions.
I would like to see if anybody would like to help work on it.
Andrew Dunbar (hippietrail)
Hoi, FYI OmegaWiki is being developed into a mark II version. In this version it will be possible to have your own version on your own system. It will allow for the synchronisation with other servers.. so in essence it will have aspects of peer-to-peer data.
We are currently working on importing the Wikiword data (the master thesis of Daniel Kintzler). This will get us a lot of terminology out of Wikipedia.. Using Wiktionary data would be great as well. the issue will be how to disambiguate. Thanks, GerardM
On Fri, Oct 31, 2008 at 1:19 AM, Andrew Dunbar hippytrail@gmail.com wrote:
2008/10/27 Keisial keisial@gmail.com:
Steve Summit wrote:
Has anyone done any work to make a mediawiki wiki usable off-line? Specifically, I'm thinking of tweaking it so that it can (a) fetch pages statically out of a dump file, (b) keep a log of page edits, and (c) submit those edits later, once on-line again. But of course I'd like to use / build on previous work, if any.
I'm working on (a) (dump-based off-line mediawiki). b & c would be nice additions, but I do not have any time slot assigned for them in the near future.
I'm working on an offline Wiktionary reader extension for Firefox which works with dump files. It also emulates certain API functions.
I would like to see if anybody would like to help work on it.
Andrew Dunbar (hippietrail)
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Another idea:
Subscription channels. You subscribe to a set of articles ( category, or "this article and all articles that link it"). if you are on-line, a robot slowly mirror these categories as static files on the hard disk. (update if changes are made, download if there are new). Make so this extension open a sidebar, where you can browse your offline categories, and open one of these, make so If you click on a link that is not mirrored, a popup ask "This article is not saved offline, do you want to add to this category?".
wikitech-l@lists.wikimedia.org