Search Results: "ag"

8 November 2006

Dirk Eddelbuettel: RQuantLib 0.2.5

The new version 0.3.14 of QuantLib was released yesterday (and I prepared Debian packages for QuantLib itself, the QuantLib-SWIG Python and Ruby wrappers, the QuantLib Reference Manual (pdf format) and the QuantLib Reference Manual (html format) last night). On the same release day, Dominick and I also updated the RQuantLib package. As a result, a new version 0.2.5 has now been uploaded to both R's master CRAN host and Debian. Only minor API updates were needed. It may take a day or two for the Debian packages to start to migrate over the mirror network. The shared library package once again introduces what is technically a new package (as the release version is encoded in the name) and we have to wait for it to be approved by the ftp masters. In the meantime, the sources are of course also here.

Erich Schubert: Kiss or diss launched.

Kiss or Diss logo Kiss or diss, a rather spontaneous project of a few friends of mine and I, has officially launched. It basically works like famous Hot or Not, except we're doing video, have a much better user interface and are also trendier. Hot or not is so... web 1.0 :-) You get to see girls and boys (choice is up to you) trying to impress you (or more likely making fool of themselves). To continue to the next video, vote on them. Really simple, but quite addictive because of the contents. There are lots of videos with people dancing. There are some pretty good singers inbetween. If you don't filter out males, you'll occassionally get some nice guitar playing... There is a certain amount of Ajax in it already, more web 2.0 goodness to come. Tags and such. Ajax is quite useful here, because you can comment or share a video without the page reloading - and thus the flash movie restarting. Definitely a plus in user experience. And since you need flash, your browser should have javascript anyway. There is no way we'll do a Lynx version with aalib, sorry. :-) P.S. Not all of these videos are "safe for work". Youtube does delete quite some videos, so they all should be okay (though still maybe "inappropriate"), but YMMV. Don't blame us if you get into trouble for watching videos at work. Do it in your lunch break or so. :-) P.P.S. And don't blame us for wasted hours watching stupid videos, either!

7 November 2006

Evan Prodromou: 16 Brumaire CCXV

I'm sitting in the keynote for the Web 2.0 Conference and realizing that it's been far too long since I made an entry on my blog. It's been a huge week for me since I last posted. Whew. OK, so, I think I'm caught up. There's probably a lot of stuff that I missed, but I don't feel like I have to fill in any more. The next 3 days at Web 2.0 are going to be busy, so I really want to be able to blog without guilt. tags:

Aigars Mahinovs: Im blue!

Me and a Blue Man
In the last day of Lastguru’s visit, I convinced him to go to The Blue Man group performance in the New London Theatre. The performance was just great - a combination of rhythmic music, dramatic light and a hilarious comedy show. Just wonderful!
There was a lot of classic Blue Man moments - weird looks, colour-splashing drums, rock concert movements, textual and emotional sketches with the audience and the great “You Are LATE!” intermission. It really was 100 minutes of pure fun.
And best of all, on the exit I was given a special ticket with which I can get back in again for free if I bring a friend - yay!

Clint Adams: Go home, Canadians

For everyone wanting the TN1 visa, here is the secret, he proclaimed. When they ask if you have ever been in trouble with the police, just say No . Also, if your bags weigh more than fifty pounds, tell the flight attendant she is cute, even if she isn't, he continued. And that she looks strong? she asked.

Andreas Barth: Second day: Release planing

Today started with finishing the list of open issues for Etch, and trying to add time expectations to the list. This sounds like an easy task at first glance, but actually it involves asking many people, and getting time expectations updated etc. As result of that list, and some further discussions, I started drafting the next release update mail. One also is hinted to many issue which escaped attention so far, so it involved also a round of bug severity changing. Also, I finished working on "how does apt behave with more than one signature" for now: There is http://testmirror.turmzimmer.net/debian which has an additional signature on the sarge Release-file (thanks to Netcologne for hosting) - please feel free to just use it for any sarge system, and report errors back. I'll revisit the experiences in two weeks time. The rest of day involved smaller issues, e.g. fixing the sort-by-bugnumber-mode on bts.turmzimmer.net (which I broke with yesterdays changes for "related" bugs), and a couple of other things. I also started to update the etch-release-page, but that needs to be continued tomorrow it seems. After I saw some more people not too happy with apache2.2 configuration changes (or rather, some modules are no longer there automatically), I decided to dedicate this Thursday to Apache.

