This approach feels wrong to me. The red flag is the duplication of
data within the payload: in 30+ years of professional development,
I've never seen that work out well.
The root of the problem is that you've chosen to deliver data in a
format (JSON) that can't support integers with a value
it
and requires minimal implementation effort for developers.
I hope I'm not too late with my suggestion :-)
Tom
On 10/19/10 7:10 PM, Craig Hockenberry wrote:
This approach feels wrong to me. The red flag is the duplication of
data within the payload: in 30+ years of professional
5 minutes (or even 15 minutes) for the OAuth timestamp is a major
problem on the iPad. This device doesn't have a guaranteed network
connection and therefore doesn't do NTP syncs on a regular basis. It's
common for these devices to be off by an hour or more.
We do a check at startup against the
yFrog supports OAuth echo, but with a different technique than Raffi
proposed on his blog:
http://code.google.com/p/imageshackapi/wiki/TwitterAuthentication
I also know that img.ly is working on the echo endpoint.
-ch
On May 20, 10:38 pm, Rich rhyl...@gmail.com wrote:
This are the providers I
It's not in this documentation, which is the first thing I found:
http://dev.twitter.com/pages/auth
-ch
On Apr 25, 1:40 pm, Abraham Williams 4bra...@gmail.com wrote:
It is specified on the XAuth documentation.
On Sun, Apr 25, 2010 at 13:39, Craig Hockenberry
craig.hockenbe
Hi Raffi!
Is there a delay/verification after a new app is created? I just
created a new app and am seeing problems getting the OAuth token with
a xAuth HTTP request that looks like this:
xAuth consumer key = N3fq77IdBT4qfglbcb4njg, consumer secret =
REDACTED
xAuth URL =
? applications are not, by default, given
access to xAuth - if you e-mail a...@twitter.com with
- your client token; and
- a description of your application
then we can grant it access.
On Sun, Apr 25, 2010 at 1:22 PM, Craig Hockenberry
craig.hockenbe...@gmail.com wrote:
Hi Raffi
Hi Taylor!
Please comment on how this change will affect this bug:
http://code.google.com/p/twitter-api/issues/detail?id=1529
Hopefully, the timestamp portion of the ID will allow since_id to work
correctly when load increases.
-ch
On Mar 26, 1:41 pm, Taylor Singletary
Just wrote up this bug:
http://code.google.com/p/twitter-api/issues/detail?id=1529
I'm aware of several other developers of mobile Twitter clients that
are affected by this issue. If you are as well, please chime in and
star the bug.
Thanks!
-ch
To everyone who's suggesting to embed a web view in the desktop or
mobile app, please go read this:
http://fireeagle.yahoo.net/developer/documentation/
oauth_best_practice
Specifically, ... we insist that you must not use embedded rendering
controls to present the OAuth process
Phishing
2. What can be improved about the desktop workflow?
Get Apple to integrate OAuth into the existing keychain mechanisms on
the Mac and iPhone:
http://blog.atebits.com/2009/02/fixing-oauth/
Until that happens, no user or developer is going to be happy with
OAuth in a desktop or mobile
We're seeing a weird error occur with the API in the past few days:
every so often, users will get malformed JSON data. From our app, the
following message is displayed:
http://files.iconfactory.net/craig/bugs/TwitterYAJL.jpg
That error occurs when the JSON data can't be parsed.
I'd like to
of the failure to
be sent to a...@twitter.com.
--Naveen A.
On Sep 9, 12:02 pm, Craig Hockenberry craig.hockenbe...@gmail.com
wrote:
We're seeing a weird error occur with the API in the past few days:
every so often, users will get malformed JSON data. From our app, the
following
An added benefit to this approach is it adds a disincentive for SPAM.
Spammers don't waste time on things that no one will ever see...
-ch
On Sep 8, 9:12 am, Craig Hockenberry craig.hockenbe...@gmail.com
wrote:
As we're all aware, there has been a huge influx of spammy followers
(e.g
As we're all aware, there has been a huge influx of spammy followers
(e.g. @Girl12345.)
These accounts are deactivated quickly enough, but we're seeing cases
where they accounts hang around in the user's follower list. From the
application's point-of-view, there's no way to know that the
/entries/15790
Thanks,
Doug
On Wed, Jun 24, 2009 at 9:57 AM, richardhenry richardhe...@me.com wrote:
As someone who followed Louie, this is very weird to me. Nothing he
did looked remotely spammy/offensive/disingenuous. #freemantia
-- Richard (@richardhenry)
On Jun 24, 5:43 pm, Craig
The issue appears to affect the website, as well. When you click on
the star, it changes color, but doesn't show up in your favorites
list.
-ch
On Jun 24, 11:25 am, Craig Hockenberry craig.hockenbe...@gmail.com
wrote:
FYI:
We've been getting reports of favoriting not working in our app
Hockenberry wrote:
The issue appears to affect the website, as well. When you click on
the star, it changes color, but doesn't show up in your favorites
list.
-ch
On Jun 24, 11:25 am, Craig Hockenberry craig.hockenbe...@gmail.com
wrote:
FYI:
We've been getting reports of favoriting
Matt Doug,
Here's some more information to help fingerprint search requests:
The MGTwitterEngine library sends the following X headers by default:
X-Twitter-Client: MGTwitterEngine
X-Twitter-Client-Url: http://mattgemmell.com/source
X-Twitter-Client-Version: 1.0
These can be overridden by
I agree with Chad: explicitly stating the source and target in the
attribute name makes it much clearer. It also has a side benefit of
bringing the information you need most (for a UI) to the top of the
results hierarchy.
-ch
On Jun 9, 10:52 am, Marcel Molina mar...@twitter.com wrote:
Thanks
Yes, please!
Since we don't really know what the conference schedule looks like
right now, I'm going to say that any afternoon except Monday and
Friday would be best.
-ch
On May 21, 2:18 pm, Alex Payne a...@twitter.com wrote:
Hi all,
There's great crossover between Twitter API developers
Let me be the first to say THANK YOU for this advance notice. I found
and fixed some bugs in our iPhone client today because of it — and I'm
very happy to hear that we have some time to get the code approved in
the App Store.
We love to complain when the process goes awry, but it's also
Are replies created by setting the in_reply_to_status_id with the
statuses/update method affected by this change?
There are some clients that set the id when doing things like
retweeting -- and these may or may not have a reference to a user's
screen name in them. Will these tweets continue to
Thanks for the clarification, Doug. Overall, I think this is a very
positive change. Just a little spooked that it came out of the blue
like it did - maybe next time it would be wise to give us a bit of a
heads up before deploying...
More questions:
On http://twitter.com/account/notifications,
as it moves
from cache to backing store thing is totally unacceptable. Answers
soon.
On Fri, Mar 6, 2009 at 09:43, Craig Hockenberry
craig.hockenbe...@gmail.com wrote:
Some discussion about this thread popped up on Twitter yesterday:
http://groups.google.com/group/twitter-development-talk
DO NOT ENCODE WITH HTML ENTITIES.
The only reason that and are encoded as lt; and gt; is because
these values are represented within an XML text element. This is
invalid XML:
textThis -- is a test/text
And this is valid XML:
textThis lt;-- is a test/text
If you use HTML entities, they will
Some discussion about this thread popped up on Twitter yesterday:
http://groups.google.com/group/twitter-development-talk/browse_thread/
thread/44be91d5ec5850fa
Alex states that it's 140 bytes per tweet. So, of course, Loren
Brichter and I tried to prove that. With the following results:
1)
As a user, there are a couple of things I'd like to see in search
(both the Advanced UI form and in the API):
1) The ability to search for replies to a given tweet ID. The use case
for this is when someone asks a question like What's the best place
to get T-shirts printed in small runs?. The
[EMAIL PROTECTED] wrote:
On Thu, Nov 6, 2008 at 12:34 PM, Craig Hockenberry
[EMAIL PROTECTED] wrote:
1) The ability to search for replies to a given tweet ID. The use case
for this is when someone asks a question like What's the best place
to get T-shirts printed in small runs
29 matches
Mail list logo
