HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
AUTOMATIC1111
stable-diffusion-webui
Python2022–2024
AUTOMATIC1111 / stable-diffusion-webui

stable-diffusion-webui

Stable Diffusion web UI

AI & Machine LearningWeb DevelopmentCreative & MediaLearning & Reference
Explore on GitHubRead Hacker News discussions
88Distinct people
98Mentions
1Explicit recommenders
165.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Stable Diffusion web UI

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

For the image generation (or even indexing with the CLIP interrogator) side of things, recommend just installing the AUTOMATIC1111 github repo…

andthenwhat used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month98 dated mentions

Observed mentions: 2022-09-02 18:48:56 UTC to 2024-11-29 02:06:09 UTC.

0510152022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 commentsSep 20222022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 10 mentions; 3 submissions, 7 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 17 mentions; 4 submissions, 13 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsOct 20232023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsNov 2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC12210
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC1037
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC918
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC817
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC17413
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC505
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC606
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC101
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC404
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC615
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC404
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC101
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC211
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC101
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC202
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC404
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC000
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC101
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC000
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC000
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC202
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC000
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC202

What Hacker News says

17 sources
rm999·Jan 25, 2023
It's gotten much easier in the 24 hours because of this binary release of a popular stable diffusion setup+UI: https://github.com/AUTOMATIC1111/stable-diffusion-webui/rele... (you still need a Nvidia GPU) Extract the zip file and run the batch file. Find the cptk (checkpoint) file for a model you want. You can find openjourney here: https://huggingface.co/openjourney/openjourney/tree/main. Add it to the model directory. Then you just need to go to a web browser and you can use the AUTOMATIC1111 webui. More information here: https://github.com/AUTOMATIC1111/stable-diffusion-webui
In OpenJourney: Midjourney, but Open Source
jacooper·Jan 16, 2023
As far as my understanding goes, when a Repo doesn't have a license, it means that the author reserves all copyrights. Now that the original author added a license, any new commits will be under the AGPLv3, and his old commits(assuming he wants to) will also be relicensed to AGPLv3. However, the issue lies with other contributors, ones who committed beforehand, these commits will still be "All rights reserved", and you can't relicense that to AGPLv3 without explicit permission. https://github.com/AUTOMATIC1111/stable-diffusion-webui/grap... If that's true, then anybody modifying the project can be sued later by the old contributors and the license isn't strictly valid.
In Stable-diffusion-webui now licensed under AGPL 3.0
sillysaurusx·Jan 5, 2023
I’ll step in and say no, it’s not problematic to have one of the most productive and legendary hackers in AI to be in firm control of the future of the project that he himself created. It sounds like you’re proposing that someone should create their own fork. That’s always an option, and I encourage everyone to. But what else is the proposal here? Forcibly move the repo? It doesn’t really make sense. It’s funny seeing “the code is a mess” presented as a reason why a repo is problematic. It’s code. We all have strong feelings about code. Everyone has their own way of doing things with different engineering and product tradeoffs. In this case, automatic was right for pumping out features as quickly as possible and getting the first mover advantage. So, concretely, what do you feel should be done? I also feel like people haven’t read the act
Read the rest
ual TOS: > We do not allow sexually themed or suggestive content that serves little or no purpose other than to solicit an erotic or shocking response, particularly where that content is amplified by its placement in profiles or other social contexts. This includes: ...Pornographic content https://docs.github.com/en/site-policy/acceptable-use-polici... There’s a larger issue here, far beyond Automatic and this one repo. Those links clearly were not “little to no purpose other than to solicit an erotic or shocking response.” For reference, here’s the diff that got him unbanned: https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki...
In Automatic1111's GitHub account suspended for "ToS violations" [restored]
dEnigma·Jan 5, 2023
I can't say for sure where they got the data from, but the initial commit of the file, including all the categories, was by them[1]. I'm not even saying a ban was necessary in this case, just that the question is not about someone else implanting data, but the repository owner themselves. Apart from that I certainly wouldn't be surprised if the author had racist intentions in their GitHub activity too. At least when it comes to their Steam activity there are indications that range from dubious to extremely clear racism. First of all there is the "White Only" mod for RimWorld[2], which seems a bit unsavory, but who knows. Then the question of why the "Black Only" mod[3] has an image of a black person with a spear in the African Savannah, whereas the "White Only" one has a group of white people standing happily on a planet in modern clothin
Read the rest
g. (The "Yellow Only" mod[4] has an image of Emperor Taishō) Most condemning in my eyes is the fact that their Steam profile[5] shows that at some point their nickname was "Remember the six gorillion" (click on the little arrow next to their current name to see previous iterations). This is clearly an anti-Semitic, or at least Holocaust-denying reference.[6] [1]https://github.com/AUTOMATIC1111/stable-diffusion-webui/comm... [2]https://steamcommunity.com/sharedfiles/filedetails/?id=15187... [3]https://steamcommunity.com/sharedfiles/filedetails/?id=15188... [4]https://steamcommunity.com/sharedfiles/filedetails/?id=15205... [5]https://steamcommunity.com/id/no-sry [6]https://www.adl.org/resources/hate-symbol/six-gorillion
In Automatic1111's GitHub account suspended for "ToS violations" [restored]

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.