Live data from Hacker News

Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

github.com

101–110 of 151 posts

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#101
post #37

Earlier quoted context omitted.

Devil's advocate, this output could have unexpected results, making a filter possibly desirable. Browsers do filter by default with safe browsing URL lists for malware, and they gate access to sites with bad certificates. But agreed users should have control, leaving such filters as safe defaults only.

> Browsers do filter by default with safe browsing URL lists for malware Yes, for malware. As in, software created by criminals to damage your computer and/or steal your personal information. That's not even remotely comparable to what StableDiffusion does here. What they do is refuse to generate content you requested, based on opaque criteria that no doubt are ultimately influenced by quasi-religious sentiments reta…

The concept is quite similar to the NSFW filter found on Google and other image searches for many years. Like the “mature” search settings, this filter is active by default but simple to disable.

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#102
post #69
post #38

Earlier quoted context omitted.

If what StableDiffusion did was ask the user something like "The prompt you entered may result in the generation of content some people find objectionable. Are you sure you want to proceed?", then I would buy your argument. As currently implemented (and the implementation took more work than a confirmation prompt would have!), it's an obvious attempt to control, rather than protect, users. They try their best to dres…

They aren’t trying to “control” users, they’re trying to minimize the amount of bad press these AIs get. The approach they took was easier than your suggestion, because their system detects NSFW content on a per output image basis… so it’s easier to output some image (rickroll) rather than put up a prompt or even skip it completely (since they also generate a grid of the resulting images). I should add that it’s also…

Yeah, it's basic survival. Technology is inherently free and driven by porn, but sometimes that can be shocking to those uninitiated, so to "protect the children", restrictions are often placed to avoid alerting the horde and reverse progresses. I think those "enlightened" should construct and share such understanding that these are the actual reasons, so to avoid us all ending up in an actual dystopia where "protections" are enforced stricter than intended.

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#103
post #96
post #87

Earlier quoted context omitted.

Can you elaborate? Would Adobe be painted in a bad light if someone committed a crime using Photoshop? Honestly it just feels weird. I've read the license restrictions and I can't see why they are there out what they're preventing.

Photoshop doesn't have an automatic "Generate image of Obama selling weapons to Putin" function.

But anyone with enough time to learn (or money) can do it anyways without much effort.

(I'm trying to understand the exact difference here.) So it boils down to democratization? That anyone can do it regardless of skills acquired?

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#105
post #84
post #26

Earlier quoted context omitted.

I would say large contributions from non-members generally work rather terribly in open source. If you absolutely have to, - Communicate ahead of time; don't surprise maintainers with sweeping architectural changes or huge features no one wants or would like to review; - Try to break up changes into logical units that can be understood and reviewed independently; - Write useful and detailed commit messages (some bad…

This applies just as much if not more in a closed team setting. Personally I blame juniors that insist on using the git CLI instead of a million visual GUIs to git. They get told just do a git commit, have no idea what they changed so can't produce a meaningful commit message, and because it's the command line good luck getting a visual representation of what you're committing.

> and because it's the command line good luck getting a visual representation of what you're committing

I don't get the point here. I've never met a developer who knew about `git commit` but didn't know about `git diff` (sometimes I pointed out `git diff --cached`).

I don't think you can blame the CLI on this. It's about the lack of proofreading, in my opinion.

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#106
post #95

Earlier quoted context omitted.

Revenge porn, rumors, and defamation are already huge problems in society. Being able to generate such things on demand with AI models will make it significantly worse. https://www.theguardian.com/lifeandstyle/2018/may/07/many-re...

Perhaps, but there comes a point where the technology is out there whether we like it or not. We should criminalize bad uses, not engage in some futile attempt to try to stuff the proverbial cat back in the bag

Don't let perfection be the enemy of good. Anyone with a basic machine shop can modify an AR15 for fully automatic fire, and a bump stock can be fabricated even easier. That doesn't mean we should just give up and make these things legal and easily accessible to everyone.

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#107
post #7

Almost impossible to pinpoint what changed thanks to thousands of lines of completely irrelevant changes and shitty commit messages. It seems the only changeset that might be relevant out of +2,273 -1,531 is the +11 -7 from https://github.com/basujindal/stable-diffusion/pull/103/comm... ? Does it even work?

It looks like the first commit is the important change.

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#108
post #27

For everyone about to comment on the garbage in the commit: It looks like the committer made their changes in the top commit, then merged the updated CompViz StableDiffusion change set on top of it for some reason. That's where the license change, rick astley image, etc come from. And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter. Here's…

> And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter. It goes without saying that the authors of a piece of software have the right to make the software do whatever they want, but that shouldn't stop us from recognizing that AI engineers are starting to act like megalomaniac overseers who consider it part of their mission to steer humanity…

Don’t worry, intentionally warped faces and NSFW filters have like a month, tops

Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM

#109
post #103
post #96

Earlier quoted context omitted.

Photoshop doesn't have an automatic "Generate image of Obama selling weapons to Putin" function.

But anyone with enough time to learn (or money) can do it anyways without much effort. (I'm trying to understand the exact difference here.) So it boils down to democratization? That anyone can do it regardless of skills acquired?

It boils down to who's doing it. An artist in photoshop the artist is responsible. An AI asked to do it likely the people that made the AI is responsible (until AI can think for itself).

Take it out of drawing. If you write a program to control elevators and it breaks the elevators aren't you, the person that wrote the program, responsible? Why would Adobe be responsible for something someone else draws?

Or let's take an easier more close example. If you just made a character generator. Here's one

https://www.numuki.com/game/mii-creator/

And there was a "randomize" button that one out of 100% made a very pornographic image. Who would get the blame? The person that pushed the button or the person that created the project?

Post reply on HN