Julien Danjou: The man who did not know he had an amd64

On sunday, I was looking around at the /proc/cpuinfo on one of my last server. I saw that this Pentium 4 had a lot more of cpu flags that the one on my workstation. I discovered the nx flags and its purpose some days before, but I did not know what the lm flags was for... Oh my god, that's the 64 bits support. This box is an amd64 and it was installed as an i386. That's like using a knife to kill a kitten when you have an axe! So, even if the box was 800 km away from me, I decided to reinstall it from scratch, with the help of a serial cable connected on it. That was so easy. I just love Debian for such things. In the end, I'm happy, even if everyone is wondering why I killed a server during 10 hours just because it's better.

Ian Murdock: del.icio.us, fully integrated with browser bookmarks

Yahoo quietly released the del.icio.us Bookmarks Firefox extension the other day, which does something I’ve been wanting del.icio.us to do for a very long time, namely fully integrate with Firefox bookmarks. Like a lot of people, I gave up long ago on using bookmarks to keep track of interesting sites (del.icio.us fills that role quite nicely for me now). Still, the process of bookmarking something in del.icio.us had always been a bit tedious. The old del.icio.us extension helped a little (it would prefill the Notes field with whatever text was currently selected), but it was still missing some pretty important functionality (the popup didn’t display your existing bookmarks like the bookmarklet did). And even with del.icio.us, I still used browser bookmarks for quick access to the sites I frequent most via the bookmarks toolbar. The new extension integrates with browser bookmarks almost perfectly—with a few big exceptions. It’s easy to import your existing bookmarks (the extension even offers to give them a special tag and mark them “private” so as not to clutter your existing bookmarks, as well as mines existing tags to try to categorize what’s imported automatically). The tag button is much more functional now and offers to show your existing tags, my big complaint about the previous extension. And the new extension nicely replaces the bookmarks toolbar and allows you to specify and even order your favorite tags, effectively replacing the last useful vestiges of browser bookmarks with a del.icio.us backed equivalent that also allows you to give other tags to those bookmarks. That said, there are some pretty significant problems with the new extension, the biggest in my view being that there’s no way to change the sort order of the bookmarks within your favorite tags. Essentially, this makes the bookmarks toolbar far less useful—selecting “apps”, which used to contain a manually sorted list of web applications I frequently use, now contains a list of bookmarks in seemingly random order (it’s actually reverse chronological, but that’s not particularly useful for the bookmarks toolbar). The tags submenu under bookmarks doesn’t have any hierarchy to it—all tags are at the top level, making getting to a tag later in the alphabet quite tedious (I’d rather see a “tags starting with a”, “tags starting with b”, etc. structure). And, at least in my early experimentation, synchronization doesn’t always work as expected—changes to my local bookmarks seem to propagate back to del.icio.us, but the reverse doesn’t always seem to be true. Still, it’s a promising start, and I’m going to keep using it. If they don’t fix the sort problem soon, though, I’ll likely revert to Google Browser Sync. (Interestingly, Google Browser Sync is listed as incompatible and is disabled on installation of the del.icio.us extension, even though it technically does other things, like synchronize cookies and passwords. This would seem to be a smart move on Yahoo’s part—challenge Google’s foothold in the browser and create a foothold of its own.) A few parting thoughts: I’ve only installed this extension on my laptop thus far, and it’ll be interesting to see how well synchronization of my bookmarks works across machines (will it synchronize my favorite tags etc., allowing me to maintain a consistent browser toolbar? etc.). Finally, I’d like to see the “tag” function better integrated with the browser, perhaps the way Flock does it (a Google like star next to the address bar that reflects the current site’s del.icio.us state).

Adam Rosi-Kessel: Minor Voting Irregularities

We are fortunate in Massachusetts to have fairly simple paper ballot voting machines (rather than electronic touch-screen voting machines, see, e.g. Ed Felten’s comprehensive critiques of electronic voting). When I voted this morning, however, the machines were not feeding the ballots. Instead, the poll workers were piling the ballots up on top of the machines, apparently to be fed into the machines when they figured out how to get them to work. When I left (about 90 minutes after the polls opened), they had gotten to the point of triple-checking whether the machine was plugged in. I felt a bit uneasy leaving my secret ballot in a big open pile. It was somewhat reassuring that a police officer seemed to be in charge of watching the ballots, but I still will always have a slight reservation as to whether or not my vote was actually counted. Don’t they get to work early to test the machines? Perhaps do a few dry runs, kick the tires, etc.? Other industries seem to have figured out most of these problems a long time ago — for example, I can’t remember a single instance in my entire life of encountering a paper jam (cash or receipt) with an ATM. (I’m sure it does happen, just rarely enough that it’s never effected me). If a system is mission critical, it should be possible to get the failure rate down to something more acceptable.

