Hi,
I´m using serendipity_plugin_twitter version 1.25.
I wondered, why last night many tweetbacks were fetched multiple. My database field "lasttweetid" has a maximum lenght of 15 characters but last night Twitters Tweetids became 16 characters long and "lasttweetid" has to be adjusted.
serendipity_plugin_twitter - lasttweetid lenght
-
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: serendipity_plugin_twitter - lasttweetid lenght
Hi!
Great find, thanks a lot. It's bad the plugin tried to "optimize" this to 15 characters, when it was already foreseeable that twitter IDs would be longer than that soon.
I raised the limit to 20 chars to be safe, and committed a change to the plugin so it should auto-update its table when being accessed, in version 1.26.
Regards,
Garvin
Great find, thanks a lot. It's bad the plugin tried to "optimize" this to 15 characters, when it was already foreseeable that twitter IDs would be longer than that soon.
I raised the limit to 20 chars to be safe, and committed a change to the plugin so it should auto-update its table when being accessed, in version 1.26.
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Re: serendipity_plugin_twitter - lasttweetid lenght
Thanks Garv,
I raised the limit, too.
I raised the limit, too.
Re: serendipity_plugin_twitter - lasttweetid lenght
I don´t know if "Snowflake" has consequences to twitter plugin:
http://groups.google.com/group/twitter- ... a375532182
Chapter "Timeline" in 1st post:
"Timeline
-----------
...
26th November 2010 (Friday) : Status IDs will break 53bits in length and
cease being usable as Integers in Javascript based languages
...
Our own products and tools are affected by the change and we will be making
available any pre-parsing snippets we have created to ensure code continues
to work with the new IDs. "
http://groups.google.com/group/twitter- ... a375532182
Chapter "Timeline" in 1st post:
"Timeline
-----------
...
26th November 2010 (Friday) : Status IDs will break 53bits in length and
cease being usable as Integers in Javascript based languages
...
Our own products and tools are affected by the change and we will be making
available any pre-parsing snippets we have created to ensure code continues
to work with the new IDs. "
-
- Regular
- Posts: 695
- Joined: Tue Jul 03, 2007 3:34 am
- Location: Berlin, Germany
- Contact:
Re: serendipity_plugin_twitter - lasttweetid lenght
EDIT: Oups.. Translated this post to Englisch..
This should be no problem as long as Garvin changed the database field to 20 chars, as 53bit numbers have 16 chars.
I'm more worried about the fact, that the numbers are converted to its exponential versions, while converting them to strings. While looking at the Tweeter this is already a problem: The status links there are already broken / not working for that reason. In don't know, if the last_tweet_id is saved into the database in the same version. If so, this already could be a problem, too.
This should be no problem as long as Garvin changed the database field to 20 chars, as 53bit numbers have 16 chars.
I'm more worried about the fact, that the numbers are converted to its exponential versions, while converting them to strings. While looking at the Tweeter this is already a problem: The status links there are already broken / not working for that reason. In don't know, if the last_tweet_id is saved into the database in the same version. If so, this already could be a problem, too.
Last edited by blog.brockha.us on Wed Nov 24, 2010 3:32 pm, edited 3 times in total.
Re: serendipity_plugin_twitter - lasttweetid lenght
Only the German forum is in German, remember?blog.brockha.us wrote:Das *sollte* erst mal keine Probleme machen
YL