= 27d567bc2d48d9f40e9ccc20ea370b15)
wgd comments on Value Loading - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (11)
Maybe "value loading" is a term most people here can be expected to know, but I feel like this post would really be improved by ~1 paragraph of introduction explaining what's being accomplished and what the motivation is.
As it is, even the text parts make me feel like I'm trying to decipher an extremely information-dense equation.
It's the first time I've seen the term, and the second it has appeared at all on LessWrong.
It may be more current among "people who are on every mailing list, read every LW post, or are in the Bay Area and have regular conversations with [the SI]" (from its original mention on LW).
It's more an FHI term than a SI/LessWrong term.
It's often called "indirect normativity": a strategy in which instead of directly encoding the goal for an AI (or moral agent), we specify a certain way of "learning what to value/inferring human values" so that the AI can then deduce human values (and then implement it).
Ah, so it means the same thing as "value learning?" For some reason when I read "value loading" I thought of, like, overloading a function :D "I want cake, and that desire is also a carnal lust for BEES!"
What helped me was thinking of it in terms of: "Oh, like 'reading' human preferences as if they were an XML config file that the program loads at runtime."