Tweets All / No replies
-
Reminder: Twitter User IDs will become 64-bit integers soon. Make sure your software & infrastructure are prepared. https://dev.twitter.com/blog/test-accounts-user-ids-greater-32-bits …
-
The wait is over. Experience the award-winning Crashlytics. Now for Android Studio. http://crash.io/15KUB5Q
#androiddev -
Today, Twitter is updating embedded Tweets to enable a richer photo experience: https://blog.twitter.com/2013/rich-photo-experience-now-in-embedded-tweets-3 …
-
For DMs in User and Site Streams, we're phasing out perspectival attributes. Read more: https://dev.twitter.com/discussions/21526 …
-
Some users are having difficulty logging in to http://dev.twitter.com . We are working to resolve the issue.
-
Change invigorates the soul. I am joining the flock at
@twitter on October 14, as Director of Platform Partnerships http://dev.twitter.com -
Please join us in welcoming
@chabotc to the@twitterapi platform relations team! -
Our platform relations team is growing! Please welcome
@rchoi,@logicalarthur, and@lfcipriani. We're still hiring: https://twitter.com/jobs -
Announcing two accounts with user IDs > 32 bits, for testing https://dev.twitter.com/blog/test-accounts-user-ids-greater-32-bits …
-
String representations for lists of user IDs in connection preambles are now available in User and Site Steams APIs https://dev.twitter.com/discussions/20958 …
-
Introducing Twitter Headlines for Embedded Tweets: https://dev.twitter.com/blog/headlines-tell-story-behind-tweet …
-
We have updated our Player Cards guidelines. Quick overview and discussion in our developer forums: https://dev.twitter.com/discussions/19492 ….
-
Updated Rules of the Road & Display Requirements: more clarity, based on your feedback. Read more in our dev forum: https://dev.twitter.com/discussions/19337 …
-
Thanks everyone! API v1 Retirement is complete. Please use API v1.1 instead. https://dev.twitter.com/blog/api-v1-is-retired …
-
As part of the retirement plan today, we're also about to discontinue Basic Auth support for unelevated Streaming API roles. Use OAuth 1.0A.
-
The retirement of API v1 continues. Most inbound requests should now see HTTP 410, including to the old Search API. https://dev.twitter.com/docs/faq#17750
-
If you were using a legacy widget that no longer functions after API v1 retirement, we suggest using https://dev.twitter.com/docs/embedded-timelines … instead.
-
Looking for a library that supports API v1.1? Check out https://dev.twitter.com/docs/twitter-libraries …
-
We will begin 410ing inbound API v1 traffic now. We will gradually ramp up over the next several minutes. More info: https://dev.twitter.com/docs/faq#17750
-
We're starting the retirement process a little later than expected; we'll tweet as we begin closer to 2:30pm.
@twitterapi hasn't tweeted yet.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Flag this media
This has already been marked as containing sensitive content.