Steve Langasek: alpha day

As a matter of principle, I try to avoid any conflict of interest between my release manager and alpha porter hats, by e.g. deferring to my co-RM when there's a question of whether a particular compromise should be made to benefit alpha's releasability. Where Dunc Tank is concerned, that means some changes in priorities for bugs to work on, since I'm being paid to try to get etch out in a timely manner, not to keep the alpha port afloat. OTOH, alpha is not the only arch that produces RC bugs needing release team attention, and Dunc Tank only dictates how I spend 40-50 hours of my week -- which means another 20-30 hours a week of Debian work that I can set my own priorities for, right? So the theme ingredient over the weekend was: problems on the alpha port. I'll give myself 4/5 points for presentation, 5/5 points for use of the theme ingredient, and 6/10 points for taste (this plastic computer case needs more salt). And of course, waiting for Debian kernel packages to compile on an LX164 alpha gives one time to do other things too, like following through on the RC bugs that the BTS has wrong version-tracking information for, and preparing an NMU here and there. Less than 200 RC bugs left now, and dropping daily!

Erich Schubert: The power of userContent.css

All mozilla-based browsers have a feature called "userContent.css". It was designed to allow you to override page CSS with your own, e.g. for accessibility reasons. It has mostly been used by people to remove ads, and I'll share two examples with you. Create ~/.gnome2/epiphany/mozilla/epiphany/chrome/userContent.css (you'll probably need to create the chrome directory, too; other browsers use similar path names) and put these two rules in there:
a[href$=".pdf"]:after  font-size: 10px; color: red; content: " [PDF]"; 
iframe[src*="devart.adbureau.net"]  display:none !important; height: 0;  
@-moz-document domain("mail.google.com")   button#ac_tr   color: red !important;   button#ac_dl   color: red !important;    
The first one will postfix a red [pdf] to any link going to a PDF file. This is very valueable especially with Google scholar. The second rule is an example on how to hide elements. This example hides some ads on deviantart. You can easily pick a wider term or grab some of the existing rulesets. The third rule will color the ">deviantart. You can easily pick a wider term or grab some of the existing rulesets. The third rule will color the ">deviantart. You can easily pick a wider term or grab some of the existing rulesets. The third rule will color the "delete" button in Gmail red, so you find it easier. Since it moves around (UI hazard; "delete forever" replaces "archive" button in spam and trash folders.) this is quite nice to have. But if you want to go for default ads filtering, I'd suggest to use some of the adblock extensions. These userContent tricks are mostly useful for adding rules that the extension didn't catch.

Andreas Barth: testbed for secure apt

I was allowed to add an additional vhost to debian.netcologne.de to try out secure apt signature issues. There is now available deb http://testmirror.turmzimmer.net/debian sarge main - the only difference to the real host is an additional signature on http://testmirror.turmzimmer.net/debian/dists/sarge/Release.gpg. Please feel free to try out that host as mirror for your sarge-based systems, and report any breakages that happen. The second key I used is the volatile archive key (as that was easy available) - I'll switch one day to the real Stable Release Managers key.

MJ Ray: Flash! Aaah-aaah! He'll destroy every one of us!

Apologies for the lame misquote of the Queen song, but I just couldn't resist it... (Steve commented: "Great film, and great song! I'm going to go find my soundtrack album now!" and Luis Villa added: "Anyone who likes that particular Queen owes it to themselves to check out the Kleptones Night at the Hip-Hopera, which I think I'm now going to run off and play myself." ) Flash is a bit of a problem for me in two ways:
  1. Free software players don't handle very much of it;
  2. Most Flash file authors make inaccessible rubbish;
It's not really surprising that free software players don't handle much of it, because Macromedia/Adobe have dragged their feet about open support for the format. That makes it a frustrating and difficult reverse-engineering task and most people who are good at reverse-engineering seem to concentrate on hardware drivers so far, which is A Good Thing in my opinion. On 7 November, Alex Hudson reported that Adobe make Flash scripting Free Software with Mozilla Foundation [FSFE Discussion via GMANE] - will this improve things? Ross Burton commented:
"The Adobe donation to Mozilla is just an EcmaScript 4 VM, which is a common language used by JavaScript, VBScript and whatever the Flash scripting language is called."

Stefano Zacchiroli: editing latex the vim way

Editing LaTeX, the Vim way Uwe presented latexmk as its way of previewing LaTeX output while editing in Vim. While I don't know latexmk myself, I'm using quite a lot LaTeX recently (my Ph.D. thesis is getting huuuge) and I'm co-maintaining vim-latexsuite in Debian. With vim-latexsuite what he wants can be achieved quite easily too. I keep on editing in Vim and can exploit the following shortcuts (where <Leader> is usually mapped to backslash):
  1. <Leader>ll compile the current LaTeX source, the generated format depends on the value of g:Tex_DefaultTargetFormat (I use dvi, for a reason explained below);
  2. <Leader>lv fire up a viewer for the compiled format, in my case this runs xdvi;
  3. <Leader>ls move the DVI viewer to the point the cursor is currently at in Vim, highlighting (in xdvi) with a rectangle the current paragraph (believe me, this is amazing);
  4. CTRL+Mouse Click (this in xdvi) do the opposite of (3), i.e. move Vim to the point in the LaTeX source file corresponding to where we clicked in xdvi.
I don't really understand why Uwe want to see working previews in PDF format, to me PDF is just the final output. DVI is much better (especially for (3) and (4) above, but also because it takes less time to be generated). Oh, and of course vim-latexsuite is able to do a lot more, like deciding whether LaTeX needs to be run again to fix dangling references, use the quickfix window to jump to compilation error, and so on ... End of the SPAM :-) PS these are my latex-specific vim settings from my ~/.vim/after/ftplugin/tex.vim
setlocal tw=80
setlocal ts=8
setlocal sts=1
setlocal sw=1
setlocal iskeyword+=\\
setlocal makeprg=make
setlocal keywordprg=:help
"setlocal formatoptions+=a
setlocal spell
vmap ,b "zdi\textbf <C-R>z <ESC>
vmap ,e "zdi\emph <C-R>z <ESC>
vmap ,t "zdi\texttt <C-R>z <ESC>
  " Latex-Suite
let g:Tex_CompileRule_dvi = 'latex -interaction=nonstopmode -src-specials $*'
if v:servername != ""
 let g:Tex_ViewRule_dvi = 'xdvi -editor "vim --servername ' . v:servername . ' --remote +\%l \%f"'
endif

Maximilian Attems: linux-2.6 2.6.18 status

