National Differences in Anthropology Conferences

I’m currently helping to organize the joint conference of the Australian Anthropological Society (AAS) and the Association of Social Anthropologists of Aoteroa New Zealand (ASAA/NZ). I’ve been part of conference organizing before, so I didn’t expect to run into anything too confusing, but even within the English-language anthropology world, there are quite large differences, even if the basic unit of a conference is everywhere the fifteen-minute paper.

Because of funding limitations and my lack of imagination, I’ve only ever attended the largest conferences more than once: AAA, 4S (an STS conference), and SCA (mostly because I was a student board member.) I’ve also been to a CASCA (the Canadian conference) when it was held jointly with AES, a JASCA (the Japanese national conference,) one for the Society for East Asian Anthropology, and a couple smaller ones in Japan.) (The ASAANZ meeting I’m helping to organize will be the first one of these I attend. I’ve never been to a meeting in Europe, South America, Africa, or Asia outside of Japan and Hong Kong.)

Between all of these and the Australian/New Zealand conferences, there are two big (and unexpected to me) differences: panel formats and food.

Panel Formats

AAA, SCA, CASCA, and JASCA, and I’m sure many other conferences tend, to be based on what I’ll call the AAA-style panel. Someone will come up with a proposal for a panel, and find 5 or 6 other people to present papers or be discussants. They will all get their abstracts written by the deadline, and everyone’s contribution goes in as one package, which is also accepted or rejected as one set.

These conferences generally also accept individual paper proposals, in which a paper can be submitted without already being part of a panel. If the paper is accepted, then the organizers will put together a panel consisting of other individual papers.

The relevant characteristic here is that papers are either assessed as one panel, or they are assessed as an individual paper. There is no in-between option. And whereas individual papers go through one round of screening, papers on panels go through two: once when they are accepted by the panel organizer, and another when they panel as a whole is accepted by the conference organizers.

A few years ago, 4S started doing “open panels” which was new to me. For these panels, the conference organizers would invite proposals for panels without any associated paper proposals. Panel proposals would be accepted or rejected, and the organizers with accepted panels would then go out and invite paper proposals, which they would accept or reject.

In this system, the panels are assessed once by the conference organizers, but the rest of the selection work is done by the panel organizers. 4S continues to also accept “closed” panel proposals, which are the same as the AAA style of panel.

I recently learned that in the Australian system, all panels are treated like 4S-style open panels. The conference organizers assess only panel proposals. Panel proposals do not need to have any papers in place, and in fact, the conference rules require panels to be open to public submissions. (Although there seems to be a tacit understanding that some panels will have their roster of paper presenters already fixed.) So there are two deadlines for the AAS-style conference: one for the panels, and the one for all the papers submitted to those panels.

I can see some advantages to this approach. Labor that has to be done by the conference organizers in the AAA model is distributed across dozens of panel organizers in the AAS model.

The AAS model also makes it easier to accept a higher proportion of papers. In the AAA model, a paper on a panel rejected from the conference is gone from that conference. Especially with the way that AAA sets deadlines, a paper on a rejected panel cannot become an individual paper submission. (I have heard of rejected panels being accepted as poster sessions, however.) In the AAS model, some panels will receive a lot of paper submissions and reject some number of papers. But these papers can still survive by being transferred for consideration on other panels that may have received fewer submissions. I haven’t seen relative acceptance rates, but it wouldn’t surprise me if AAS-style conferences had much higher ones.

One question that I can’t answer yet is how this affects the feel, if not the quality of panels. I once presented as part of an open panel at 4S, and it felt like a very scattered grouping of papers that did not lead to much interesting discussion. The quality of AAA panels varies wildly, but for the good ones, it’s clear that somebody has given thought to why this group of people belonged together, and this is usually reflected in the quality of the Q&A and discussion after the papers.

Not having been to an AAS or ASAANZ meeting before, I’m curious about the effect of having all panels as open panels.

Food

At only one conference I’ve attended so far has there been food included in the conference registration fee. This was the SCA meeting held at Cornell University in 2016. At every other conference, it’s only been the finger foods at receptions that have been included. There are always conference dinners, but these cost extra. The printed conference programs usually have good suggestions for nearby restaurants. At AAA, the places to eat in and near the venue are always packed to capacity with anthropologists at lunch and dinner (except for McDonald’s.) I assumed that food was included at the SCA at Cornell because there was nowhere nearby we could go to eat.

