Replies: 1 comment
关于「Guidance for downstream tools on MiniMax H3 Community License Section V.5?」先把变量固定再猜功能 bug:
No replies yet — a minimal repro (version + one command + first error) will get you a maintainer faster than a long essay. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Comfy Org team,
I maintain a small open-source app (MIT, free, Japanese-language) that runs
MiniMax-H3 locally through ComfyUI. It does not bundle or host any weights —
users obtain them from MiniMax directly.
While reviewing the MiniMax H3 Community License I got stuck on Section V.5,
and I would appreciate any guidance, because I think it applies to a lot of
projects built on ComfyUI, not just mine.
The clause reads:
"If you provide or make available to any Third Party a product, service, or
Hosted Service that permits the generation of Outputs using MiniMax H3 ...
you must ... implement, maintain, test, and periodically review reasonable
and proportionate technical and organizational safeguards ... You must
maintain a reasonably accessible mechanism for reporting suspected
violations."
Two sources describe its scope differently:
Hosted Service.
"if you host H3 for others". The Chinese version uses 托管 the same way.
My questions:
built on ComfyUI, or only hosted services?
is any guidance planned for downstream projects on these obligations?
commercial restrictions on bundled nodes and models. I did not find a reply
there — is there a current position I may have missed?
For what it's worth, my own reading was that I could not resolve it, so I set
up a reporting channel and wrote down explicitly what I can and cannot do
(I have no server, so I cannot see or stop what users generate locally).
Happy to share that text if it is useful to anyone.
Thanks for ComfyUI — it is what made this project possible.
All reactions