AI Horde’s AGPL3 hordelib receives DMCA take-down from hlky

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • Mergify - Updating dependencies is time-consuming.
  • Sonar - Write Clean Python Code. Always.
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • hordelib

    A wrapper around ComfyUI to allow use by the AI Horde. [UnavailableForLegalReasons - Repository access blocked]

    I find it hard to be sympathetic, personally.

    You don't remove copyright notices when you copy code files from one repo to another.

    This is seemly a clearly vindictive and deliberate action by the OP to remove credit for the files, due to whatever personal history:

    > I would rather not have any mention or contribution of this person in our library, as they go against everything the Free Software movement stands for!

    The GPL FAQ is unambiguous on this point:

  • voltaML-fast-stable-diffusion

    Beautiful Stable Diffusion API and UI with support for AITemplate acceleration

    This kind of drama is just sad.

    I dont know if you are OP, but plenty of other UIs have interrogator code, like

  • Mergify

    Updating dependencies is time-consuming.. Solutions like Dependabot or Renovate update but don't merge dependencies. You need to do it manually while it could be fully automated! Add a Merge Queue to your workflow and stop caring about PR management & merging. Try Mergify for free.

  • clip-interrogator

    Image to prompt with BLIP and CLIP

    It's image -> words, the inverse of stable diffusion.


  • node

    Node.js JavaScript runtime :sparkles::turtle::rocket::sparkles:

    When projects vendor or copy from other projects, license bodies typically include all relevant copyright statements and licenses even if the license body is the same as the parent project.

    NodeJS uses the MIT license [1] and reproduces the license for the MIT-licensed Acorn.

    OP stripped the copyright statement and license attribution without mentioning hlky or the originating project in the license file. OP proceeded to confuse matters by assuming that "AGPL" suffices. It seems like the copyright statement was the offense here.

    A simple email or github issue might have resolved the matter. Given the tenor of the relationship between the OP and hlky it should be no surprise that hlky opted for the "nuclear option"


NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts