I know people have talked about this in the past, but now seems like an important time for some practical brainstorming here. Hypothetical: the recent $15mm Series A funding of Vicarious by Good Ventures and Founders Fund sets off a wave of $450mm in funded AGI projects of approximately the same scope, over the next ten years. Let's estimate a third of that goes to paying for man-years of actual, low-level, basic AGI capabilities research. That's about 1500 man-years. Anything which can show something resembling progress can easily secure another few hundred man-years to continue making progress.
Now, if this scenario comes to pass, it seems like one of the worst-case scenarios -- if AGI is possible today, that's a lot of highly incentivized, funded research to make it happen, without strong safety incentives. It seems to depend on VCs realizing the high potential impact of an AGI project, and of the companies having access to good researchers.
The Hacker News thread suggests that some people (VCs included) probably already realize the high potential impact, without much consideration for safety:
...I think this exactly the sort of innovation timeline real venture capitalists should be considering - funding real R&D that could have a revolutionary impact even if the odds are against it.
The company to get all of this right will be the first two trillion dollar company.
Is there any way to reverse this trend in public perception? Is there any way to reduce the number of capable researchers? Are there any other angles of attack for this problem?
I'll admit to being very scared.
Gwern responded to my comment in his Moore's Law thread. I don't know why he responded over there instead of over here but I decided that it was more organized to relocate the conversation to the comment it is about so I put my response to him here.
Do you have evidence one way or the other of what proportion of programmers get the existential risk posed by AGI? In any case, I don't know how to tell whether you're too pessimistic or whether I am too optimistic here.
researches for figures for this project
There are between 1,200,000 and 1,450,000 programmers depending on whether you want to count web people (who have been lumped together) in the USA according to the 2010 US Bureau of Labor Statistics. That's not the entire world but getting the American programmers on board would be major progress and researching the figures for all 200 countries in the world is outside the scope of this comment, so I will stick to that for right now.
LessWrong has over 13,000 users and over 10,000,000 visits. It isn't clear what percentage of the American programmer population has been exposed to AI and existential risk this way (and a bit over half the visits are from Americans) but since LessWrong has lots of programmers and has eight times as many visits as there are programmers in America, it's possible that a majority of American programmers have at least heard of existential risk or SI. This is just the beginning though because LessWrong is growing pretty fast and it could grow even faster if I (or someone) were to get involved in web marketing such as improving the SEO or improving the site's presentation (I may do both of these, though I want to address the risk of endless September first and I'm letting that one cool off for a while, at Luke's advice, so that people don't explode because I made too many meta threads).
I don't see any research on what percentage of programmers believe that AI poses significant risks... I doubt there is any right now, but maybe you know of some?
In either case, if someone might create a method of getting through to them that is testable and works, then this is not a straight up "x percent of relevant programmers get it" sort of problem. Teachers and sales people do that for a living, so it's not like there isn't a whole bunch of knowledge about how to get through to people that could be used. Eliezer is very successful at certain super important teaching skills that would be necessary to do this. For instance, the sequences are rapidly gaining popularity, and he's highly regarded by a lot of people who have read them. Whether or not readers understand everything they read is questionable, but that he is able to build rapport and motivate people to learn is pretty well supported. In addition to that, I became a sales person for a while after the IT bubble burst and was pretty good at it. I would be completely willing to assist in attempting to figure out a way of using consultative / question selling techniques (these work without using dark tactics by encouraging a person to consider each aspect of a decision and provide necessary information for all the choices required for their final decision) to convince programmers that AI poses existential risks.
I think this is worth formally researching. If, say, 50% of American programmers already know about it and get it, which is possible considering the figures above, then my idea is still plausible and it's just a matter of organizing them. If not, Eliezer or somebody (me maybe?) can figure out a method of convincing programmers and test it, then we'd know there was a viable solution. Then it's just a matter of having a way to scale it to the rest of the programmer population -- but that's what the field of marketing is for, so it's not like there's a need to despair there.
That would mean getting the word out to programmers around the world. This wouldn't be a trivial effort, but if they were getting it, and most American programmers had been convinced, it would be a worthwhile effort, and this would make it worth investing in. Considering that programmers are well off pretty much everywhere and that technology oriented folks tend to want internet access, communicating a message to all the programmers in the world probably is not anywhere near as hard as it would at first seem. Especially since LW is already growing so fast and there is a web professional here who is willing to help it grow (me).
You know the people at SI better than I do. Do you think SI would have an interest in finding out what percentage of programmers get it, testing methods of getting through to them, and determining what web marketing strategies work for getting the message out?