Bug #590
Twitter timestamp always wrong
| Status: | Closed | Start: | 04/20/2011 | |
| Priority: | Normal | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 100% |
|
| Category: | Engine Twitter | |||
| Target version: | 0.8.10.1 | |||
| Complexity: | Found in Version: | 0.8.10 |
||
| Votes: | 0 |
Description
It is 1:44 am
a few minutes ago meebey tweeted but my timestamp reflects something like 3:00 am etc.
- Twitter profile reflects correct GMT +1
- Smuxi IRC reflects correct time
- Smuxi local engine reflects correct timestamp
date on server of remote engine as well as local laptop reflect both correct time and timezone
Associated revisions
Revision 19f0f1182e14edc80a386e72b7b5dd6134ecfd03
[Engine-Twitter] Port to Twitterizer 2.4
- Updated Twitterizer to 2.4 (closes: #643, #590)
- Ported TwitterProtocolManager to Twitterizer 2.4
- Track API changes
- Check all TwitterResponses properly using CheckResponse()
- Implemented IsTemporilyErrorResponse() to check if the error can be
ignored or not
- Use friends/ids and users/lookup to correctly fetch all friends including
enumeration in steps of 100 (closes: #465)
Revision ed9ac4c109c53205ddedb064a59f58488d5f6e6b
[Twitter-Engine] Convert local Twitter time values to UTC (closes: #590)
History
Updated by Mirco Bauer 4781 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 19f0f1182e14edc80a386e72b7b5dd6134ecfd03.
Updated by Mirco Bauer 4553 days ago
- Status changed from Closed to New
- Target version changed from 0.8.9 to 0.8.10.1
- Found in Version set to 0.8.10
Smuxi still shows incorrect time values (off by 2 hours), but only when used with a smuxi-server
Updated by Mirco Bauer 4553 days ago
- Status changed from New to Closed
Applied in changeset ed9ac4c109c53205ddedb064a59f58488d5f6e6b.