We want to get the replies to our tweets, which I would have thought
was simple enough ... but proves not to be so ...
Using Mentions is one mechanism which looks like it will work OK,
but I'm reading that using the Search API is the recommended route.
Using the Search route, with to:user works
DK was abandonded by Yahoo awhile ago, but DKIM is very stable.
Twitter runs DKIM signing and verification code on all of our mail
servers, as does Google, Facebook, Yahoo, and many other major sites.
OK. Will study further and implement the necessary check.
And Dale - I somehow missed
I'd think with the recent changes to the replies (mentions) functionality,
there isn't a reason to use search any more (for that functionality).
Mentions now include any tweet that has your @username in it. Whereas before
it did not. Of course, now the in_reply_to_status_id might not be to one of
That would work. So would something a a bit simpler.
I am not sure I see the need for the username to be passed back.
Seems like that could easily be done by the site. Also unsure as to
why the special key is needed if it's always just returned as a
parameter.
Is this something that can be
Casey,
I believe you received some misguided advice. The statuses/mentions [1]
method is your best bet. With a single call to this method you will have
access to all mentions of your username and the actual status data [2] and
in_reply_to data.
1.
Glad that you are finally getting around to this.
I posted it April 10th
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/960612fbcb8059de/5c2231ff33cff9e6?lnk=gstq=revoke#5c2231ff33cff9e6
On May 6, 10:28 am, jmathai jmat...@gmail.com wrote:
That would work. So
This is a bug introduced in the last deploy. We've all agreed on the
VERP format,
twitter-follow-emailname=domain@postmaster.twitter.com
I'll follow up with engineering and file a bug. Sorry about this.
-john
On May 6, 2009, at 2:53 PM, TjL wrote:
The email notifications for new
I thought I'd add my $.02 to this thread.
I'm working on an iPhone app that uses the Twitter API.
This is a side project for me with a small budget and tight timelines.
I'm using Matt Gemmel's Objective-C library to integrate with Twitter.
Everything was going along smoothly, until I realized
On Wed, May 6, 2009 at 18:05, MPS mpelzsher...@gmail.com wrote:
I thought I'd add my $.02 to this thread.
I'm working on an iPhone app that uses the Twitter API.
This is a side project for me with a small budget and tight timelines.
I'm using Matt Gemmel's Objective-C library to integrate
Don't touch that dial …
We're (John and I) discussing bounce processing and spam
detection and may have to revert the from address change to help with
people's spam filters. I'll update once I know more.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On May 6, 2009, at 3:13
nore...@twitter.com isn't the best choice because many mailers on the
Internet refuse to acknowledge Errors-To: headers.
Right now, because there is little industry consensus on how to
properly handle a bounce (aside from send a message back to the Return-
Path:) our VERP methodology on
It seems John and I cannot help but write mails at the same time :)
— Matt
On May 6, 2009, at 3:54 PM, John Adams wrote:
nore...@twitter.com isn't the best choice because many mailers on
the Internet refuse to acknowledge Errors-To: headers.
Right now, because there is little industry
Alex,
I'm getting this xml parsing error all day long. I'm using jdom.jar
and pass twitter api xml response directly to build jdom document.
Looking at the xml file right now, but hope you can take at look at it
as well. I expect other jdom users may see the same error.
2009-05-06 19:11:49,401
I'm getting this xml parsing error all day long. I'm using jdom.jar
and pass twitter api xml response directly to build jdom document.
Looking at the xml file right now, but hope you can take at look at it
as well. I expect other jdom users may see the same error.
2009-05-06 19:11:49,401
I switch to use http://twitter.com/statuses/public_timeline.xml, and
jdom does not throw the same error.
I check xml specs and here is what I think:
the data mining feed http://twitter.com/statuses/
public_timeline_partners_#.xml returns xml document containing an
invisible end of medium
*sigh*
Seriously? I've already started telling people to change their filters
and now they're going to break *again*.
This is why daddy drinks.
All kidding aside, I don't understand how a change like this gets
pushed out without the left hand knowing WTF the right hand is doing —
which is what
16 matches
Mail list logo
