Last modified: 2014-06-05 08:57:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 17305 - RCFeed: Expose original server timestamp of event in IRC RC Feed
RCFeed: Expose original server timestamp of event in IRC RC Feed
Product: MediaWiki
Classification: Unclassified
Recent changes (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Krinkle
Depends on:
Blocks: 16599
  Show dependency treegraph
Reported: 2009-02-01 18:02 UTC by Gurch
Modified: 2014-06-05 08:57 UTC (History)
2 users (show)

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


Description Gurch 2009-02-01 18:02:01 UTC
Users' system clocks are generally not synchronized with those of Wikimedia's servers, and there is frequently a delay; in particular, there can be periods of lag and then many revisions all being recieved at once.

Assigning revisions the system time as of when they arrived is fine for knowing what edits were made in what order, but weirdness occurs when trying to use these edits' supposed timestamps in conjunction with actual timestamps fetched through the API (revisions in the wrong order, edit conflicts that aren't, and so forth). The only way around this is to ask the API what the revision's real timestamp is when doing anything with it, kind of negating the advantage of using the IRC feed in the first place.
Comment 1 Mike.lifeguard 2009-03-23 01:42:25 UTC
Component -> RecentChanges
Comment 2 Krinkle 2014-06-05 08:57:39 UTC
The IRC RC Feed is no longer in development (considered frozen for backwards compatibility).

It's replacement[1] based on JSONRCFeedFormatter and MachineReadableRCFeedFormatter has a timestamp property[2] already.


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