Aside

Internet Census

Internet Census - Use of IPv4 Addresses in 24 Hour Period

An anonymous researcher (one person though they use “we” throughout their documentation) has released the results of an extraordinary study. By temporarily constructing a botnet on openly available devices around the world, they were able to map usage of the global internet over IPv4 at a scope and level of detail that has no rival outside of proprietary network operations databases.
Continue reading

One Year in Internet Architecture

On the simple basis of experience, one ought not to hire a graduate student in a humanities/social science/philosophy/etc cultural studies program for technical AND operations work in an internet architecture (or any professional services) firm. But temporary work is the order of the day for academia, and so too for the summers when its laborers are fully, not just effectively, unpaid. So it was at the tail end of a long, frankly brutal summer of odd jobs and the freelance whateverer hustle that a Craigslist ad for office work found an applicant in a tired, frustrated, untrained pseudo-intellectual. The firm hired the applicant to file paperwork and clean up the (four-person) office and get coffee – nothing an intern couldn’t have done, but the summer crop of interns was heading out and the fall crop hadn’t yet arrived, and so hail to the precariat. During the interview, the CEO and co-founder asked about passion, about worldview, about habit, and about (of course) technology. He also asked – and this applicant took it for a trick question – after an entrepreneurial spirit. The answers were forthright but somewhat made up on the spot. But it fit. Continue reading

Lessons, Connections and Directions

The summer now underway, it’s a good time to take stock of gains, setbacks, and lessons learned from the semester. This post simply reviews the three sets of work undertaken over the past few months, and then try to detail the priorities and next steps necessary to continue progress towards the dissertation. Between materials, structures, and approaches, more incommensurability than contiguity prevails – yet weak ties persist in imagination and in theory. Broadly speaking, both epistemological and methodological considerations justify holding all three in concert, as parts of the long-term and focused project. And yet this can only hint at a strategy, it seems, and my largest outstanding challenge will be to find the coherent framework that unifies or at least governs the relationship between each of these schools of thought. Continue reading

Aside

Notes on Migrating WordPress to AWS with Bitnami

Having recently moved several sites, including this one, from GoDaddy to Amazon, I thought I’d share the process that drove me pretty crazy at first. I’m indebted to several other such blog posts whose tutorials pointed the way:

I will assume, for those readers following this post, that you already know how to create an Amazon account, and that you have at least a passing familiarity with (or the ability to look up) Linux command line operations.

The first step is to spin up an Amazon EC2 instance on your account. When you choose your Amazon Machine Image (AMI), you have a huge variety of options, especially for WordPress. I recommend using the 1-click Bitnami WordPress AMI from the AWS Marketplace (I used ami-745af71d for Ubuntu 64-bit – a free, stable release for AWS).

When you launch the instance, you’ll have to assign it a key pair for security. Be sure to save the private key in a safe place, because you only get one shot to download it.

Security Group: SSH by default. Add ports 80 (HTTP), 21 (FTP), and SFTP, and 3306 (MYSQL) access set up.

