dabr - Project Hosting on Google Code

Today 13 hours ago r253 (Quick fix for "in reply to" no longer showing. As discovered...) committed by david.carrington - Quick fix for "in reply to" no longer showing. As discovered by @squawkbox. Quick fix for "in reply to" no longer showing. As discovered by @squawkbox. 15 hours ago dabr-r252.zip (Code snapshot revision 252 ) file uploaded by david.carrington - Labels: Featured Labels: Featured 15 hours ago issue 66 (Support for the new RT API) Status changed by david.carrington - Fixed in r252 Status: Fixed Fixed in r252 Status: Fixed 15 hours ago r252 (Basic Twitter Retweet support, mostly a merge of @yegle's r2...) committed by david.carrington - Basic Twitter Retweet support, mostly a merge of @yegle's r251 change. Basic Twitter Retweet support, mostly a merge of @yegle's r251 change. Last 7 days Dec 08, 2009 issue 89 (Recent changes to statuses/{friends,followers} api) Status changed by david.carrington - I suspected that. Unhelpfully, that also means we'll need to switch to XML for this request again as PHP has bad handling of the 64 bit integers that return as the cursor IDs. Status: Accepted I suspected that. Unhelpfully, that also means we'll need to switch to XML for this request again as PHP has bad handling of the 64 bit integers that return as the cursor IDs. Status: Accepted Dec 07, 2009 issue 89 (Recent changes to statuses/{friends,followers} api) reported by cnyegle - Recently twitter made some modification to statuses/{friends,followers}，they canceled the page parameter. Dabr should use curse parameter instead of page to make friends/followers list pagination work correct. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0friends Recently twitter made some modification to statuses/{friends,followers}，they canceled the page parameter. Dabr should use curse parameter instead of page to make friends/followers list pagination work correct. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0friends Dec 05, 2009 r251 (Add support for the official retweet, still testing. ) committed by cnyegle - Add support for the official retweet, still testing. Add support for the official retweet, still testing. Dec 05, 2009 r250 (Merge trunk changes from r242 to r249. ) committed by cnyegle - Merge trunk changes from r242 to r249. Merge trunk changes from r242 to r249. Dec 05, 2009 issue 87 (Full implementation of lists) commented on by felixonmars - This is my small fix of lists.php, which makes it compatible with cnyegle's branch. (Custom API Key Support). - or there will be an error while list operating. This is my small fix of lists.php, which makes it compatible with cnyegle's branch. (Custom API Key Support). - or there will be an error while list operating. Dec 05, 2009 issue 71 (Expend short URLs on server side) commented on by ldoug...@gmail.com - made modification to batch api calls to expand short URLs. Also made the display show only the domain part of the link rather than the entire link (like on slashdot) curious for feedback on the way I did it made modification to batch api calls to expand short URLs. Also made the display show only the domain part of the link rather than the entire link (like on slashdot) curious for feedback on the way I did it Dec 05, 2009 issue 66 (Support for the new RT API) commented on by david.carrington - Issue 82 has been merged into this issue. Issue 82 has been merged into this issue. Dec 05, 2009 issue 82 (Add support for official retweet) changed by david.carrington - Status: Duplicate Status: Duplicate Dec 05, 2009 issue 82 (Add support for official retweet) commented on by cnyegle - This is a duplicate issue of issue 66 This is a duplicate issue of issue 66 Dec 04, 2009 issue 86 (The "expect 100-continue" error) commented on by cnyegle - @zhankezk in function twitter_process,before curl_exec @zhankezk in function twitter_process,before curl_exec Dec 04, 2009 issue 86 (The "expect 100-continue" error) commented on by zhankezk - Can you teach where should I add this code? In which file of dabr? Thanks ! Can you teach where should I add this code? In which file of dabr? Thanks ! Dec 04, 2009 issue 86 (The "expect 100-continue" error) commented on by cnyegle - @ldouglas I've tested this solution on my dabr mirror for a long time and it works fine :-) @ldouglas I've tested this solution on my dabr mirror for a long time and it works fine :-) Dec 03, 2009 issue 88 (Add a page to edit user the profile) reported by ldoug...@gmail.com - What would you like dabr to do? Allow user to edit user profile How would you prefer dabr to do it? add a separate page for user to edit name, bio, url and location using patch for Issue 83 allow legacy Geocoding support in location field using captured lat/long. Not sure about support for this field going forward. What would you like dabr to do? Allow user to edit user profile How would you prefer dabr to do it? add a separate page for user to edit name, bio, url and location using patch for Issue 83 allow legacy Geocoding support in location field using captured lat/long. Not sure about support for this field going forward. Dec 03, 2009 issue 82 (Add support for official retweet) commented on by ldoug...@gmail.com - added a page to see retweets by you, to you and of you only thing missing on the "of you" page is information of who retweeted you - as is supplied on the corresponding twitter.com retweets webpage. Not sure about cost/benefit there based on the data available. added a page to see retweets by you, to you and of you only thing missing on the "of you" page is information of who retweeted you - as is supplied on the corresponding twitter.com retweets webpage. Not sure about cost/benefit there based on the data available. Dec 03, 2009 issue 83 (Geolocation) commented on by ldoug...@gmail.com - added a page to see retweets by you, to you and of you only thing missing on the "of you" page is information of who retweeted you - as is supplied on the corresponding twitter.com retweets webpage. Not sure about cost/benefit there based on the data available. added a page to see retweets by you, to you and of you only thing missing on the "of you" page is information of who retweeted you - as is supplied on the corresponding twitter.com retweets webpage. Not sure about cost/benefit there based on the data available. Dec 03, 2009 issue 86 (The "expect 100-continue" error) commented on by ldoug...@gmail.com - will this affect any process where this error is not occurring? will this affect any process where this error is not occurring? Last 30 days Dec 03, 2009 r249 (Support for Google Analytics' new mobile tracking code.) committed by david.carrington - Support for Google Analytics' new mobile tracking code. Support for Google Analytics' new mobile tracking code. Dec 02, 2009 issue 80 (Supporto Google Language API) commented on by ldoug...@gmail.com - here is my implementation in the status page here is my implementation in the status page Dec 02, 2009 r248 (Maemo devices should get the Touch mode by default. (Thanks ...) committed by david.carrington - Maemo devices should get the Touch mode by default. (Thanks @whatleydude and @tnkgrl) Maemo devices should get the Touch mode by default. (Thanks @whatleydude and @tnkgrl) Dec 01, 2009 issue 87 (Full implementation of lists) commented on by ldoug...@gmail.com - made some adjustments - fixed bug you found with the follow, made the actions more smart and dynamic, and moved all that code into the theme function. makes it a little cleaner. made some adjustments - fixed bug you found with the follow, made the actions more smart and dynamic, and moved all that code into the theme function. makes it a little cleaner. Dec 01, 2009 issue 77 (Lists API integration) Status changed by david.carrington - Basic support works. See Issue 87 for further work. Status: Fixed Basic support works. See Issue 87 for further work. Status: Fixed Dec 01, 2009 issue 87 (Full implementation of lists) changed by david.carrington - That's one of the biggest user-contributed patches I've seen, and while I don't have time to look at it right now I'd really like to show my appreciation. You'll make a lot of Dabr users happy if this all works nicely :) Status: Accepted Owner: david.carrington Labels: Priority-High −Priority-Low That's one of the biggest user-contributed patches I've seen, and while I don't have time to look at it right now I'd really like to show my appreciation. You'll make a lot of Dabr users happy if this all works nicely :) Status: Accepted Owner: david.carrington Labels: Priority-High −Priority-Low Dec 01, 2009 issue 42 (Support posting pictures to flickr ) commented on by david.carrington - To support an issue on Google Code projects you must click the star. As far as I know, only one person thinks Flickr uploads are worthwhile. Please do not comment on issues unless you have a constructive comment beyond "I need this!". Two of the best ways to send photos to Flickr are a) by e-mail, and b) by using a photo upload app such as Shozu. There's little benefit in using a web-based file upload, especially since most phones can't preview image uploads and some big names can't do web-based uploads at all - iPhone and Android. To support an issue on Google Code projects you must click the star. As far as I know, only one person thinks Flickr uploads are worthwhile. Please do not comment on issues unless you have a constructive comment beyond "I need this!". Two of the best ways to send photos to Flickr are a) by e-mail, and b) by using a photo upload app such as Shozu. There's little benefit in using a web-based file upload, especially since most phones can't preview image uploads and some big names can't do web-based uploads at all - iPhone and Android. Dec 01, 2009 r247 (Dabr goes #red for World Aids Day) committed by david.carrington - Dabr goes #red for World Aids Day Dabr goes #red for World Aids Day Nov 30, 2009 issue 87 (Full implementation of lists) commented on by ldoug...@gmail.com - i suppose this could go with issue 77 i suppose this could go with issue 77 Nov 30, 2009 issue 42 (Support posting pictures to flickr ) commented on by ldoug...@gmail.com - as a work-around, you can sign up for Posterous, link it to both your Twitter and Flickr accounts, then implement the uploadAndPost API method which works the same way as Twitpic uploads. It will post to your Posterous blog and autopost a link to your twitter as well as upload it to your Flickr account. Not direct, but still a workaround. on the Twitpic page, you can put the service you want in a dropdown (with Twitpic and Posterous) and set the upload URL to http://'.$_POST['service'].'.com/api/uploadAndPost see http://tr.im/GfXG as a work-around, you can sign up for Posterous, link it to both your Twitter and Flickr accounts, then implement the uploadAndPost API method which works the same way as Twitpic uploads. It will post to your Posterous blog and autopost a link to your twitter as well as upload it to your Flickr account. Not direct, but still a workaround. on the Twitpic page, you can put the service you want in a dropdown (with Twitpic and Posterous) and set the upload URL to http://'.$_POST['service'].'.com/api/uploadAndPost see http://tr.im/GfXG Nov 30, 2009 issue 87 (Full implementation of lists) reported by ldoug...@gmail.com - What would you like dabr to do? be able to add and remove people from lists, to create, update and delete lists, to subscribe to/follow lists How would you prefer dabr to do it? implemented on my local copy - attached What would you like dabr to do? be able to add and remove people from lists, to create, update and delete lists, to subscribe to/follow lists How would you prefer dabr to do it? implemented on my local copy - attached Nov 30, 2009 issue 83 (Geolocation) commented on by fabio.parri - Very cool patch! Looking forward to it being applied to dabr. What about people not having javascript capable phones? Would that be possible to reverse the geocoding from a place name? I know that wouldn't be perfect, but it's always better than nothing ;) Very cool patch! Looking forward to it being applied to dabr. What about people not having javascript capable phones? Would that be possible to reverse the geocoding from a place name? I know that wouldn't be perfect, but it's always better than nothing ;) Nov 28, 2009 FAQ (Frequently asked questions) Wiki page commented on by tm.adjie - how about TwitterLists feature? it isn't included yet in downloadable Dabr sourcecode. how about TwitterLists feature? it isn't included yet in downloadable Dabr sourcecode. Nov 28, 2009 ListsAPI (A page to show the Twitter List API (until they document it ...) Wiki page commented on by tm.adjie - have you integrate this TwitterLists feature into downloadable Dabr sourcecode? have you integrate this TwitterLists feature into downloadable Dabr sourcecode? Nov 27, 2009 issue 83 (Geolocation) commented on by cnyegle - Here is an updated patch. geolocation is stored in cookie and refresh every minutes. Just apply this patch and put geolocation.png in images/, the geo-location-js is included. Here is an updated patch. geolocation is stored in cookie and refresh every minutes. Just apply this patch and put geolocation.png in images/, the geo-location-js is included. Nov 27, 2009 issue 83 (Geolocation) commented on by cnyegle - @fabio.parri Hi fabio.parri, I've implemented a demo of geolocation feature on my dabr mirror.If you have a mobile phone with GPS, you can try it now :-) https://yegle.net/dongtaiwang.com/ patch attached. You need to download geo-location-javascript's zip file and put geo.js at BASE_URL @fabio.parri Hi fabio.parri, I've implemented a demo of geolocation feature on my dabr mirror.If you have a mobile phone with GPS, you can try it now :-) https://yegle.net/dongtaiwang.com/ patch attached. You need to download geo-location-javascript's zip file and put geo.js at BASE_URL Nov 26, 2009 issue 86 (The "expect 100-continue" error) reported by cnyegle - What are the steps to trigger the problem? 1)Try to post a long tweet What happened? The "expect 100-continue" error occurred. What did you expect to happen? This can be fixed by one line in function twitter_process curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); For more info, google "expect 100-continue twitter" What are the steps to trigger the problem? 1)Try to post a long tweet What happened? The "expect 100-continue" error occurred. What did you expect to happen? This can be fixed by one line in function twitter_process curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); For more info, google "expect 100-continue twitter" Nov 25, 2009 r246 (Quick fix for moby.to previews.) committed by david.carrington - Quick fix for moby.to previews. Quick fix for moby.to previews. Nov 24, 2009 issue 83 (Geolocation) commented on by fabio.parri - Ah ok, now I see what you mean. Adding JS supporto seems a nice option, but I'm afraid it wouldn't work with old mobile clients who don't support it. What about a slimmed-down implementation. I think something like: User setting his/her location, which gets transformed, server-side, to GPS coordinates through a geocoding service like Google's, so you can post geolocated tweets. Also, user can access to all other Twitter geo services, using those coordinates. I know it's not the best solution, but it seems to me it could be the most compatible one ;) Ah ok, now I see what you mean. Adding JS supporto seems a nice option, but I'm afraid it wouldn't work with old mobile clients who don't support it. What about a slimmed-down implementation. I think something like: User setting his/her location, which gets transformed, server-side, to GPS coordinates through a geocoding service like Google's, so you can post geolocated tweets. Also, user can access to all other Twitter geo services, using those coordinates. I know it's not the best solution, but it seems to me it could be the most compatible one ;) Nov 24, 2009 issue 85 (Image resizing on the fly via PHP) reported by fabio.parri - On some very old browsers like, 3's www3, images are shown in their real size, not in the one set with the width and height attributes. It would be very useful if larger images would be resized dynamically via PHP. Old browsers like www3 are still used, for example in Italy, because 3 gives users 50 Mb of FREE web traffic on it, every day ;) On some very old browsers like, 3's www3, images are shown in their real size, not in the one set with the width and height attributes. It would be very useful if larger images would be resized dynamically via PHP. Old browsers like www3 are still used, for example in Italy, because 3 gives users 50 Mb of FREE web traffic on it, every day ;) Nov 23, 2009 issue 84 (Better support for HTTPS/SSL) reported by cnyegle - What would you like dabr to do? Have a better support for HTTPS/SSL. How would you prefer dabr to do it? When I access to https://dabr.co.uk and login, I should stay with HTTPS. But instead I was redirected to an HTTP page. On my dabr mirror, I have to set BASE_URL to https://yegle.net/dabr/ to force an HTTPS environment. Also,when I'm in HTTPS environment, the avatars should use https://s3.amazonaws.com/twitter_production/ instead of http://a[0-9].twimg.com/ What would you like dabr to do? Have a better support for HTTPS/SSL. How would you prefer dabr to do it? When I access to https://dabr.co.uk and login, I should stay with HTTPS. But instead I was redirected to an HTTP page. On my dabr mirror, I have to set BASE_URL to https://yegle.net/dabr/ to force an HTTPS environment. Also,when I'm in HTTPS environment, the avatars should use https://s3.amazonaws.com/twitter_production/ instead of http://a[0-9].twimg.com/ Nov 22, 2009 issue 83 (Geolocation) commented on by cnyegle - @fabio.parri Hi there, I know twitter's geolocation API, I'm talking about how to implement it in dabr :-) Now the biggest problem for me seems there is no suitable icons to indicate tweets with geolocation. :-( @fabio.parri Hi there, I know twitter's geolocation API, I'm talking about how to implement it in dabr :-) Now the biggest problem for me seems there is no suitable icons to indicate tweets with geolocation. :-( Nov 21, 2009 issue 83 (Geolocation) commented on by fabio.parri - Uhm, that looks to me as another thing. I was referring to support for Twitter Geolocation APIs: http://apiwiki.twitter.com/FindPage?SearchFor=geo Uhm, that looks to me as another thing. I was referring to support for Twitter Geolocation APIs: http://apiwiki.twitter.com/FindPage?SearchFor=geo Nov 21, 2009 issue 83 (Geolocation) commented on by cnyegle - This can be implemented using geo-location-javascript project homepage: http://code.google.com/p/geo-location-javascript/ This can be implemented using geo-location-javascript project homepage: http://code.google.com/p/geo-location-javascript/ Nov 20, 2009 issue 83 (Geolocation) reported by fabio.parri - Add support to GeoLocation APIs Add support to GeoLocation APIs Nov 19, 2009 issue 82 (Add support for official retweet) commented on by cnyegle - patch update,bug fix patch update,bug fix Nov 19, 2009 issue 82 (Add support for official retweet) commented on by cnyegle - patch update,bug fix patch update,bug fix Nov 18, 2009 issue 82 (Add support for official retweet) commented on by cnyegle - small fix do not use intval() to handle the tweet id. small fix do not use intval() to handle the tweet id. Nov 18, 2009 issue 82 (Add support for official retweet) commented on by cnyegle - small fix, do not display official retweet button when tweet's owner is protected. small fix, do not display official retweet button when tweet's owner is protected. Nov 18, 2009 issue 82 (Add support for official retweet) reported by cnyegle - What would you like dabr to do? Add support for official retweet How would you prefer dabr to do it? Below is my patch to support the official retweet. What would you like dabr to do? Add support for official retweet How would you prefer dabr to do it? Below is my patch to support the official retweet.

issue 83 (Geolocation) commented on by fabio.parri - Ah ok, now I see what you mean. Adding JS supporto seems a nice option, but I'm afraid it wouldn't work with old mobile clients who don't support it. What about a slimmed-down implementation. I think something like: User setting his/her location, which gets transformed, server-side, to GPS coordinates through a geocoding service like Google's, so you can post geolocated tweets. Also, user can access to all other Twitter geo services, using those coordinates. I know it's not the best solution, but it seems to me it could be the most compatible one ;)

Ah ok, now I see what you mean. Adding JS supporto seems a nice option, but I'm afraid it wouldn't work with old mobile clients who don't support it. What about a slimmed-down implementation. I think something like: User setting his/her location, which gets transformed, server-side, to GPS coordinates through a geocoding service like Google's, so you can post geolocated tweets. Also, user can access to all other Twitter geo services, using those coordinates. I know it's not the best solution, but it seems to me it could be the most compatible one ;)

Today

Last 7 days

Last 30 days