If you’re planning to come to Wellington for AAS/ASAANZ in 2020, I have good news for you. Your conference registration fee will include lunch on each day of the conference, plus “morning and afternoon teas.” These are what people back home call coffee breaks. I expect there will be cookies and coffee in addition to “tea.” In fact, a frightening amount of our budget will be used to feed you. Much of your registration fee is going to go straight into your (or someone else’s) stomach.

When I originally started putting the budget together for this conference, I did not include expenses for any meals, but this was quickly corrected. It seems that in Australia, New Zealand, and much of Europe, the conference’s food is part of the experience. In fact, it is, as more than one person told me, the thing that people remember about a conference, more than any talk they hear.

I’ve had good food while at conferences, but rarely from the conference. With any luck, we’ll have something delicious for you if you make the trip to Wellington in December.

Fake Interdisciplinary Collaborations

Lianghao Dai at natureindex (via Ulrike Felt on Twitter):

‘Fake’ interdisciplinary collaborations (IDCs) happen when scientists of various disciplines put their names on a joint project application for an interdisciplinary research project, but no knowledge integration occurs, because they end up working on their individual or mono-disciplinary research separately.

Because an authentic IDC requires continuous investment of time and intellectual input, or in Klein’s3 words “rounds of iterations”, with high risk of no actual output in the near future, the motivation to spend time going really deeply into team collaboration is lacking.

In Japan, people might talk about participation in “fake IDCs” as the tatemae for their research: the collaboration is the outward appearance they need to secure funding, but their actual research aims are different. It’s not uncommon for this to be done in order to get the money to cover basic work expenses (such as computer equipment, software) that are no longer covered by their own universities due to cutbacks.

The Alchemy of Meth

via Nick Shapiro on Twitter.

A new book by Jason Pine.

Meth is almost always within reach. And when it’s ingested, it can make anything else feel within reach. Meth increases energy and alertness. More importantly, it generates anticipatory pleasure. That is, rather than giving the sense of satiation derived from having consumed something good…, meth activates the “seeking system,” creating excitement about good rewards to come. This felt sense of futurity is like hope.

Conveniently, the book is on Jstor.

A personal website for $50 a year

Since I’ve recently redone this website, I thought I’d write quickly about what I used to put it together.

While sites like WordPress.com and SquareSpace can make it extremely easy to put together nice and easily maintained websites, they cost a little more than I am willing to pay.

My aim for my own website has always been to have one for the lowest cost and the greatest flexibility. This is the setup I currently work with.

The Pieces

The platform: WordPress. For this website (and the site for NatureCulture), I now run and install the free, but fully functional, version of WordPress. This gives you access to the most important and useful parts of WordPress without having to subscribe to WordPress.com’s services. The trade-off is that you have to do a lot of hands-on configuration and maintenance yourself.

I’ve been using WordPress for NatureCulture for a while, and have started to appreciate how easy it makes it to manage files and alter the appearance of a website. Because it’s widely used, if something does break, it’s not difficult to find a tutorial or guide online for fixing it.

The hosting service: NearlyFreeSpeech. This is a pay-what-you-use hosting service based in the US that I’ve been using for nearly ten years. Depending on your usage, you might pay only a few dollars a month for hosting. If you’re a technical person, NearlyFreeSpeech gives you a lot of freedom, but there are also a lot of things that you can inadvertently break. Fortunately for me, they seem to know that a lot of people will want to use WordPress with them, so they make it very easy, and provide clear instructions for installing it.

Other bits

WordPress and NearlyFreeSpeech are the main parts, but in addition, there are a few bits of software that are essential.

An SSH client: To use and maintain WordPress takes logging into NFS’s server and manually typing things into a command-line interface. This interface is used to update the WordPress software, as well as its themes and plugins. (WordPress has some web-based tools, but I’ve never been able to get these to work.) To log in, you need software that will connect you to the server using a protocol called SSH. This is just something that let’s you control another computer remotely using text commands. SSH is easily found on MacOS and Windows, and on iOS I use something called Termius.

An FTP Client: On occasion, I need to transfer manually transfer some files to the server, such as if I want to embed something in a page that WordPress doesn’t quite support. For these purposes, you need an FTP client that will easily let you select and transfer files from your computer to the server. I use a free piece of software called CyberDuck.