2.6.18-4 was uploaded on Sunday and should be soonest available after dinstall run for most archs. The ia64 build failure is fixed in svn thanks to Thiemo Seufer (ths). alpha is waiting for an updated gcc (see patch in #397139). s390 is currently broken by vserver, patch is awaited soon. linux-latest will be updated tomorrow and expect soon a 2.6.18-5, once those issues are cleared.
linux-image-2.6.18-2- is the Debian kernel team stabilized kernel. Please install it and report eventual bugs. If you know a patch from Linus git tree that fixes your problem even better name it. Thanks for your testing!
We had been quite busy to feed stable with patches that fit the Documentation/stable_kernel_rules.txt. Goodies like Xen, drm-i965 or ahci backport are shared with Fedora Core 6 release. Beyond that for example the r8169 patch series or ccisss support for 2 TB volumes got backported. Out of reach are destabilizing patches like the new 2.6.19 ACPI patches. Further backports are planed for the SUSE reiserfs 2.6.19 patches and vorlon has a fix in the pipe for the vga console driver on alpha.

6 November 2006

Andreas Barth: First day of experiment

Today, I started with the well-known experiment by making sure I'm not dropped out from social security for taking part there. After that was started, I invested some time on a long-standing wishlist bug on bts.turmzimmer.net, so that one can see even the RC-bugs related to a (source) package which would be ignored otherwise if at least one bug would be shown. This required some more code cleanup first. Now everything should work. I started the afternoon with creating a list of open tasks that are not marked as RC bugs, and dependencies between those. During that, I learned that the security teams thinks that we lost the security sparc autobuilder - not something that makes me happy, and something that needs to be fixed independent of Etch. Actually, it seems the autobuilder is just recovering, but I'll continue looking at it. apt-keys One item open on the list of open tasks is the final usage of apt-keys (which involves me in more than one way), so I started a testbed for having the Release-file signed by more than one key, and check whether apt is still happy. Adding another signature turned out to be quite easy with just adding it to the Release.gpg-file. If there is more than one signature on the release-file, but not all keys are know to apt, apt warns, but doesn't stop:
W: There are no public key available for the following key IDs:
010908312D230C5F
If however there is a bad signature, apt fails, even if there is also a good signature. (And please note, if the key is unknown, the signature is not bad but unknown - this gives the interesting behaviour that removing a trusted key by apt-key my remove the need to explicitly confirm to go on with the upgrade.) Summary on apt-keys Current behaviour is ok, we just need to sign one file extra with each stable (point) release, and this can be done with: gpg --no-default-keyring --secret-keyring srm-secring.gpg -b --armor etch/Release >> etch/Release.gpg (or rather, sign off-line, and append on ftp-master). The behaviour with multiple keys might look a bit strange, but IMHO we can live with it. I'm currently preparing to use real keys, and publish the result on some place where anybody could test it (for the latest sarge point release), and I hope we can put it on for the next point release on ftp-master.

Russell Coker: the death penalty

I have just read the news about Saddam finally receiving the death penalty (it did not seem likely that his case would have any other outcome) and have been thinking about the death penalty in general.

Firstly I think that in a jury based system every jury member should have a hand in the execution. If they vote for the death penalty (if you use a jury then it should decide whether the death penalty is acceptable) then they should all be involved in carrying out the sentence. It would be quite easy to fit a room with a dozen switches that control an electric chair. If the jury members are unable to pull the switch then that should result in the sentence being commuted. I am against people voting for actions which they lack the courage to perform themselves.

One problem I have with the death penalty is the poor quality of justice in most courts. The US is a good example of this where poor people are the ones who get the death sentence. A pre-requisite of having penalties such as the death penalty should be that there is a reasonable chance of convicting the person who committed the crime!

In the case of someone like Saddam Hussein there is an additional problem of creating a martyr. I think that a solution to this would be to give him a life sentence and put him on TV on shows based on the Jerry Springer Show. Show him for what he is and let the audience pass judgement on him, I'm sure that he would not do well on such a show.

Another possibility is to have a glass prison where the lights are always on and web-cams show everything he does (including the toilet and shower). That might fall into the category of cruel and unusual punishment, but really the cruel and unusual stuff is what happens in Abu Ghraib (under the command of Saddam Hussein and more recently under the command of George Bush).

Wouter Verhelst: From 2 to 5

One thing about being an m68k porter is that you get to play with hardware a lot. And I mean a lot. Ska, jazz, newwave, and barok had all died during the last few weeks to months; so I was back to two working m68k machines that I could somewhat work with (quickstep, a 25Mhz 040 that I own, and arrakis, a 50Mhz (or so) 060 owned by Ingo Juergensmann). Which was not enough. To make matters worse, arrakis had actually died last week, but that was fixed quickly enough (thanks, Ingo). Which had left me with non-working jazz, barok, ska, and newwave. It isn't the first time that newwave dies on me, and it isn't the first time that a simple power-on again fixes it, after a few weeks of downtime. I can only conclude that this isn't a box which likes being powered on all the time, and that I'll have to leave it powered off for a few weeks every now and then. That's not a big issue, since the machine isn't very high on RAM anyway, so not very useful (apart from testing EMILE on, and other similar things). Barok had died a few weeks ago with a kernel oops that it couldn't even print out entirely. If that sounds like hardware failure, that's because it is hardware failure. Luckily, it's nothing too bad; removing the expansion cards one by one and replacing them afterwards revealed that it's the cache RAM which is the culprit. That's good news and bad news at the same time; good, because a Macintosh IIci can work without this cache RAM (it was sold without those things after all; the cache expansion was an option); bad, because it already is the slowest machine I have, and losing the cache doesn't make it speed up. But at least that one works again—if any of you have some IIci cache lying around that you don't need anymore, feel free to send it my way. Jazz had only paniced, like it does every time. It's a Quadra 950, and those have never been very well supported by Debian. I just needed to reboot it, which I forgot about every time I got near it. It's working again now, compiling away at the next EMILE version, which will fix a few bugs and should make it into etch. Or, well, at least it would be, if not for the b0rken debian/rules file, which I will now have to fix, I guess. Not that this isn't anything I can't handle. Leaves Ska, which needs a new hard disk. That's not a big problem, I just need to get around to flinching me one out of the old unused RAID array at the office, low-levelling it, and placing it in ska. Which I have been planning to do for only, eh, three months or so. Whoops.

Barry Hawkins: The missing ingredient in commercial desktop OS options; a package management system

Having spent the better part of two days provisioning my new MacBook Pro’s OS X, Debian, and Windows XP instances, I am keenly aware of how much the Debian distribution’s package management system and its volume of packages have spoiled me. In that two days, the amount of time required to provision Debian was negligible, even though it is configured to completely match my Lifebook’s Debian Sid instance. In fact, the sum total of time to set up Debian, including every application I use, was about 45 minutes of my involvement. Those who know Debian (and Ubuntu, Linspire, Xandros, Mepis, or any other Debian derivative) are coolly nodding their heads, while others are probably thinking I am a lying, biased Linux zealot. It’s no lie; here are the steps I had to take: Compare that to what it takes with either Mac OS X or Windows XP to get all of your applications installed and configured. Even if you don’t know a thing about Linux or even the more technical side of those operating systems, you can tell from the brevity of that set of steps that the Debian setup is remarkably simple. Now, some will already be keying in their comment posts with exclamations of “Hey! There’s DarwinPorts/Fink/Cygwin!” Yeah, each of those is a nice start; however, they pale in comparison. Fink at least has the robust apt/dpkg foundation, but even it has a relatively meager package selection. I am sure I’ll be writing more on life with Fink and DarwinPorts in the near future. I still don’t have half the stuff installed on XP that I plan to use. I get tired just thinking about the installs. 8^)

