HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Sygil-Dev
stable-diffusion
AI & Machine Learning2022–2022
Sygil-Dev / stable-diffusion · Archived

stable-diffusion

Discover this repository through its Hacker News conversations.

15Distinct people
20Mentions
0Explicit recommenders
1.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

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

What people are saying

No recommendation phrase was found in the indexed comments.

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:56:55 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 6-hour interval20 dated mentions

Observed mentions: 2022-08-29 01:41:05 UTC to 2022-09-04 20:06:18 UTC.

012342022-08-29 00:00:00 UTC to 2022-08-29 06:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsAug 29, 00:002022-08-29 06:00:00 UTC to 2022-08-29 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-08-29 12:00:00 UTC to 2022-08-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-29 18:00:00 UTC to 2022-08-30 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-08-30 00:00:00 UTC to 2022-08-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-30 06:00:00 UTC to 2022-08-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-30 12:00:00 UTC to 2022-08-30 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-08-30 18:00:00 UTC to 2022-08-31 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-08-31 00:00:00 UTC to 2022-08-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-31 06:00:00 UTC to 2022-08-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-31 12:00:00 UTC to 2022-08-31 18:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-08-31 18:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-09-01 00:00:00 UTC to 2022-09-01 06:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-09-01 06:00:00 UTC to 2022-09-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 1, 06:002022-09-01 12:00:00 UTC to 2022-09-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 18:00:00 UTC to 2022-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-02 00:00:00 UTC to 2022-09-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-02 06:00:00 UTC to 2022-09-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-02 12:00:00 UTC to 2022-09-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-02 18:00:00 UTC to 2022-09-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-03 00:00:00 UTC to 2022-09-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-03 06:00:00 UTC to 2022-09-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-03 12:00:00 UTC to 2022-09-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-03 18:00:00 UTC to 2022-09-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-04 00:00:00 UTC to 2022-09-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-04 06:00:00 UTC to 2022-09-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-04 12:00:00 UTC to 2022-09-04 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-09-04 18:00:00 UTC to 2022-09-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 4, 18:00

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
Aug 29, 00:002022-08-29 00:00:00 UTC2022-08-29 06:00:00 UTC202
Aug 29, 06:002022-08-29 06:00:00 UTC2022-08-29 12:00:00 UTC101
Aug 29, 12:002022-08-29 12:00:00 UTC2022-08-29 18:00:00 UTC000
Aug 29, 18:002022-08-29 18:00:00 UTC2022-08-30 00:00:00 UTC202
Aug 30, 00:002022-08-30 00:00:00 UTC2022-08-30 06:00:00 UTC000
Aug 30, 06:002022-08-30 06:00:00 UTC2022-08-30 12:00:00 UTC000
Aug 30, 12:002022-08-30 12:00:00 UTC2022-08-30 18:00:00 UTC202
Aug 30, 18:002022-08-30 18:00:00 UTC2022-08-31 00:00:00 UTC101
Aug 31, 00:002022-08-31 00:00:00 UTC2022-08-31 06:00:00 UTC000
Aug 31, 06:002022-08-31 06:00:00 UTC2022-08-31 12:00:00 UTC000
Aug 31, 12:002022-08-31 12:00:00 UTC2022-08-31 18:00:00 UTC404
Aug 31, 18:002022-08-31 18:00:00 UTC2022-09-01 00:00:00 UTC303
Sep 1, 00:002022-09-01 00:00:00 UTC2022-09-01 06:00:00 UTC202
Sep 1, 06:002022-09-01 06:00:00 UTC2022-09-01 12:00:00 UTC000
Sep 1, 12:002022-09-01 12:00:00 UTC2022-09-01 18:00:00 UTC000
Sep 1, 18:002022-09-01 18:00:00 UTC2022-09-02 00:00:00 UTC000
Sep 2, 00:002022-09-02 00:00:00 UTC2022-09-02 06:00:00 UTC000
Sep 2, 06:002022-09-02 06:00:00 UTC2022-09-02 12:00:00 UTC000
Sep 2, 12:002022-09-02 12:00:00 UTC2022-09-02 18:00:00 UTC000
Sep 2, 18:002022-09-02 18:00:00 UTC2022-09-03 00:00:00 UTC000
Sep 3, 00:002022-09-03 00:00:00 UTC2022-09-03 06:00:00 UTC000
Sep 3, 06:002022-09-03 06:00:00 UTC2022-09-03 12:00:00 UTC000
Sep 3, 12:002022-09-03 12:00:00 UTC2022-09-03 18:00:00 UTC000
Sep 3, 18:002022-09-03 18:00:00 UTC2022-09-04 00:00:00 UTC000
Sep 4, 00:002022-09-04 00:00:00 UTC2022-09-04 06:00:00 UTC000
Sep 4, 06:002022-09-04 06:00:00 UTC2022-09-04 12:00:00 UTC000
Sep 4, 12:002022-09-04 12:00:00 UTC2022-09-04 18:00:00 UTC202
Sep 4, 18:002022-09-04 18:00:00 UTC2022-09-05 00:00:00 UTC101

