Just over two weeks ago, I talked about more interactive experiences within expanded Tweets and how easy it is for users to discover even more great content on Twitter. The technology behind expanded Tweets -- Twitter cards -- gives developers and publishers a way to tell richer stories on Twitter, directly within Tweets and drive traffic back to their sites. Since launch, we've seen great engagement and more than doubled the number of partners that are part of expanded Tweets, and we continue to add more.
Yesterday we started rolling out a new experience for expanded Tweets that gives partner websites the option to present their content in a more engaging way on Twitter. When users expand Tweets containing links to sites that have opted in to participate, they’ll see content previews, images, videos, and more.
The blue bird has become symbolic of our product and our company. You can find the bird in so many places now — on twitter.com, on mobile phones or tablets, across countless applications and sites that have integrated with the Twitter platform. As Twitter continues to evolve, we think this is the right time to revise the bird.
Today we're happy to announce a big update to our streaming documentation on dev.twitter.com. We've improved the organization of the streaming docs and added supplemental information to better explain the Streaming APIs. If you are new to these APIs, the new introduction page is a great place to start. Developers who are already familiar with streaming concepts will still get a lot out of new pages such as a comprehensive list of query parameters and an explanation of the data formats you'll see in a stream.
We’ve been hosting community-organized Developer Teatimes around the globe, allowing us to meet many developers building great applications on the Twitter platform. We want to do even more of these, so we’re continuing to push forward with the latest series of community-organized Teatime events in a number of new cities. With this format, the local organizers will give a presentation on the Twitter APIs followed by local companies sharing experiences and best practices for integrating with the platform.
The earliest adopters of the Twitter platform arrived with a firm understanding of our service and the objects that represented the various nouns and verbs that describe Twitter's capabilities and opportunity. The platform has grown considerably since and now developers of all levels of familiarity and experience are getting started with the Twitter API.
We've been lucky enough to travel to a number of cities these past several months and meet so many great Twitter developers building on the platform. So we're now looking forward to landing in Paris soon, where we'll be hosting yet another Developer Teatime.
This event will take place on June 16th, and will run from 3pm to 6pm. We'll be covering a number of different topics, including the latest platform developments, an overview of our API product suite, and an in-depth technical session. We'll also be holding a Q&A; for developers at the end of the event.
The SSL Certificate for api.twitter.com is currently signed against the Verisign G2 Root CA certificate. Verisign (recently acquired by Symantec) is no longer issuing new certificates against the G2 root (it expires in 2019.) They are only currently issuing certificates against the Verisign G3 and G5 roots (for EV certificates).
As the certificate for api.twitter.com is due to expire soon, we will be upgrading our servers with a new SSL Certificate that will be signed against the Verisign G3 root.
Discussions on dev.twitter.com are a key place for our developer community to work together and chat about the Twitter Platform and products. Today, we’re introducing new features to surface the most Frequently Asked Questions, providing instant and easy access to the information that matters most to you.
When we originally released the Twitter API back in 2006, little thought was given to API design patterns like explicit versioning, subdomain partitioning, and response structures that would scale with the rapid but unexpected growth of the Twitter service and platform. Over the past two years we've continued refining and upgrading our original API and the monolithic infrastructure that powered it.