I wasn't able to attend the announcement regarding ABUIKit / TwUI. Can
someone provide a summary of what was presented?
Thanks.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https
And... it appears to have just gone live.
On Jun 8, 11:37 am, SM wrote:
> When will force_login go live for authorize? There is an approaching
> deadline for the switch from xAuth to OAuth and time is needed for
> testing, fixes, app approval and some buffer for contingencies.
--
When will force_login go live for authorize? There is an approaching
deadline for the switch from xAuth to OAuth and time is needed for
testing, fixes, app approval and some buffer for contingencies.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twi
When exactly do links get wrapped in t.co URLs? In the stream of
people I follow, I've noticed more links getting wrapped this way
recently, but it's not every single link.
Will there be a time when every single link is wrapped with t.co?
--
Twitter developer documentation and resources: https:/
Are tweet entities required for parsing Twitter Photos? Many clients
do their own parsing and can figure out when a link is an image based
on the URL (twitpic, yfrog, etc). It looks like Twitter Photos will
use t.co in which case it doesn't look possible to figure out whether
the link is an image b
representation a hack
> around some issues with certain programming languages, and not an
> optimal solution. Wouldn't want this to become the default option.
>
> 2) No
>
> Tom
>
> On 11/11/10 6:34 AM, SM wrote:
>
>
>
>
>
>
>
> > Hello. Coupl
Hello. Couple questions:
1.) Are you planning on eventually eliminating the integer
representation and only using strings for id's?
2.) If an application doesn't use Javascript to parse JSON (for
example, YAJL-OBJC and NSNumbers in Obj-C), is it necessary to make
any changes at all?
Thanks.
O
Will the conversion to Snowflake affect clients using the yajl-objc
framework? Does yajl-objc already parses 64-bit unsigned integers
correctly?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements
I'm also getting deleted statuses in the home timeline via the API.
The ones I'm looking at now are about 4 hours old.
I hope this is fixed soon.
On Oct 10, 1:06 am, CWorster wrote:
> Hello,
>
> I start noticing this issue 3-4 days ago. Thedeletedtweets
> disappeared after several hours (up to 1
Hi Taylor,
I am missing all mentions since July 31. This has been the case for at
least a week, probably more.
On Aug 24, 8:17 am, Taylor Singletary
wrote:
> There is a known issue related to JSON timelines containing null elements,
> which has crippled some clients. We'll have a fix for this dep
How do the offsets for tweet entities work when the tweet is a new-
style retweet (which doesn't include the letters RT). Do the offsets
include an implicit "RT"? Do we have to correct for this if we are
only doing new-style retweets?
I'd like to test some OAuth code. As part of that I'd like to create
some test accounts with representative screennames and passwords so I
can make sure I do the encoding right.
What characters are valid for screenname and password?
I have an OAuth app (http://mowglii.com/itsy) and I'm getting errors
saying I'm limited to 75 requests per hour. Huh?
Thanks, Abraham.
On May 17, 3:24 pm, Abraham Williams <4bra...@gmail.com> wrote:
> http://status.twitter.com/post/599443974/remember-me-login-feature-te...
>
> Abraham
>
>
>
>
>
> On Mon, May 17, 2010 at 14:12, SM wrote:
> > It looks like a change was rece
It looks like a change was recently made to mobile.twitter.com so that
it no longer remembers logins. Every time I quit the browser and then
revisit the site, I have to re-login.
1. Open browser (Chrome, Safari, etc)
2. Visit http://mobile.twitter.com
3. Log in
4. Quit browser
5. Relaunch browser
nding?
>
> Thanks!
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Fri, Mar 12, 2010 at 12:22 PM, SM wrote:
> > My desktop app uses Adobe AIR with Javascript. I'm using the OAuth
> > javascript library from here:
>
>
My desktop app uses Adobe AIR with Javascript. I'm using the OAuth
javascript library from here:
http://oauth.googlecode.com/svn/code/javascript/
I am able to POST with xAuth to get the token/token_secret. I am then
able to GET timelines using the received tokens. However, so far I am
unable
ur app?
>
> On 3/9/10 5:14 PM, "SM" wrote:
>
>
>
> > On the application detail page there is a stat that shows how many
> > users your app has.
>
> > How is this stat calculated? Is it the number of authorized tokens or
> > does it reflect some ro
On the application detail page there is a stat that shows how many
users your app has.
How is this stat calculated? Is it the number of authorized tokens or
does it reflect some rolling count of accesses using an authorized
token? Or some other calculation?
If someone uses my app once and then fo
> > If that is the reason for disallowing the source param, why is this
> > policy not being applied uniformly? How would users of Tweetie,
> > Twitterrific, etc. feel if all their updates now said 'from web'? How
> > would the developers of those apps feel?
>
> those applications have been grandfa
> > What is the reason for no longer allowing the source parameter for
> > Basic Auth desktop apps?
>
> the ability to "forge" the source parameter is too easy when simply using
> basic auth.
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi
Hi Raffi,
If that is the reason
> > What is the reason for no longer allowing the source parameter for
> > Basic Auth desktop apps?
>
> the ability to "forge" the source parameter is too easy when simply using
> basic auth.
Hi Raffi,
Why not disallow it for all apps then? Would the users of Tweetie,
Twitterrific, etc like that?
Hi Raffi,
What is the reason for no longer allowing the source parameter for
Basic Auth desktop apps?
The issue is this: The policy is blatantly unfair. The current policy
benefits some desktop apps that use Basic Auth while penalizing
others. The policy should either remove the source parameter
I'd like for Twitter to reinstate granting 'from app' links for
desktop apps that use Basic Auth.
As it stands, developers who have relatively new desktop apps are
penalized by having updates from their app say 'from web'. Older Basic
Auth desktop clients continue to enjoy a link back to the clien
I agree with Isaiah. This is a huge improvement over the current PIN
workflow.
When will this roll out? Is there an authorization endpoint we can use
now for testing purposes? That would be great.
On Dec 10 2009, 8:58 am, Isaiah wrote:
> This seems like a dramatic improvement to me. When will T
I've noticed both on twitter.com and via the API that a tweet from a
person I follow isn't showing up in my home timeline. I can see older
tweets from this person in my home timeline and in my @ timeline, but
not the latest one.
I'm trying to write an HTML/Javascript/AJAX app using Adobe Air. I'm
using XMLHttpRequest to verify credentials. When the user supplies
incorrect credentials, the Twitter API sends back the 401 status which
seems to automatically pull up the standard Windows credentials dialog
box.
How do I suppr
27 matches
Mail list logo