<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://webarchive.nationalarchives.gov.uk/20100407032215/http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce</id>
  <title type="text">Twitter API Announcements Google Group</title>
  <subtitle type="text">
  A low-volume group, updated only when changes to the Twitter API are released or are pending release. More detailed conversation happens at http://groups.google.com/group/twitter-development-talk.
  </subtitle>
  <link href="http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/feed/atom_v1_0_msgs.xml" rel="self" title="Twitter API Announcements feed"/>
  <updated>2010-08-13T23:12:53Z</updated>
  <generator uri="http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Taylor Singletary</name>
  <email>taylorsinglet...@twitter.com</email>
  </author>
  <updated>2010-08-13T23:12:53Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c03fa2b1ae90d2a9/a56592abbce575d9?show_docid=a56592abbce575d9</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c03fa2b1ae90d2a9/a56592abbce575d9?show_docid=a56592abbce575d9"/>
  <title type="text">Twitter API &amp; the Basic Auth Shutdown: Everything you need to know.</title>
  <summary type="html" xml:space="preserve">
  Hi Developers, &lt;br&gt; Basic authentication is being deprecated beginning on August 16th. After &lt;br&gt; August 31st, API clients will no longer be able to identify themselves using &lt;br&gt; only a login and password when accessing the Twitter REST API. &lt;br&gt; For those that just like to skim, here are the basics: &lt;br&gt; - Basic Auth will be completely shut off on August 30th.
  </summary>
  </entry>
  <entry>
  <author>
  <name>themattharris</name>
  <email>thematthar...@twitter.com</email>
  </author>
  <updated>2010-08-12T15:27:30Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/028d83b0fc0c450b/8076d376422a618f?show_docid=8076d376422a618f</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/028d83b0fc0c450b/8076d376422a618f?show_docid=8076d376422a618f"/>
  <title type="text">Introducing the Tweet Button</title>
  <summary type="html" xml:space="preserve">
  Hey everyone, &lt;br&gt; &lt;p&gt;Today we’re launching the Tweet Button to make it easy for your users &lt;br&gt; to share your website with their followers. When they click on the &lt;br&gt; Tweet Button, a Tweet box will appear pre-populated with a message and &lt;br&gt; link chosen by you. Once they have sent a Tweet they can choose to &lt;br&gt; follow accounts recommended by you. All of this happens on your
  </summary>
  </entry>
  <entry>
  <author>
  <name>Taylor Singletary</name>
  <email>taylorsinglet...@twitter.com</email>
  </author>
  <updated>2010-07-28T19:52:47Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/f7b3dd8ac9e10395/1e1eeeefc496b038?show_docid=1e1eeeefc496b038</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/f7b3dd8ac9e10395/1e1eeeefc496b038?show_docid=1e1eeeefc496b038"/>
  <title type="text">Announcing a limited User Streams testing period for desktop apps</title>
  <summary type="html" xml:space="preserve">
  Hi Developers, &lt;br&gt; User Streams is now in a limited testing period for desktop clients. We are &lt;br&gt; working closely with developers to preview their implementations to a &lt;br&gt; restricted set of testers. We are gathering feedback and usage statistics to &lt;br&gt; prepare for an open beta period, tentatively scheduled for late Q3 or Q4 of
  </summary>
  </entry>
  <entry>
  <author>
  <name>John Kalucki</name>
  <email>j...@twitter.com</email>
  </author>
  <updated>2010-07-20T22:52:29Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/43e0f704d9aba601/9ae22c47bc5c420d?show_docid=9ae22c47bc5c420d</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/43e0f704d9aba601/9ae22c47bc5c420d?show_docid=9ae22c47bc5c420d"/>
  <title type="text">TLS (SSL) cipher suites on User Streams preview</title>
  <summary type="html" xml:space="preserve">
  We&#39;ve changed the set of supported TLS Cipher Suites on the User &lt;br&gt; Stream service preview. If your SSL-enabled client suddenly starts to &lt;br&gt; have troubles negotiating a connection to betastream.twitter.com or &lt;br&gt; chirpstream.twitter.com on port 9443 as of 22:40 UTC today, July 20th, &lt;br&gt; this is probably why. Please let us know, and we&#39;ll work to resolve
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ryan Sarver</name>
  <email>rsar...@twitter.com</email>
  </author>
  <updated>2010-07-07T14:18:42Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/130a8c1749a87279/0f9d28ef4eab3a77?show_docid=0f9d28ef4eab3a77</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/130a8c1749a87279/0f9d28ef4eab3a77?show_docid=0f9d28ef4eab3a77"/>
  <title type="text">Temporary changes to whitelisting</title>
  <summary type="html" xml:space="preserve">
  I wanted to email everyone and give notice that we are going to be holding &lt;br&gt; off on approving any additional whitelist requests until after the World Cup &lt;br&gt; is over. We actually paused this last week, so if you haven&#39;t gotten a &lt;br&gt; response, this is why. It will take us a while to get through the backlog &lt;br&gt; after the World Cup, so please be patient and don&#39;t reapply as it just makes
  </summary>
  </entry>
  <entry>
  <author>
  <name>John Kalucki</name>
  <email>j...@twitter.com</email>
  </author>
  <updated>2010-07-06T19:29:03Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/e489615896f07e88/e111045903511337?show_docid=e111045903511337</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/e489615896f07e88/e111045903511337?show_docid=e111045903511337"/>
  <title type="text">User Streams Preview Update</title>
  <summary type="html" xml:space="preserve">
  User Streams is a Streaming API feature that allows clients to receive &lt;br&gt; nearly all events required to update an application in real-time and without &lt;br&gt; managing polling rate-limits. &lt;br&gt; Two recent changes: &lt;br&gt; * @replies from non-mutual followings are now filtered on the server by &lt;br&gt; default. This behavior now matches the &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.twitter.com&quot;&gt;[link]&lt;/a&gt; display. If you wish
  </summary>
  </entry>
  <entry>
  <author>
  <name>Raffi Krikorian</name>
  <email>ra...@twitter.com</email>
  </author>
  <updated>2010-06-23T19:20:51Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/3395f28bbce2e805/a9289515501e2028?show_docid=a9289515501e2028</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/3395f28bbce2e805/a9289515501e2028?show_docid=a9289515501e2028"/>
  <title type="text">modifying rate limits under serious load</title>
  <summary type="html" xml:space="preserve">
  hi everyone, &lt;br&gt; as you all know, Twitter has been faced with considerable capacity problems &lt;br&gt; in recent weeks. we have many efforts under way to expand capacity and more &lt;br&gt; efficiently use the capacity we have. starting today, we&#39;re going to begin &lt;br&gt; adjusting rate limits dynamically under load in order to maintain an awesome
  </summary>
  </entry>
  <entry>
  <author>
  <name>Taylor Singletary</name>
  <email>taylorsinglet...@twitter.com</email>
  </author>
  <updated>2010-06-22T23:18:49Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/0b0ca89823de5d65/85e16517fd4fbfd2?show_docid=85e16517fd4fbfd2</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/0b0ca89823de5d65/85e16517fd4fbfd2?show_docid=85e16517fd4fbfd2"/>
  <title type="text">api.twitter.com/1/search.* is no longer functional, use search.twitter.com/search instead</title>
  <summary type="html" xml:space="preserve">
  Hi Everyone, &lt;br&gt; As we warned back in May ( &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://bit.ly/9vBx5m&quot;&gt;[link]&lt;/a&gt; ), we&#39;ve now removed Search &lt;br&gt; API access from our undocumented endpoint at api.twitter.com. If you&#39;re &lt;br&gt; using the Search API, all of your requests should be sent to &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://search.twitter.com/search&quot;&gt;[link]&lt;/a&gt; instead. &lt;br&gt; For those using &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://twitter.com/search&quot;&gt;[link]&lt;/a&gt;, &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://api.twitter.com/search&quot;&gt;[link]&lt;/a&gt;, or
  </summary>
  </entry>
  <entry>
  <author>
  <name>Raffi Krikorian</name>
  <email>ra...@twitter.com</email>
  </author>
  <updated>2010-06-17T23:46:06Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/dfb89d9f29f339a2/fcc1422966e7be5b?show_docid=fcc1422966e7be5b</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/dfb89d9f29f339a2/fcc1422966e7be5b?show_docid=fcc1422966e7be5b"/>
  <title type="text">moving the OAuth switch over date to august 16, 2010</title>
  <summary type="html" xml:space="preserve">
  hi all. &lt;br&gt; as you&#39;ve all probably noticed, with the world cup going on, twitter is &lt;br&gt; experiencing record load. because of this, we&#39;re moving the oauth switchover &lt;br&gt; date to august 16, 2010. &lt;br&gt; we want to make sure that you all have calm waters to test your new &lt;br&gt; codebases where you&#39;re not dealing with whales, robots, and whatnot. with
  </summary>
  </entry>
  <entry>
  <author>
  <name>Taylor Singletary</name>
  <email>taylorsinglet...@twitter.com</email>
  </author>
  <updated>2010-06-16T13:31:12Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/2150dd6284c5dd7b/4179efce4eea60e9?show_docid=4179efce4eea60e9</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/2150dd6284c5dd7b/4179efce4eea60e9?show_docid=4179efce4eea60e9"/>
  <title type="text">Scheduled Twitter API Network Maintenance, June 16th @ 6-7:30 AM PDT 21</title>
  <summary type="html" xml:space="preserve">
  Hi Developers, &lt;br&gt; A little late notice, but just wanted to make sure you&#39;ve all seen what was &lt;br&gt; posted on the Twitter status blog a bit earlier: &lt;br&gt; MAINTENANCE ACTION: &lt;br&gt; ————————— &lt;br&gt; We’ll be working with our network provider to perform some tests and &lt;br&gt; maintenance. During this time you can expect a high rate of errors (whales)
  </summary>
  </entry>
  <entry>
  <author>
  <name>Raffi Krikorian</name>
  <email>ra...@twitter.com</email>
  </author>
  <updated>2010-06-08T22:57:21Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/14d5474c13ed84aa/0f78b195eda96990?show_docid=0f78b195eda96990</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/14d5474c13ed84aa/0f78b195eda96990?show_docid=0f78b195eda96990"/>
  <title type="text">link wrapping on the API</title>
  <summary type="html" xml:space="preserve">
  hi all. &lt;br&gt; twitter has been wrapping links in e-mailed DMs for a couple months &lt;br&gt; now&amp;lt;&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://bit.ly/twttldmemail&quot;&gt;[link]&lt;/a&gt;&amp;gt;. &lt;br&gt; with that feature, we&#39;re trying to protect users against phishing and other &lt;br&gt; malicious attacks. the way that we&#39;re doing this is that any URL that comes &lt;br&gt; through in a DM gets currently wrapped with a twt.tl URL -- if the URL turns
  </summary>
  </entry>
  <entry>
  <author>
  <name>Taylor Singletary</name>
  <email>taylorsinglet...@twitter.com</email>
  </author>
  <updated>2010-06-07T16:48:10Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/228cf4ba766a37cf/dfb0ddf17490aedb?show_docid=dfb0ddf17490aedb</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/228cf4ba766a37cf/dfb0ddf17490aedb?show_docid=dfb0ddf17490aedb"/>
  <title type="text">In San Francisco for WWDC? Come to Twitter HQ on June 9th 6-8pm for a @twitterapi meetup!</title>
  <summary type="html" xml:space="preserve">
  Hi Mac Devs, &lt;br&gt; This time last year we hosted an informal meetup of WWDC attendees. The &lt;br&gt; event turned into a fun evening so we&#39;ve decided to do it again. We are &lt;br&gt; inviting WWDC attendees and Twitter Platform developers to our office on &lt;br&gt; Wednesday, June 9, at 6PM. There is limited space, so please register at
  </summary>
  </entry>
  <entry>
  <author>
  <name>John Kalucki</name>
  <email>j...@twitter.com</email>
  </author>
  <updated>2010-06-02T21:49:12Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c2441464b516d59b/274fdd02e3328fc0?show_docid=274fdd02e3328fc0</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c2441464b516d59b/274fdd02e3328fc0?show_docid=274fdd02e3328fc0"/>
  <title type="text">Annotations in Streams - June 7th</title>
  <summary type="html" xml:space="preserve">
  We will test Streaming API Tweet Annotation as early as next week - June 7th &lt;br&gt; through June 11th. All streaming clients, including user streams preview &lt;br&gt; clients, should expect empty annotations and the rare populated annotation &lt;br&gt; during arbitrary test periods. Assuming general stability, on our end and &lt;br&gt; yours, we&#39;ll eventually leave annotation delivery turned permanently on.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Mark McBride</name>
  <email>mmcbr...@twitter.com</email>
  </author>
  <updated>2010-05-30T13:21:30Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c47f6f37048a7985/7256f7f0ea773197?show_docid=7256f7f0ea773197</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/c47f6f37048a7985/7256f7f0ea773197?show_docid=7256f7f0ea773197"/>
  <title type="text">List events now available in userstreams</title>
  <summary type="html" xml:space="preserve">
  The userstreams preview now delivers list updates in addition to the &lt;br&gt; social graph changes it is already streaming. This includes &lt;br&gt; * Lists created/updated/destroyed by you or your followings &lt;br&gt; * List members added/removed by you or your followings &lt;br&gt; * List subscriptions added/removed by you or your followings
  </summary>
  </entry>
  <entry>
  <author>
  <name>Mark McBride</name>
  <email>mmcbr...@twitter.com</email>
  </author>
  <updated>2010-05-24T20:51:50Z</updated>
  <id>http://webarchive.nationalarchives.gov.uk/20100407032215/http://groups.google.com/group/twitter-api-announce/browse_thread/thread/4ff33ef2d9d9d009/1fb6cd60ac9402e4?show_docid=1fb6cd60ac9402e4</id>
  <link href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/4ff33ef2d9d9d009/1fb6cd60ac9402e4?show_docid=1fb6cd60ac9402e4"/>
  <title type="text">[twitter-api-announce] OAuth now supported on stream.twitter.com</title>
  <summary type="html" xml:space="preserve">
  The production streaming API (stream.twitter.com) now has support for &lt;br&gt; OAuth 1.0A. Please let me know if you run into any issues. &lt;br&gt; &lt;p&gt; ---Mark &lt;br&gt; &lt;p&gt;&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://twitter.com/mccv&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;p&gt;-- &lt;br&gt; Twitter API documentation and resources: &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://apiwiki.twitter.com&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; API updates via Twitter: &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://twitter.com/twitterapi&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
</feed>

