I might look at swapping over to the reverse geocoder provided by
geoapi.com as an alternative to the google maps api which has a
tendency to give some weird results.
On Dec 24, 9:04 am, Marcel Molina wrote:
> For the last few months, the Platform team has been really excited about all
> the poss
I've recently switch to using this regex for pulling out links,
haven't spotted any issues with any extra characters surrounding the
links as yet.
/(?i)\b((?:[a-z][\w-]+:(?:\/{1,3}|[a-z0-9%])|www\d?[.])(?:[^\s()<>]+|\
([^\s()<>]+\))+(?:\([^\s()<>]+\)|[^`!()\[\]{};:\'".,<>?«»“”‘’\s]))/
It was post
Retweets of Me (http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-
statuses-retweets_of_me)
* add details about who retweeted your tweets, only needs to be first
retweeter and a count of total number of times retweeted.
Lists:
* add list details node (eg. same as GET list_id method) to other
l
I'm seeing the same thing (for
http://api.twitter.com/1/statuses/retweeted_to_me.xml),
no retweets showing after November 11th for my 'deanjrobinson'
account, and none at all showing for my 'hahlo' account.
On Nov 19, 8:22 pm, Rich wrote:
> Am I the only one seeing that the ReTweeted To Me API
This could possibly be related,
I recently switched from using https://twitter.com to https://api.twitter.com
and found that the majority of my cURL calls (via php) to the api
started failing, although no other parts of my function changed.
Out of curiosity I changed it to http://api.twitter.com
+1
I've just started adding Lists to Hahlo.com and found this same thing.
Based on the description in the docs I was expecting:
/user/lists.format to be just the lists the user created
/user/lists/subscriptions.format to be the lists the user created +
those they are following (as it is on twit
Looking at the examples I think this works much nicer, and should be
'friendlier' to implement. Looking forward to playing with it further.
On Oct 1, 9:08 am, Marcel Molina wrote:
> We've updated the retweet payload to look a lot more like a regular
> tweet's payload. We find this change makes t
Nice stuff!
Glad I didn't spend a heap of time developing my own list/group
solution for Hahlo, instead I can just drop in the API. sweet.
On Oct 1, 9:13 am, Marcel Molina wrote:
> Over on the main Twitter blog @nk has written about a new Lists
> feature we're getting ready to
> launch:http:
Just checking out my @ mentions and noticed there are a whole bunch
missing, took a little while to register what was going on, but it
looks like only tweet that begin with @username are being returned -
this is happening both on twitter.com and via the API.
Anyone else notice this, and is it a b
99.9% of login attempts simply don't work at all in Firefox 3.5, they
just redirects to blank https://twitter.com/sessions page
If by some fluke it does actually login I can't logout to change
accounts.
Logins work in Safari, but posting statuses only does occasionally,
I've tried to update a pro
What about those using the regular API, via both Basic Auth and OAuth,
is there anything at all we can do to stop getting endless 408's ?
I'm guessing that since even twitter.com itself is still very
"inconsistent", for lack of a better word, theres probably nothing
much more we can do than just
nford
> Twitter Dev
>
> On Jul 9, 2009, at 4:38 PM, dean.j.robinson wrote:
>
>
>
> > Thanks for the super speedy response Matt.
>
> > On Jul 10, 9:26 am, Matt Sanford wrote:
> >> Hi all,
>
> >> Some changes were just deployed and it l
> Thanks;
> – Matt Sanford / @mzsanford
> Twitter Dev
>
> On Jul 9, 2009, at 4:25 PM, dean.j.robinson wrote:
>
>
>
> > Everyone just magically got logged out of my hahlo4 beta, which was
> > working fine an hour ago, and now when they reauthorize its not
>
Everyone just magically got logged out of my hahlo4 beta, which was
working fine an hour ago, and now when they reauthorize its not
sticking.
OAuth login works fine, redirect back to hahlo4, but all api calls are
returning 401 status codes.
Saw mention in another topic regarding whether twitter
awesome... I probably should have looked closer, I only did a quick
search of the group and check the api changelog... didn't think to run
a request and check
On Jun 15, 2:53 pm, Abraham Williams <4bra...@gmail.com> wrote:
> On Sun, Jun 14, 2009 at 23:17, dean.j.robinson
> wro
Any plans to add an attribute to the API responses to indicate if a
user is a "verified" user? Would be nice if this info was available so
that it could be displayed against the appropriate tweeters as needed.
Also swapped my own groups implementation in Hahlo4 for the
saved_searches api last nig
I'll admit I'm a little disappointed that the info won't be part of
the user objects anymore (will have to rethink some of my planned
features... ie. won't be able to dynamically show/hide the dm button
next to tweets if it means I need an additional api call for each
user) instead relying on anot
Nice work guys, talk about the firehose has been floating around for
ages, great to see it finally appear and with numerous variants
available (thats a bonus). I personally don't have any use for it
(yet) but I'm sure it'll please quite a few.
On May 10, 2:04 pm, John Kalucki wrote:
> Note: Th
actually only one of the two was deleted, sorry my bad, its just not
showing up in my google groups recent activity.
On Apr 25, 1:56 pm, "dean.j.robinson"
wrote:
> So, if I've got two users "user_a" and "user_b" the method currently
> works like
So, if I've got two users "user_a" and "user_b" the method currently
works like this (from api wiki):
"Tests for the existence of friendship between two users. Will return
true if user_a follows user_b, otherwise will return false."
Now, if I also wanted to know if "user_b" follows "user_a" I c
I posted this yesterday, but the post appeared to vanish into the
ether, during the OAuth 'outage' my dev version of Hahlo 4 (which uses
OAuth) continued to work fine, is this because I was already logged in
and the token was still valid? I'm guessing if I'd logged out/
unauthorized then I wouldn'
I've had a quick look, looks good so far, nicely organised, plenty of
info etc. Will go through it more closely during my lunch break and
let you know if I spot anything.
top work.
On Apr 15, 3:35 am, Doug Williams wrote:
> Ahmed and Chad,
> I'm rolling in all of those suggestions right now. Th
Especially with regards to the deprecation of certain things. I
totally missed the topic about the deprecation of the since param
which was only posted on the 8th. Reading it now it said:
"Please use the next few days to update your application to use the
since_id
parameter if it is currently usi
I noticed this because I've got some code that checks the utc_offset
and noticed that it was missing.
For my hahlo account verify_credentials is returning this (appears to
be missing colours, utc_offset, fav counts etc etc):
7097682
Hahlo.com
hahlo
Newcastle, Australia
The best iPhon
gt; 1.https://apiwiki.twitter.com/FAQ#HowcanIgetmyappinthesidebarpromotionbox
>
> Thanks,
> Doug Williams
> Twitter API Supporthttp://twitter.com/dougw
>
> On Tue, Mar 31, 2009 at 9:03 PM, dean.j.robinson
> wrote:
>
>
>
> > Hi all,
>
> > Saw a tweet earlier from @bs about '
Hi all,
Saw a tweet earlier from @bs about 'saved searches' being a new
feature on twitter that is now available for some users. This is one
of the features I had been planning on adding to Hahlo4, so I'd like
to know if its something that we might be able to do via the api in
the future (perhaps
Thumbs up :)
I was thinking about the same thing, just hadn't gotten around to
ticketing, given the number of iphone//mobile related apps, it would
be appreciated by many I think.
On Mar 30, 5:50 am, Chad Etzel wrote:
> Hi Guys,
>
> I have opened a code issue
> here:http://code.google.com/p/tw
I was just about to ask the exact same question. I noticed this soon
after implementing oauth in Hahlo4 but figured it was just a bug in my
code. I'd auth on my laptop and it would work fine, then I'd auth on
my phone and the laptop would stop working, auth back on the laptop
and the phone would s
att Sanford
>
> On Mar 4, 2009, at 03:32 PM, dean.j.robinson wrote:
>
>
>
> > For example:
>
> >https://twitter.com/oauth/authorize?oauth_token=OMxcOPndHoO57JMFURt8G...
>
> > that url doesn't work (returns stanard twitter page not found), but
&
For example:
https://twitter.com/oauth/authorize?oauth_token=OMxcOPndHoO57JMFURt8GyzKpnREj9oKf6aG6f3pU
that url doesn't work (returns stanard twitter page not found), but
this one does
http://twitter.com/oauth/authorize?oauth_token=OMxcOPndHoO57JMFURt8GyzKpnREj9oKf6aG6f3pU
This doesn't always
An enormous thank you from me too! Every other library/example I've
found either didn't appear to work or was a clear a mud to me.
thanks again for sharing.
On Feb 15, 1:03 pm, Abraham Williams <4bra...@gmail.com> wrote:
> I wrote up some example code to get OAuth working in PHP.
>
> Code:http
Great news, can't wait to start learning about it, and implementing it
in Hahlo. A PHP example, even a very basic one, would be very much
appreciated as I've never worked with OAuth before. Looking forward to
hearing more details in the next week or so.
thanks
Dean
The colors I set via the api are still not showing on twitter.com, yet
they are being returned via the api. Is this a bug or could I have
done something wrong when I was setting the colors?
On Dec 31 2008, 3:21 pm, "dean.j.robinson"
wrote:
> I'm in the process of adding a
I'm in the process of adding a screen to Hahlo to allow users to
change their twitter profile colors on the fly, the "post" to the api
works, and returns the updated user info as expected, and when I re-
retrieve a user profile from the api it too reflects the changes I
submitted, but the colors a
Started getting reports from users yesterday that they couldn't login
to hahlo.com.
Turns out that the check I run against "verify credentials" was also
returning code 417 instead of the usual/expected 200, so even though
the check was working to hahlo is looked like it was failing, changed
my ch
D]> wrote:
> I can have it return the "extended" version of the User object, sure.
>
> On Wed, Dec 10, 2008 at 18:26, dean.j.robinson
>
>
>
> <[EMAIL PROTECTED]> wrote:
>
> > Thanks Alex, looks great.
>
> > I'm playing with it now
On Thu, Dec 4, 2008 at 12:42, Brooks Bennett <[EMAIL PROTECTED]> wrote:
>
> > I agree, this is a great change.
>
> > On Dec 3, 11:07 pm, "dean.j.robinson" <[EMAIL PROTECTED]>
> > wrote:
> >> "return the representation of the authenticated user
awesome, I didn't even know that :) I'll be sure to mention that next
someone accuses Hahlo of "double posting"
On Dec 7, 6:29 am, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> We do ignore subsequent identical messages. I'll update the documentation.
>
>
>
> On Sat, Dec 6, 2008 at 10:37, Corey Mens
According to the api docs you can pass an email address to the user/
show method, I would assume that if a user didn't exist you'd get back
a 404, which should allow you to determine whether or not the user
exists.
eg: http://twitter.com/users/[EMAIL PROTECTED]
On Nov 30, 5:02 am, "Abraham Wil
The rewrite of the api has been on the cards for a while, and I've
kind of avoided doing any major work on Hahlo until I knew what was
happening, however it got the better of me last weekend and I began
work on Hahlo 4 which itself is a complete re-write.
Given that its a re-write how much do you
"return the representation of the authenticated user"
does that mean that the response will be the same as if we called
http://twitter.com/users/show/id.format for the authenticated user?
If so that would be awesome and means I could completely eliminate
some of the extra api calls that I'm mak
41 matches
Mail list logo