Biella Coleman: I would rather be a member of the other AAA

I just got back from 4S, which happens to be one of my favorite of the large professional association conferences. Ok, 15 minutes to deliver talk is the equivalent of being treated as canned sardines, and thus totally unpleasant, but I feel like I can go to most any talk and find it relevant or interesting to my own work. I t is certainly more manageable too in terms of size than something like the AAAs which also gives you a paltry 15 minutes to present and worse, the association has been treading in some ethically problematic territory lately, so much so, I would rather throw my money to the other AAA. While in Vancover, my Internet access was near to nothing (I was staying with a friend who I have not seen since the summer of 2002, but alas, thanks to chatting we have been in pretty consistent contact). When I came back I came across some discouraging but not so surprising new news on the AAA and their cowardly decision to fight the FRPAA that would mandate open access for articles derived from federally funded research… The cherry on top of the cake was they dissolved the AnthrSource Steering Committee formed precisely to figure out how to open up access, no less! Alex Golub, a Savage Minds blogger, and a now ex-member of AnthroSource committee has written an excellent roundup of the story (link above) and Peter Suber, also has two very nice summaries, including links to the appropriate documentation. This year since I am curtailing my time on the conference circuit, I decided not to go to the AAA conference because frankly I am totally annoyed with the professional organization. I am usually quite proud to be or at least amused after I tell folks that I am am anthropologists (most react as if I had decided to embark on some real courageous path) but I am quite embarrassed about the association that is supposed to represent my interests and the profession at large. The links on SM point to and flesh out the problems with AAA’s refusal to jump on an exciting opportunity to free up some knowledge but I want to just emphasize three of the most problematic parts of their decision: 1.The most offensive part is that in reality the proposed bill is quite conservative in so far as it only asks for what should already be (a) given. That is, if the government is using tax dollars to fund research, it has every right to demand the fruits of such scholarship is made available to tax payers. Right? Given the neoliberal moment we are in, in which the government is retrehcnhing on all sorts of supports, this bill is admirable and I am afraid that if it does not pass it can be easily used by conservatives to justify future cuts of such funds. And given the very uncontroversial nature of the bill, it is not surprising that so many of the social science and humanities associations did not protest the bill… Anthropology sticks out as a sore sore thumb in fact. 2. The AAAs deployed FUD tactics to justify their position saying that open access would jeopardize peer review… Sigh. That is just so off the mark and the AnthroSource steering committee letter addressed this point well. 3. Many anthropologist know first-hand how appalling access outside of Europe, US, Australia, Japan etc, can be, even for academics and thus, AAA’s lack of support for this is also implicitly sanctions the North South Division that have plagued the field and all of academia so long. And for a field that has often been very thoughtful about these power/knowledge dynamics, it is doubly even more stinging… Is there really such a strong disconnect between the association and discplinary ethical currents?

Next.

Previous.