Last modified: 2012-12-30 20:53:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T41061, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 39061 - Meta changes notification will be useful
Meta changes notification will be useful
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-05 21:22 UTC by Григор Гачев
Modified: 2012-12-30 20:53 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Григор Гачев 2012-08-05 21:22:36 UTC
The meta info is treasure for a well-written bot. The problem is, fetching it on every login is bandwidth waste, and relying on an obsolete cached copy might produce bad results.

Is it possible to create a way to check if (and what) meta info has changed?

The best idea I came with is a request that will supply the "last fetched here" timestamp and will get a description of what meta should be re-requested. For example, the description may list the meta types and their parameters that should be requested. Then, the bot may request them if / when needed for its task.

(I came to this idea while trying to write a new version of Apibot.)

Grigor Gatchev
Comment 1 db [inactive,noenotif] 2012-08-06 17:51:36 UTC
Did you mean meta=siteinfo?
Comment 2 Григор Гачев 2012-08-08 08:04:12 UTC
Also meta=allmessages, meta=userinfo (where affected by the site change), meta=globaluserinfo (where affected) and possibly other meta (eg. when a new meta param is introduced.

Paraminfo changes will be very useful, too - forgot about them in the first post.  In short, any info a bot will better depend on, and is reasonable to cache it.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links