HTTP/2 302
server: nginx
date: Mon, 22 Dec 2025 10:14:51 GMT
content-type: text/plain; charset=utf-8
content-length: 0
x-archive-redirect-reason: found capture at 20101022125839
location: https://web.archive.org/web/20101022125839/https://dev.twitter.com/discuss
server-timing: captures_list;dur=0.877346, exclusion.robots;dur=0.059418, exclusion.robots.policy;dur=0.043154, esindex;dur=0.013513, cdx.remote;dur=25.113350, LoadShardBlock;dur=153.688967, PetaboxLoader3.datanode;dur=101.974075, PetaboxLoader3.resolve;dur=7.339999
x-app-server: wwwb-app54-dc6
x-ts: 302
x-tr: 216
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0
set-cookie: wb-p-SERVER=wwwb-app54; path=/
x-location: All
x-as: 14061
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
HTTP/2 200
server: nginx
date: Mon, 22 Dec 2025 10:14:51 GMT
content-type: text/html; charset=utf-8
x-archive-orig-date: Fri, 22 Oct 2010 12:58:39 GMT
x-archive-orig-server: hi
x-archive-orig-status: 200 OK
x-archive-orig-x-transaction: 1287752319-24189-33175
x-archive-orig-etag: "fa32b3aac24b4a4baa92be1678fdf823"
x-archive-orig-last-modified: Fri, 22 Oct 2010 12:58:39 GMT
x-archive-orig-x-runtime: 0.02333
x-archive-orig-content-length: 9220
x-archive-orig-pragma: no-cache
x-archive-orig-x-revision: DEV
x-archive-orig-expires: Tue, 31 Mar 1981 05:00:00 GMT
x-archive-orig-cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
x-archive-orig-set-cookie: auth_token=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT
x-archive-orig-set-cookie: _twitter_sess=BAh7CjoMY3NyZl9pZCIlZDIyMmY3NDNiNDRkOWViOWFiNTZjNGMyYWIzMWQz%250AN2M6D2NyZWF0ZWRfYXRsKwiL6ATUKwE6DnJldHVybl90byIjaHR0cDovL2Rl%250Adi50d2l0dGVyLmNvbS9kaXNjdXNzIgpmbGFzaElDOidBY3Rpb25Db250cm9s%250AbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsAOgdpZCIlZDMyMWJm%250ANWNkNDVkZGJiZjFmNjhjNTNjOTk1Njg4YjQ%253D--4f29e931c130d14b65dd53f4e0d51c6c7cd65c47; domain=.twitter.com; path=/
x-archive-orig-x-xss-protection: 1; mode=block
x-archive-orig-x-frame-options: SAMEORIGIN
x-archive-orig-vary: Accept-Encoding
x-archive-orig-connection: close
x-archive-guessed-content-type: text/html
x-archive-guessed-charset: utf-8
memento-datetime: Fri, 22 Oct 2010 12:58:39 GMT
link:
; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate"
content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org
x-archive-src: ARCHIVEIT-2142-NONE-FLIING-00000/ARCHIVEIT-2142-NONE-FLIING-20101022125831-00000-crawling109.us.archive.org-6680.warc.gz
server-timing: captures_list;dur=0.731387, exclusion.robots;dur=0.021171, exclusion.robots.policy;dur=0.009960, esindex;dur=0.024907, cdx.remote;dur=11.003395, LoadShardBlock;dur=233.437193, PetaboxLoader3.datanode;dur=228.159907, PetaboxLoader3.resolve;dur=83.648787, load_resource;dur=111.923823
x-app-server: wwwb-app54-dc6
x-ts: 200
x-tr: 420
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0
x-location: All
x-as: 14061
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
content-encoding: gzip
Discuss | dev.twitter.com
Twitter's ID format is changing.
October 19, 2010
Twitter's ID format is changing . Please read , this effects nearly everyone.
More»
x
Last week you may remember Twitter planned to enable the new Status ID generator - 'Snowflake' but didn't. The purpose of this email is to explain the reason why this didn't happen, what we are doing about it, and what the new release plan is.
Previous Announcements
August 31, 2010
Basic Auth has been deprecated. All applications must now use OAuth .
Don't fret! @twitterapi is here to help! Feel free to reach out to us directly, or via our Twitter Development Talk group.
The switch to OAuth is a good thing! You, as the application developer,
don't have the burden of keeping potentially damaging credentials for your users (especially considering that a lot of people use the same password for multiple services);
don't have to worry about the user changing their password — a user can change his or her password and the OAuth "connection" to your app will still work;
don't have to worry about other applications masquerading as your application as only your application can set the byline with your application name;
will eventually have access to more trusted APIs from Twitter that will only be available to "trusted" OAuth-enabled applications; and
will be contributing to the web of trust between users, service providers, and applications.
Choose your authorization path.
Discuss
Get in touch with the Twitter API team and the community of API developers
Mailing lists
Developer Talk Detailed conversations between Twitter developers.
Announcements
Updated only when changes to the Twitter API are released or are pending release.
IRC
#twitterapi on irc.freenode.net