Trolling - Revision history

Alex at 08:35, 11 September 2015

2015-09-11T08:35:54Z

Lilith2: /* Defense from trolling */

2015-08-20T19:59:38Z

‎Defense from trolling

Lilith2: /* Related */

2015-08-20T19:58:09Z

‎Related

Lilith2: /* Destructables */

2015-08-20T19:56:50Z

‎Destructables

Lilith2: /* Inspirational */

2015-08-20T19:56:00Z

‎Inspirational

Lilith2 at 19:54, 20 August 2015

2015-08-20T19:54:22Z

Lilith2: /* Work flow */

2015-08-20T19:53:26Z

‎Work flow

Lilith2: /* Developing bot functionality */

2015-08-20T19:52:11Z

‎Developing bot functionality

Lilith2: /* Developing bot functionality */

2015-08-20T19:50:59Z

‎Developing bot functionality

Lilith2 at 19:47, 20 August 2015

2015-08-20T19:47:06Z

← Older revision		Revision as of 08:35, 11 September 2015
Line 284:		Line 284:
	== References ==		== References ==

−	[[Category:~~Resources~~]]	+	[[Category:How_To]]

@@ Line 15: / Line 15: @@
 * [[Step 2#How_should_you_deal_with_trolls.3F|How to deal with trolls]]
-* The Japanese martial art of aikido affords a framework for understanding argument as harmonization rather than confrontation. Two movements, circling away ("tenkan") and entering in ("irimi"), suggest tactics for arguing with adversaries. The ethical imperative of aikido involves protecting one's adversary from harm, using the least force necessary, and, when possible, transforming aggression into cooperation. And add a dash of [[controlled folly]].
+* The Japanese martial art of aikido affords a framework for understanding argument as harmonization rather than confrontation. Two movements, circling away ("tenkan") and entering in ("irimi"), suggest tactics for arguing with adversaries. The ethical imperative of aikido involves protecting one's adversary from harm, using the least force necessary, and, when possible, transforming aggression into cooperation.
 My response depends. On how busy I am with other things that I enjoy more, on a [[Self-dox|quick profiling scan of the attackers]] ... and sometimes I troll back for the lulz of it. Actually. :D

@@ Line 277: / Line 277: @@
 * [[Step 2#Installing_Bots_Against_Trolls_And_Swarming_Together|Installing Bots Against Trolls And Swarming Together]]
 * [[Psychological warfare]]
 == References ==
 [[Category:Resources]]

@@ Line 19: / Line 19: @@
 My response depends. On how busy I am with other things that I enjoy more, on a [[Self-dox|quick profiling scan of the attackers]] ... and sometimes I troll back for the lulz of it. Actually. :D
-== Destructables ==
+== Subvertising ==
 ''Progressives are quite adept at the critique of this ‘manufacture of consent,’ but we need to learn how to construct dissent ... as well. We need to acknowledge that politics – even our own politics – is about persuasion, and that one of the most effective ways to persuade people, and effect change, is to tap into their dreams. If progressives are going to take politics and power seriously, we need to learn to use spectacle not grudgingly but enthusiastically and free of guilt. We need to make spectacle our own.'' ~ Stephen Duncombe <ref>Destructables http://destructables.org/</ref>.

@@ Line 272: / Line 272: @@
 * Encyclopedia Dramatica encyclopediadramatica[dot]se
 * The Official Internet Butthurt Complaint Form http://www.pophangover.com/4641/the-official-internet-butthurt-complaint-form/
 == Related ==

← Older revision		Revision as of 19:54, 20 August 2015
Line 279:		Line 279:
	== References ==		== References ==

−	[[Category:~~How_To~~]]	+	[[Category:Resources]]

@@ Line 217: / Line 217: @@
 And since I am preparing to make GNU licensed twitter bots that can be run from local machines, and of which the code can be inspected and installed, adapted, and used by other people …
-==== Install and configure git ====
+'''Install and configure git'''
   $ sudo apt-get install git
@@ Line 229: / Line 230: @@
 [[File:Githubsignedup.png|320px|thumb|right]]
-==== Set up a github account ====
+'''Set up a github account'''
 Set up a github account https://help.github.com/articles/signing-up-for-a-new-github-account/ (<em>put username and password in keepassx or other password file or a scrap-of-paper-soon-to-be-lost</em>).
 It is possible to use a credential helper https://help.github.com/articles/caching-your-github-password-in-git so Git will remember my GitHub username and password every time it talks to GitHub. But maybe best is setting up for two-factor authentication https://help.github.com/articles/about-two-factor-authentication and creating a personal access token https://help.github.com/articles/creating-an-access-token-for-command-line-use to use instead of a GitHub password.
-==== Getting started with git ====
+'''Getting started with git'''
 You can get a git project using two main approaches http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository: The first takes an existing project or directory and imports it into Git. The second clones an existing Git repository from another server. There are several ways to clone repositories available on GitHub https://help.github.com/articles/which-remote-url-should-i-use. Cloning with HTTPS is recommended: The https:// clone URLs are available on all repositories, public and private, and work everywhere, even from behind a firewall or proxy. But not when using tor.

@@ Line 57: / Line 57: @@
 With that we have a Twitter user account and a registered application. We can make API calls either as a user or as an application. The <em>API key</em> and <em>API secret</em> to make API calls on behalf of the application, and your <em>access token</em> and <em>access token secret</em> to make API calls on behalf of your user account. For more see "how to get my API key" https://dev.twitter.com/discussions/631.
 Develop bot functionality using what is called "piecemeal growth". For now seek bots with basic functionalities to test what wurks and what not:
-==== Retweeting mined tweets ====
+=== Retweeting mined tweets ===
 The first bot is based on this examplebot https://github.com/dariusk/examplebot with only minor adaptations. It mines public tweets for by you desired gold nuggets and retweets the latest nugget.
@@ Line 97: / Line 96: @@
   :~/twitterbot$ node bot
-==== Retweeting tweets from a twitter/list ====
+=== Retweeting tweets from a twitter/list ===
 This bot retweets the latest tweets from a twitter list timeline.
@@ Line 149: / Line 148: @@
   :~/twitterbot$ node index
-==== Update with media ====
+=== Update with media ===
 On my piecemeal growth path of developing bots for the sake of unserious seriousness (controlled folly), I wanted to regularly promote our “lulzwarfare” product(s) with for commercial settings usual marketing slogans and examples of lulz as eye catching illustration on twitter.
 Of course, none of the twitter libraries on node.js I tried got update_with_media to work. The code ran fine and reported success but the tweets went into some mysterious void. Debuggers! After two days of banging my head, I not only found I wasn’t the only one banging my head, I also found a workaround https://gist.github.com/adaline/7363853 .

@@ Line 63: / Line 63: @@
 The first bot is based on this examplebot https://github.com/dariusk/examplebot with only minor adaptations. It mines public tweets for by you desired gold nuggets and retweets the latest nugget.
-'''Download bot files'''
+'''Download bot files''': Create a directory for your bot. Download the files from here https://github.com/dariusk/examplebot <em>(the download link is on the righthand side in the navbar)</em>. Unzip and extract or copy the files to the directory you created.
 Create a directory for your bot. Download the files from here https://github.com/dariusk/examplebot <em>(the download link is on the righthand side in the navbar)</em>. Unzip and extract or copy the files to the directory you created.
-'''Install dependencies'''
+'''Install dependencies''': Now install a Twitter API library so we can actually make API calls in our twitterbot project. Enters twit https://github.com/ttezel/twit , a Twitter API Client for <em>node</em> that supports both the REST API v1.1 https://dev.twitter.com/docs/api/1.1 & Streaming APIs https://dev.twitter.com/docs/streaming-apis (Note: Proper use and care of the Streaming API https://dev.twitter.com/discussions/14935).
 Now install a Twitter API library so we can actually make API calls in our twitterbot project. Enters twit https://github.com/ttezel/twit , a Twitter API Client for <em>node</em> that supports both the REST API v1.1 https://dev.twitter.com/docs/api/1.1 & Streaming APIs https://dev.twitter.com/docs/streaming-apis (Note: Proper use and care of the Streaming API https://dev.twitter.com/discussions/14935).
 Using a terminal go to the directory with the files and type the <em>npm</em> install command at the '''user prompt''':
   :~/twitterbot$ npm install twit
-'''Configure bot'''
+'''Configure bot''': Open the file config.js and add your <em>API key (previously known as consumer key)</em>, <em>API secret (previously known as consumer secret)</em>, <em>access token</em> and <em>access token secret</em> strings in their respective intended locations instead of the three dots.
 Open the file config.js and add your <em>API key (previously known as consumer key)</em>, <em>API secret (previously known as consumer secret)</em>, <em>access token</em> and <em>access token secret</em> strings in their respective intended locations instead of the three dots.
   module.exports = {
   consumer_key: '...'
@@ Line 97: / Line 94: @@
   setInterval(retweetLatest, 1000 * 60 * 60);
-'''Test bot'''
+'''Test bot''': Start your bot on the prompt in your bot directory (where the bot.js resides):
 Start your bot on the prompt in your bot directory (where the bot.js resides):
   :~/twitterbot$ node bot
@@ Line 104: / Line 100: @@
 This bot retweets the latest tweets from a twitter list timeline.
-'''Download bot files'''
+'''Download bot files''': Create a directory for your bot. Download the files from here https://github.com/dariusk/dariusbots <em>(the download link is on the righthand side in the navbar)</em>. Unzip and extract or copy the files to the directory you created.
 Create a directory for your bot. Download the files from here https://github.com/dariusk/dariusbots <em>(the download link is on the righthand side in the navbar)</em>. Unzip and extract or copy the files to the directory you created.
-'''Install dependencies'''
+'''Install dependencies''': Next is installing a Twitter API library so we can actually make API calls in our twitterbot project. Enters twit https://github.com/ttezel/twit , a Twitter API Client for <em>node</em> that supports both the REST API v1.1 https://dev.twitter.com/docs/api/1.1 & Streaming APIs https://dev.twitter.com/docs/streaming-apis (Note: Proper use and care of the Streaming API https://dev.twitter.com/discussions/14935).
 Next is installing a Twitter API library so we can actually make API calls in our twitterbot project. Enters twit https://github.com/ttezel/twit , a Twitter API Client for <em>node</em> that supports both the REST API v1.1 https://dev.twitter.com/docs/api/1.1 & Streaming APIs https://dev.twitter.com/docs/streaming-apis (Note: Proper use and care of the Streaming API https://dev.twitter.com/discussions/14935).
 This bot has a number of other dependencies, of which one is grunt http://gruntjs.com/. The grunt file that is in the download is helpful for installing all necessary libraries in node-modules. Using a terminal go to the directory with the files and type the <em>npm</em> install command at the '''user prompt''':
   :~/twitterbot$ npm install
-'''Configure bot'''
+'''Configure bot''': Open the file config.js and add your <em>API key (previously known as consumer key)</em>, <em>API secret (previously known as consumer secret)</em>, <em>access token</em> and <em>access token secret</em> strings that you got when you [[#Create_an_access_token|set up for bots using node]], in their respective intended locations instead of the three dots.
 Open the file config.js and add your <em>API key (previously known as consumer key)</em>, <em>API secret (previously known as consumer secret)</em>, <em>access token</em> and <em>access token secret</em> strings that you got when you [[#Create_an_access_token|set up for bots using node]], in their respective intended locations instead of the three dots.
   module.exports = {
   consumer_key: '...'
@@ Line 153: / Line 146: @@
   generate();
-'''Test bot'''
+'''Test bot''': Start your bot on the prompt in your bot directory (where the index.js resides):
 Start your bot on the prompt in your bot directory (where the index.js resides):
   :~/twitterbot$ node index
@@ Line 162: / Line 154: @@
 As a result this bot has an additional file in its top directory, and no dependency on twit, but on request https://github.com/mikeal/request .
-'''Download bot files'''
+'''Download bot files''': Create a directory for your bot. Download the files from here https://github.com/LilithLela/updatewithmediabot . Unzip and extract or copy the files to the directory you created.
 Create a directory for your bot. Download the files from here https://github.com/LilithLela/updatewithmediabot . Unzip and extract or copy the files to the directory you created.
-'''Install dependencies'''
+'''Install dependencies''': Now install a Twitter API library so you can actually make API calls. Enters request https://github.com/mikeal/request , a Simplified HTTP request client.
-Now install a Twitter API library so we can actually make API calls. Enters request https://github.com/mikeal/request , a Simplified HTTP request client.
 Using a terminal go to the directory with the files and type the <em>npm</em> install command at the user prompt:
   :~/twitterbot$ npm install request
-'''Configure bot'''
+'''Configure bot''': Open the <em>bot.js</em> file and add your <em>API key (previously known as consumer key)</em>, <em>API secret (previously known as consumer secret)</em>, <em>(access) token</em> and <em>(access) token secret</em> strings you created when you [[#Create_an_access_token|set up for bots using node]], in their respective intended locations instead of the three dots.
 Open the <em>bot.js</em> file and add your <em>API key (previously known as consumer key)</em>, <em>API secret (previously known as consumer secret)</em>, <em>(access) token</em> and <em>(access) token secret</em> strings you created when you [[#Create_an_access_token|set up for bots using node]], in their respective intended locations instead of the three dots.
   module.exports = {
     consumer_key: '...',
@@ Line 216: / Line 205: @@
   setInterval(produceLulz, 1000 * 60 * 120);
-'''Test bot'''
+'''Test bot''': Start your bot on the prompt in your bot directory:
 Start your bot on the prompt in your bot directory:
   :~/twitterbot$ node bot

@@ Line 25: / Line 25: @@
 For example, The Art & Science of Billboard Improvement http://www.billboardliberation.com/guidebook.html
-=== Using bots to troll on twitter ===
+== Using bots to troll on twitter ==
 [[File:Powerleveling.jpg|480px|thumb|right]]