Assign an Elastic (static) IP address to the instance, so that you can access it from anywhere more easily – but be aware that if you need to shut down the instance, the IP address will release from it, and you’ll have to reassign it. You’ll have to delete or rename bitnami’s IP configuration files (

Open an SSH tunnel to the instance (user: bitnami, key: private key)

Update and upgrade the server if necessary.

Open an FTP connection to the instance (same credentials)

On the old server:

Export your database (including an add-drop tables query) from the old host (This may be through PHPMyAdmin, for example. If you need access to the database, consider installing the WordPress plugin Portable PHPMYAdmin or Database Manager)

Export your WordPress content through the built-in Exporter Tool in WordPress. This will download a specialized XML file.

Copy your wp-content folder in its entirety from the old server via FTP or SCP.

On the new server:

If necessary, install a database management plugin like you did on the old site.

Replace the default bitnami wp-content folder with your backup from the old site via FTP or SCP.

Import your database via PHPmyadmin (or plugin)

Import your content if necessary via the Importer tool (installs like a plugin)

if you have to change file permissions/ownership:

wp-content gets 0775, owner is bitnami, group is daemon.

backup and edit httpd.conf

name of admin, allow override all, include wordpress.conf and virtual hosts.conf

httpd-vhosts.conf

virtual host using name of site, point to wordpress/htdocs document root

backup and edit wordpress.conf

instead of htaccess file

sudo vi /opt/bitnami/apps/wordpress/conf/wordpress.conf

set rewrite mod rules to /wordpress/

 mysql – table wp-options

siteurl and -home to
127.0.0.1/wordpress/

restart apache and mysql

$ sudo /opt/bitnami/ctlscript.sh restart apache
$ sudo /opt/bitnami/ctlscript.sh restart mysql

fix breaks:

front-end settings; just put the two sites side by side.
duplicate content from importer, esp. menus
links: esp. relational vs hard links if domain is changing (incld. directory structure e.g. example.com/blog/ into example.com/)
images: likely bad links if wp-content and db are both imported
plugins: this is the big one esp. if there are server config tweaks necessary. case by case basis.

dns change: a record

point @ to AWS elastic IP
try to keep old one as cname or subdomain a record

backup and edit wp-config.php to name the site

shaboom

Aside

Notes on AWS Migration

Migrating a WordPress blog from GoDaddy to Amazon Web Services Hosting with Bitnami.

Having recently moved several sites, including this one, from GoDaddy to Amazon, I thought I’d share the process. I’m indebted to several other such blog posts whose tutorials pointed the way. (TODO: add links). I will assume, for those readers following this post, that you already know how to create an Amazon account, and that you have at least a passing familiarity with (or the ability to look up) Linux command line operations.

The first step is to spin up an Amazon EC2 instance on your account. When you choose your Amazon Machine Image (AMI), you have a huge variety of options, especially for WordPress. I recommend using the 1-click Bitnami WordPress AMI from the AWS Marketplace (TODO: add link and AMI #) – this is a free, stable release that is well-integrated into (indeed, designed specifically for) WordPress on AWS.

TODO: add screenshot

When you launch the instance, you’ll have to assign it a key pair for security. Be sure to save the private key in a safe place, because you only get one shot to download it.

TODO: add screenshot

Security Group: SSH by default. Add ports 80 (HTTP), 21 (FTP), and SFTP, and 3306 (MYSQL) access set up.

Assign an Elastic (static) IP address to the instance, so that you can access it from anywhere more easily – but be aware that if you need to shut down the instance, the IP address will release from it, and you’ll have to reassign it.

Open an SSH tunnel to the instance (user: bitnami, key: private key)

Open an FTP connection to the instance (same credentials)

TODO: add screenshot

 

TODO: add screenshot

export db (incld add-drop tables) from old
export content (wp exporter)
copy wp-content folder (tarball works well)

replace bitnami wp-content/ with the backup from the old one (ftp) (unzip or tar x*f on the new site)
import db via phpmyadmin (plugin)
import content via importer (plugin)

*delete ipconfig file*

if you have to change file permissions/ownership:
wp-content gets 0775, owner is bitnami, group is daemon.

backup and edit httpd.conf
– name of admin, allow override all, include wordpress.conf and virtual hosts.conf
httpd-vhosts.conf
– virtual host using name of site, point to wordpress/htdocs document root

– create a second virtual host with the temporary name of the site?

backup and edit wordpress.conf
– instead of htaccess file

sudo vi /opt/bitnami/apps/wordpress/conf/wordpress.conf

– set rewrite mod rules to /wordpress/

 

mysql – table wp-options
– siteurl and -home to
– 127.0.0.1/wordpress/

restart apache and mysql

fix breaks:

– front-end settings; just put the two sites side by side.
– duplicate content from importer, esp. menus
– links: esp. relational vs hard links if domain is changing (incld. directory structure e.g. example.com/blog/ into example.com/)
– images: likely bad links if wp-content and db are both imported
– plugins: this is the big one esp. if there are server config tweaks necessary. case by case basis.

dns change: a record
– point @ to AWS elastic IP
– try to keep old one as cname or subdomain a record

backup and edit wp-config.php

– to name the site

shaboom

Internet – Lit Reviews – New Media, Old Media Reader

The essays that comprise this reader forage far and wide for fodder. This review cannot encompass the entire scope of their contributions, but in the same way that the collection provides an introductory overview of many crucial topics in internet (and related media/technology) studies, we can begin with a look at some highlights from the text, and then return later for more in-depth analysis and critique of other selections. Wendy Chun’s introduction to the volume does a more complete and thorough job of this than can a blog post. If we begin with a review of her piece, then, we get a good sense of the state of internet research as far as media studies are concerned. What emerges at the limits of this research, made clear by her analysis of the variations on political-economic, visual-cultural, archaeological, systemic, and aesthetic themes taken up by the contributors, is the mobilization of an opposition between continuity and rupture, in both historical and theoretical terms. In other words, media studies – especially new media studies – is founded on the claim that it can mediate between change and continuity.

Continue reading

Internet – Lit Reviews – Chun, Nakamura, Gitelman

Three writers who focus on the use and rhetoric of media, rather than on their inherent characteristics or their ethical valences, come together here. Wendy H. K. Chun demands that our attention to the social contexts of emergent technologies center on the political matters of force and sovereignty. Lisa Nakamura draws our attention to myriad, and structural, irruptions of old inequalities as manifested in ostensibly transcendent new media. And Lisa Gitelman pointedly reminds us, through a meticulous and engaging historiography, that what we call ‘new’ in media has older histories than we often care to admit, that all media were new once, and that any divergent practice or technology enters a complex set of other, perhaps related, media, in which nothing can be outgrown, only deprecated. Together, these thinkers provide good scholarship on which further research can be modelled, and provocative questions that demand further thought.
Continue reading

Internet – Lit Reviews – McLuhan, Manovitch

Whether one accepts straightforwardly deterministic speculation or not, whether one prefers to think the mind and the collective mind as functions of or factors in computing, we are bound by mediating forces. As the paragons of privileged speculation, Marshall McLuhan and Lev Manovich stand unchallenged as the sources for media and software theory in the United States. Their conceptual frameworks are most contentious when held against certain French thinkers’. McLuhan’s insight that all media contain as a message a prior medium finds a counterpoint in Regis deBray’s analysis of media as overlapping paradigms, rather than linear progressions. Manovich’s later contributions to software theory as a field in its own right takes as a direct target the archaeology of media as expounded by Michel Foucault, whose concentration on print and writing as valid archival data severely limits his historiographic impulses. But taking these two Anglo writers’ work on their own, we can unpack just where they stand, as well as their utility and inspiration for contemporary thought. Continue reading