← Back to context

Comment by abigail95

1 day ago

You must put authorization on your server if you don't want others connecting to it.

While the right of access is not granted by AGPL - it is not reasonable to run a public service with an AGPL client and say you shouldn't be connecting to it.

They are doing a lot of work to create implied consent under CFAA.

If you want to control access you must do something to control access - it must reach a threshold, it cannot just be a public user agent string.

> You must put authorization on your server if you don't want others connecting to it.

Unfortunately, the CFAA doesn't necessarily require that authorization is implemented through technical means, and it definitely doesn't require any authorization to be technically robust.

  • The point is that they distributed AGPL licensed software which legally speaking puts them on very thin ice if they say "actually you're not allowed to modify that software we gave you and explicitly told you you could modify to do whatever you want."

    This is a direct quote from the Affero GPL:

    > When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.

    The thing Bambu is doing is very much against the spirit of the AGPL, which is the license they chose for the Bambu printer software. And the AGPL has such broadly written language it's hard to believe what they are doing complies with the letter.

    • You're certainly allowed to modify the software, but that doesn't necessarily give you the right to connect it to hardware owned by other people. And AGPL does not provide for any right to services -- only a right to use and modify the covered work.

      For example, AGPL doesn't prevent you from being banned from a Mastodon server.

      The key part of the sentence you quoted is "... to the extent such circumvention is effected by exercising rights under this License with respect to the covered work" -- meaning, you can't use anti-circumvention to prevent people from using or modifying the copyrighted code.