The source parameter means nothing. I can change Mitter to identify itself as Twiterrifc, for example. If they take a road like that, some spammer can change the parameter to, say, YOUR application and your users will flock to something else (but, most probably, spammers won't use any source, meaning the source it's the website itself -- which proves nothing.)
On Tue, Jan 6, 2009 at 9:01 AM, Jesse Stay <[email protected]> wrote: > In light of the current Phishing scheme, for the sake of my app and others, > can Twitter include the source of the DM in the XML returned? At least this > way I could start sending my App source id in the feeds so users know which > apps DMs come from, and which ones are not identified. I recognize it's not > a perfect solution, but it is one way I can prove to my users my own app is > not compromised (yes, users are asking out there, and they're asking about > many other apps as well). It's also one way my users can let me know if > they find out for some reason it has been compromised (knock on wood). > > Thanks, > > Jesse > -- Julio Biason <[email protected]> Twitter: http://twitter.com/juliobiason
