Multi-user Twitter Applications - Revision history

Admin: /* Implementation */

2018-03-09T03:09:05Z

Implementation

← Older revision		Revision as of 03:09, 9 March 2018
Line 70:		Line 70:
	?>		?>
	</source>		</source>


			=Flags=

			[[Category:Twitter]]
			[[Category:Bots]]
			[[Category:Python]]
			[[Category:PHP]]

Admin: /* Implementation */

2014-05-10T19:18:26Z

Implementation

← Older revision		Revision as of 19:18, 10 May 2014
Line 37:		Line 37:
	$options = array(		$options = array(
	'http' => array(		'http' => array(
	'header' => "Content-type: ~~application~~/x-~~www-form-urlencoded~~\r\n",		'header' => "Content-type: text/html; charset=utf-8\r\n",
	'method' => 'POST',		'method' => 'POST',
	'content' => http_build_query($data),		'content' => http_build_query($data),

Admin: /* Implementation */

2014-05-10T19:17:28Z

Implementation

← Older revision		Revision as of 19:17, 10 May 2014
Line 59:		Line 59:
	$options = array(		$options = array(
	'http' => array(		'http' => array(
	'header' => "Content-type: ~~application~~/x-~~www-form-urlencoded~~\r\n",		'header' => "Content-type: text/html; charset=utf-8\r\n",
	'method' => 'POST',		'method' => 'POST',
	'content' => http_build_query($data),		'content' => http_build_query($data),

Admin: /* Implementation */

2014-05-10T19:14:49Z

Implementation

← Older revision		Revision as of 19:14, 10 May 2014
Line 53:		Line 53:
	<source lang="php">		<source lang="php">
	<?php		<?php
	$url = '~~http~~://~~server~~.com/~~path~~';		$url = 'https://api.twitter.com/oauth/request_token';
	$data = array('oauth_callback' => 'oob'); // value is set to "oob" following https://dev.twitter.com/docs/auth/pin-based-authorization		$data = array('oauth_callback' => 'oob'); // value is set to "oob" following https://dev.twitter.com/docs/auth/pin-based-authorization

Admin: /* Implementation */

2014-05-10T19:13:08Z

Implementation

@@ Line 27: / Line 27: @@
 Probably PHP, because I haven't dealt with POST and GET in Python yet and this is a bit of a one-shot thing.
-Via http://stackoverflow.com/questions/5647461/how-do-i-send-a-post-request-with-php:
+Here's a simple script to send a POST message with PHP, via http://stackoverflow.com/questions/5647461/how-do-i-send-a-post-request-with-php:
-<pre>
+<source lang="php">
 $url = 'http://server.com/path';
 $data = array('key1' => 'value1', 'key2' => 'value2');
@@ Line 45: / Line 46: @@
 var_dump($result);
-</pre>
+?>

Admin: /* Implementation */

2014-05-10T19:07:01Z

Implementation

← Older revision		Revision as of 19:07, 10 May 2014
Line 26:		Line 26:

	Probably PHP, because I haven't dealt with POST and GET in Python yet and this is a bit of a one-shot thing.		Probably PHP, because I haven't dealt with POST and GET in Python yet and this is a bit of a one-shot thing.

			Via http://stackoverflow.com/questions/5647461/how-do-i-send-a-post-request-with-php:

			<pre>
			$url = 'http://server.com/path';
			$data = array('key1' => 'value1', 'key2' => 'value2');

			// use key 'http' even if you send the request to https://...
			$options = array(
			'http' => array(
			'header' => "Content-type: application/x-www-form-urlencoded\r\n",
			'method' => 'POST',
			'content' => http_build_query($data),
			),
			);
			$context = stream_context_create($options);
			$result = file_get_contents($url, false, $context);

			var_dump($result);
			</pre>

Admin: /* Normal Sign-In/Authorization */

2014-05-10T18:50:22Z

Normal Sign-In/Authorization

← Older revision		Revision as of 18:50, 10 May 2014
Line 15:		Line 15:
	Next, Twitter's servers respond to the GET request with a public and private OAuth token.		Next, Twitter's servers respond to the GET request with a public and private OAuth token.

	Now, the app ~~redirects~~ the user ~~(this~~ is the OAuth ~~URL redirection field we left blank when we created our app)~~ to ~~a new~~ URL. This ~~URL contains a~~ public OAuth ~~token in the URL itself, and this public~~ token allows third parties to authorize users via Twitter, without handling their usernames and passwords directly.		Now, the user has a public OAuth token, and the app can redirect the user anywhere it wants, and as long as that public OAuth token is included in the URL, the user is effectively signed in with Twitter.

			Users can either be redirected to <code>api.twitter.com/oauth/authenticate?oauth_token=[OAuth Token Returned By Twitter Goes Here]</code>, or alternatively, to an arbitrary URL like <code>mysite.com/stuff?oauth_token=[...]</code>.

			This public OAuth token allows third parties to authorize users via Twitter, without handling their usernames and passwords directly.

	=Implementation=		=Implementation=

Admin at 17:47, 10 May 2014

2014-05-10T17:47:01Z

← Older revision		Revision as of 17:47, 10 May 2014
Line 1:		Line 1:
	We're going to assume you're setting up a Twitterbot to use a Twitterbot app (as described at the [[~~Twitterbot~~]] page), and that you're going to use The Hard Way to enable authorization between your Twitterbot and your app. This will enable you to authorize an arbitrary number of users with a single app.		We're going to assume you're setting up a Twitterbot to use a Twitterbot app (as described at the [[Twitterbots]] page), and that you're going to use The Hard Way to enable authorization between your Twitterbot and your app. This will enable you to authorize an arbitrary number of users with a single app.

	If you go with The Hard Way, the Twitter account you use to create the app should be your primary Twitter account, or an app that is exclusively for deploying the app. (Side note: while Twitter will normally delete inactive accounts, i.e., accounts that have no tweets, if an account owns an app and has never tweeted, Twitter will still consider this an active account, and will not delete it.)		If you go with The Hard Way, the Twitter account you use to create the app should be your primary Twitter account, or an app that is exclusively for deploying the app. (Side note: while Twitter will normally delete inactive accounts, i.e., accounts that have no tweets, if an account owns an app and has never tweeted, Twitter will still consider this an active account, and will not delete it.)

Admin: Created page with "We're going to assume you're setting up a Twitterbot to use a Twitterbot app (as described at the Twitterbot page), and that you're going to use The Hard Way to enable author..."

2014-05-10T17:46:49Z

Created page with "We're going to assume you're setting up a Twitterbot to use a Twitterbot app (as described at the Twitterbot page), and that you're going to use The Hard Way to enable author..."

New page

We're going to assume you're setting up a Twitterbot to use a Twitterbot app (as described at the [[Twitterbot]] page), and that you're going to use The Hard Way to enable authorization between your Twitterbot and your app. This will enable you to authorize an arbitrary number of users with a single app.

If you go with The Hard Way, the Twitter account you use to create the app should be your primary Twitter account, or an app that is exclusively for deploying the app. (Side note: while Twitter will normally delete inactive accounts, i.e., accounts that have no tweets, if an account owns an app and has never tweeted, Twitter will still consider this an active account, and will not delete it.)

Assuming you've created your app, you now need to modify it to enable it to authorize Twitter users other than the Twitter user who created the app. I'm following this article https://dev.twitter.com/docs/auth/pin-based-authorization for PIN-based authentication.

=Process Breakdown=

==Normal Sign-In/Authorization==

A normal sign-in or user authorization procedure follows these basic steps:

First, we send a POST request to Twitter servers containing a request for OAuth tokens.

Next, Twitter's servers respond to the GET request with a public and private OAuth token.

Now, the app redirects the user (this is the OAuth URL redirection field we left blank when we created our app) to a new URL. This URL contains a public OAuth token in the URL itself, and this public token allows third parties to authorize users via Twitter, without handling their usernames and passwords directly.

=Implementation=

Using either Python or PHP...

Probably PHP, because I haven't dealt with POST and GET in Python yet and this is a bit of a one-shot thing.