What Hacker News says

2 sources
The original license that accounts for most of the code you are concerned with was released with an MIT license. https://github.com/CompVis/stable-diffusion/commit/2ff270f4e... The August 10th update made unenforceable rules about how the pre-trained model can be used or distributed. A new license was added to an entire codebase that was already partially released under the MIT license. So only the new code would have copyright reserved. That alone makes most of your argument a moot point. The actual scripts being used were committed to the repo on August 21st. https://github.com/hlky/stable-diffusion/commit/1d0036cb6644... And these actual scripts being used don't seem to be modified from the ones that were relicensed with the rights reserved. The crux of the situation for me is that at no point during the release of the pre-trained mode
Read the rest
l do the authors claim any sort of copyright on the images produced, if the end user is generating on their own hardware. There's no meaningful way to legally enforce the current CreativeML Open RAIL-M or the previous MIT derived license that creates rules about how the output of the software can be used. That is something that has been confusing me, but I imagine it will get cleared up sooner rather than later. The additional rules are effectively an acceptable use policy. There is no meaningful legal consequence of breaking acceptable use policy. The most that can be done is that an end user will no longer be allowed to used the pre-trained models. Additionally acceptable use policy has to specify a jurisdiction. In the US, breaking acceptable use policy does not amount to violating the CFAA. The actual license seems mostly about a way for there to be no way to hold the authors of the models accountable for any illegal activity done by the end users. Which is completely fair and understandable. This kind of misunderstanding and fear-based approach to reusing code is what holds back progress and seems to be what the authors actively tried to fight by releasing the current repo with a CreativeML Open RAIL-M license. I believe the intent of the authors is as important as the exact text of the repository. Especially since the cited sources for the foundation this was built of off, x-transformers by lucidrains, OpenAI's ADM codebase, and Denoising Diffusion Probabilistic Model, in Pytorch by lucidrains are all licensed with MIT. Most importantly, the restrictive license is based almost completely on the condition that the end user is using their pre-trained model. If the end-user manages to create and uses their own model from scratch, there is no reason for any part of the original repo license to apply.
In Ask HN: For those using Stable Diffusion locally, how do you filter fishy repos?
Look at the "assets" and "scripts" directories. Those contain images and code. Those things were released alongside a LICENSE file. They are now reproduced in the fork you linked, but with the LICENSE file rewritten completely. The original license (Aug. 10) did not grant permission to relicense those scripts. All it said about them was "All rights reserved". The current license, the one added on Aug. 22, does seem grant explicit permission to sublicense and redistribute what it calls the "Complementary Material" (which includes the source code surrounding the model), however, it has a lot of specific provisions, among which are the requirement that the original copyright notice be reproduced. Like I said, in practice this might not be a big deal, but forking a repo whose license starts with "All rights reserved" and which does not explic
Read the rest
itly grant permission to relicense its code, and then rewriting the license file in your fork, should be a huge red flag. As of the Aug. 22 license the fork might be compliant, but I think it would be a lot safer to include a copy of that license in addition to the new GNU license for the forker's changes. And pre-Aug 22, when this fork was made, it was just flat out ignorant to fork and relicense. You can't just delete "All rights reserved" and paste in a GNU license. Look at the license the forker deleted[0]. Literally all it says is "All rights reseved", and then lists a few things you can't do. There's not a single provision that would make it okay to redistribute at all, let alone modify and relicense it. 0. https://github.com/hlky/stable-diffusion/commit/b4c61769dfa1...
In Ask HN: For those using Stable Diffusion locally, how do you filter fishy repos?

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.