Agreed : further absolutely unnecessary obfuscation of links.
The whole reason for the use of shorteners and even the 140 character limit
was in place due to the character restrictions on SMS. SO: Why not JUST
shorten these links for SMS messages they send out?? I'm sure SMS only
users are in a
URL.
As long as Twitter doesn't start abusing this t.co thing, and as long as
it's not down, it's fine with me.
Tom
On 6/10/11 10:09 PM, Kosso wrote:
Agreed : further absolutely unnecessary obfuscation of links.
The whole reason for the use of shorteners and even the 140 character limit
content
in the mouseover.
John, you're smoking something. I just checked Google, Facebook, Bing,
and Yahoo with a search of the term PHP. None of the exposed URLs are
shortened. What they do in the background is irrelevant for the
general public and for the purpose of this discussion.
Kosso
Out of interest, what did you get rejected by Apple for? Was it
anything to do with Twitter? Or was it all objectiveC stuff?
I too have a Twitter client waiting in the wings for submission. Not
long to go now.
I'm just going to launch it and see what happens.
if Twitter 'rejects'/disables it
Yup.
it's down. has been for hours.
users of my app can't log in / authenticate their twitter accounts.
If they're already logged in, they're fine. ie: other API calls work.
On Jul 19, 4:02 pm, cyclemenow cycleme...@gmail.com wrote:
I'm unable to use my own app!
The status page implies that
Out of interest, will there be any (legal?) reason why any of the
attendants can't stream the meetup to UStream, for example?
Also, do we need to bring a ticket, or will we sign in using
OAuth? ;) heh
On Feb 26, 2:19 pm, Ryan Sarver rsar...@twitter.com wrote:
We won't be having a live video
my problems are opposite (using some php scripts) verification is ok,
tweeting ok, but verified timelines (friends and mentions) not ok.
On Jul 27, 9:29 pm, winrich winric...@gmail.com wrote:
ok guys.
so my calls were failing on the verify_credentials call and not on the
update or timeline
Go to http://twitter.com/oauth_clients (assuming it's the oAuth
callback url you're asking about)
Then select your app and click 'edit application settings'
hth
On Jul 26, 6:08 pm, Bob Fishel bobfis...@gmail.com wrote:
How can I change my callback URL?
Go to your 'settings' - then 'connections' - then the link is on the
right, if you have registered apps : http://twitter.com/oauth_clients
hth
On Jul 26, 2:34 pm, Bob Fishel bobfis...@gmail.com wrote:
So i registered an application to learn the ins and outs of the
twitter api for a personal
same here. all was working fine (using abraham's php scripts linked
from the examples) - has not been working for the past couple of
hours.
On Jul 27, 7:44 pm, Duane Roelands duane.roela...@gmail.com wrote:
I am receiving 401 (Unauthorized) when
agreed.
please Twitter, tell us WHAT the fix required was.
what should we look for.
have you tested your 'fix' against all the code examples you link from
the API pages?
that would be nice. thx.
I'm getting some posts through. some not. so something's still up/down
On Jul 27, 8:04 pm,
Just a heads up for British devs (and Matt) :
The UK is currently in 'BST' (British Summer Time) - meaning that the
Twitpocalypse will occur at 10PM. (GMT + 1)
@kosso
On Jun 12, 11:30 am, Matt Sanford m...@twitter.com wrote:
Hello again,
The responses to @twitterapi and all
... they appear to have changed the call from a POST to a GET.
I didn't see an update/change about this.
So, in PHP use:
$to = new TwitterOAuth($consumer_key, $consumer_secret,
$twitterOAuthToken, $twitterOAuthSecret);
$content = $to-OAuthRequest('https://twitter.com/account/
for finally implementing OAuth! Great news!
Regards,
@kosso
14 matches
Mail list logo
