hospadar
Joined 8 years ago
Joined 8 years ago
Problems like "how do we build better automated surveillance robots? it's so inconvenient to have to actually have a human remotely piloting the kill-bots"
Sure, but why would the billionaires who own the warehouse full of GPUs permit that to happen? There's a ton of better ways capital could be distributed, and the barriers to implementing them seem to be primarily extant rich people, not the lack of super-awesome ai venture capitalists.
I'd guess that stability is concerned with their legal liability, also perhaps they are decent humans who don't want to make a product that is primarily used for harassment (whether they are decent humans or not, I imagine it would affect the bottom line eventually if they develop a really bad rep, or a bunch of politicians and rich people are targeted by deepfake harassment).
[1] https://www.cagoldberglaw.com/states-with-revenge-porn-laws/...
^ a lot of, but not all of those laws seem pretty specific to photographs/videos that were shared with the expectation of privacy and I'm not sure how they would apply to a painting/drawing, and I certainly don't know how the courts would handle deepfakes that are indistinguishable from genuine photographs. I imagine juries might tend to side with the harassed rather than a bully who says "it's not illegal cause it's actually a deepfake but yeah i obviously intended to harass the victim"
"this thing we sell might destroy humanity?!"
"but yeah we're gonna keep making it cause we're making fat stacks from it"
Is the move here just trying to seem like the good guy when you're making a thing that, however much good it might do, is almost certainly going to do a lot of damage as well? I'm not totally anti-ai, but this always smells a little of the wolves guarding the henhouse.
I wonder if this is what it felt like back when we thought everything was going to be nuclear powered? "Guys we made this insane super weapon!! It could totally power your car!! if it leaks it'll destroy all life but hey you only have to fill the tank once every 10 years!!"
It seems pretty logical to assume to me that you'd almost always have fewer ped fatalities if more people were biking instead of driving.
[1] https://www.theguardian.com/commentisfree/2018/mar/08/killer...
That's (probably) good for getting the most important papers to the top, but it also strongly disincentivizes whole categories (often very important paper). Two obvious categories are replication studies and negative results. "I tried it too and it worked for me" "I tried it too and it didn't work" "I tried this cool thing and it had absolutely no effect on how lasers work" could be the result of tons of very hard work and could have really important implications, but you're not likely to make a big splash in high-impact journals with work like that. A well-written negative result can prevent lots of other folks from wasting their own time (and you already spent your time on it so might as well write it up).
The pressure for impactful work also probably contributes to folks juicing the stats or faking results to make their results more exciting (other things certainly contribute to this too like funding and tenure structures). I don't think "don't care about impact" is a solution to the problem because obviously we want the papers that make cool new stuff.
But making regulations is much easier if you’re very wealthy, so you advocate for regulations that keep you wealthy with a very expensive loud voice and that creates a pretty strong feedback cycle.
One way out (seems to me) is chopping the top off the wealth curve and redistributing - it might matter less that poorer folks are getting money and more that extremely wealthy folks have less insanely disproportionate power to make a world that suits only them.
omg switching away from jenkins (in our case to gitlab CI) was a revalation. SO much easier to use. There were a ton of things we were avoiding doing in CI (or at all) that we started doing (easily) once we switched.
> it must work properly, and I don't expect it to be pretty
Too often it really _didn't_ work properly, or the gap between where we were and "working properly" was a mysterious foggy ocean with no clear path.
To be fair, we drove it pretty hard, we had some jobs that ran thousands of tests on big clusters of nodes to validate and deploy huge ETL pipelines, but man it was nice to have that work smoothly with a nice UI that made sense with super-well-documented pipline commands. It did _basically_ work with jenkins, but the experience of troubleshooting problems and adding new features was a constant pain point that really dragged out a lot of work.
For safety stuff, justice-related decision-making, etc I think explainability is critical, but on the other hand for something like "match doodle to controlled vocabulary of shapes" (and tons of other very-simple-for-humans-but-annoyingly-hard-for-computers problems), why not just use the tiny model?
Maybe if we get really good at making ML models we can make models that invent comprehensible algorithms that solve complex problems and can be tweaked by hand. Maybe if we discover that a problem can be reasonably well solved by a very tiny model, that's a good indication that there is in fact a decent algorithm for solving that problem (and it's worth trying to find the human-comprehensible algorithm).
If that's not plunder I don't know what is.