On Wed, Jan 7, 2009 at 2:13 AM, fastest963 wrote:
> Apps should get an API-key or something and then if they wanted their
> source name included then they would have to use their API-key and it
> would do a lookup key -> name from there?
> That would only apply for apps that want their name as th
Apps should get an API-key or something and then if they wanted their
source name included then they would have to use their API-key and it
would do a lookup key -> name from there?
That would only apply for apps that want their name as the source.
Also, if that could be implemented, an optional,
On Mon, Jan 5, 2009 at 8:22 PM, Julio Biason wrote:
>
> 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 somethin
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, mean
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