These pieces let me run fairly complex websites without too much trouble. Also, it’s really cheap.

Cost: The main costs of running a website are for storage space, bandwidth, and domain name registration. In addition, to run something like WordPress, you need a computer somewhere running a database system (to store your blog posts and so on).

The domain name registration (to claim “gjotsuki.net”) runs about $15 US a year. This price is basically the same no matter where you host your website.

The other costs are the ones that vary. If you sign up for a service like WordPress.com (WordPress’s commercial, all-in-one package), then you pay around $3 a month for basic hosting, so $36 US a year. (A domain name is included for the first year.) The downside is you don’t get to customize the appearance of your website very much, and don’t have FTP (or SSH) access to your server, limiting how creative you can be with content. To get those things can cost two or three times as much.

With my own setup on NFS, I pay the same $15 per year for the domain name, but only around $48 for everything else per year. This actually includes the cost of both my personal website, and another website I host for my parents. (For comparison, the website for NatureCulture cost less than $40 to run for all of 2019, including the domain name.)

WordPress is actually quite a heavy piece of software, so if you use something less resource-intensive to run your site, it’s possible to reduce the cost even further. Back in 2012, when my site was much simpler (a few text pages, PDFs, and a couple of images), I paid less than $6 for the entire year, plus $15 for the domain name.

With these basic parts, I get something that matches the service that WordPress charges $34 a month for.

Why WordPress?

This current website is the third version I’ve put online since 2010-ish, when I first decided I should have a personal page. In the beginning, I learned basic CSS, typed all of the pages into a text editor, and uploaded the individual files myself to the server.

The website was only a few megabytes in size, which was mostly PDFs and a few images, so it loaded extremely quickly. But the main reason for me doing things this way was that it was cheap.

The trade-off was that the site was difficult to maintain. Every time I wanted to make a correction or add something new, I had to hand-code everything and re-upload the files. The same had to be done to change the site’s appearance. In addition, I had to manually keep track of the relationships between all of the pages, and make sure all the links worked.

For a set of static pages, this was not too much of a burden, but it wasn’t a system that would work if I wanted to regularly add content. Writing and formatting text in TextEdit with HTML tags was also difficult to read and correct.

Nevertheless, the first version of my page lasted for nearly eight years.

When I finally decided to make a change, I wanted something that would look a little more interesting and let me add content more easily.

I came upon a piece of software called Jekyll. Jekyll is similar to WordPress. It’s geared towards creating sites with frequently updated blogs and supports themes so that a site’s appearance can be customized and changed easily.

But there is an important difference between WordPress and Jekyll. WordPress runs on the remote host, and is accessed through a web browser. Beyond rendering webpages, your local computer does not do anything special. All of the actual work is done on the server. Blog posts are generated remotely as they are requested, and then sent to the web browser.

In contrast, Jekyll is software you run locally, on your own computer. For instance, to post a new blog entry, you type the content into a file on your computer and save it as a text file (following a few formatting conventions.) Then you run the Jekyll program, and it generates an HTML file and adjusts other pages to accommodate the new entry. These files are then uploaded to a server, which just dispenses them as is to visitors’ web browsers. Basically, Jekyll does once on your own computer what WordPress does (in principal) on the remote server every time somebody visits.

I liked Jekyll because it does not use many remote resources, making it quite cheap to run a site, but it is more manageable than directly editing HTML and CSS files. There was also a pretty good selection of themes, so I was able to find something that I liked.

The downside was that Jekyll never quite worked for me as promised. I would type in a page, run the software, and get errors or find the page rendering in ways I didn’t expect. I would try to customize the pages and when I got things looking ok, something else would stop working. I eventually got a site that I was fairly happy with, but I barely touched the site again for more than a year.

In the end, I settled on WordPress. Working on NatureCulture, I had figured out many of its quirks, and I felt comfortable installing and customizing it. The most important part was, even though using WordPress increases the cost of running my site, its design is intuitive enough that I will never forget how to do ordinary things on it. I wouldn’t have to fight WordPress in the way that I fought with Jekyll. A bonus is that WordPress has a very large ecosystem of themes, tutorials, and plugins to choose from, including a capable iOS app, and good traffic stat tools.

So here we are. It’s much easier to do than it sounds. Try it out.