Custom Query (1098 matches)

AIM may be breaking non-clientlogin auth at some point in the future. Non-libpurple bitlbee doesn't support that. It had a specified shutdown date but it was suspended and it's unspecified now. Still should be done.

​http://web.archive.org/web/20120124160700/http://dev.aol.com/authentication_for_clients

​http://web.archive.org/web/20080310152955/http://dev.aol.com/aim/oscar

​http://web.archive.org/web/20080309222525/http://dev.aol.com/aim/web/serverapi_reference#startOSCARSession

​http://web.archive.org/web/20080309055747/http://dev.aol.com/aim/clients

​http://localhost:18000/notebooks/aim%20clientlogin.ipynb

Currently, every Tweet (and DM) posted has a "field" "source":

Utility used to post the Tweet, as an HTML-formatted string. Tweets from the Twitter website have a source value of web . Example:

"source":"\u003Ca href=\"http:\/\/itunes.apple.com\/us\/app\/twitter\/id409789998?mt=12\" \u003ETwitter for Mac\u003C\/a\u003E"

​https://dev.twitter.com/overview/api/tweets

Metadata like this is revealing and should be avoided or optional where possible.

If the Twitter API allows posting without this: please provide an option to disable the source value, like "account twitter set source false".

If the Twitter API does not allow it, please add an option to accept user values like "account twitter set source <string>".

Thanks, and keep up the good work!

< passcod> [49] Another "everything is awful" about the new @twitter reply UI: any indication a retweet is a reply vanishing upon tap. https://t.co/PTph19Vgdi <pic.twitter.com/PTph19Vgdi> <pic.twitter.com/PTph19Vgdi>

​https://twitter.com/passcod/status/791513337783734272

I can sorta see why this happens, since it grabs the entities from a different place.