Yesterday, I published an article on some of the rights that you can exercise in software freedom *even if* your upstream has violated the #copyleft license. While their violation *will* limit your options, ∃ many useful activities that you still have rights to pursue.
https://sfconservancy.org/blog/2026/may/17/incomplete-corresponding-source-code-copyleft-agpl/
While recent events inspired this, other situations are similar.
IANAL & TINLA.
#AGPLv3 #SoftwareFreedom #OpenSource #BambuStudio #Bambu3d #GPLv3 #AGPL #GPL #SFC #Bambu #FOSS #licensing #copyright #DMCA

Dealing with Incomplete Copyleft Source That Doesn't Correspond
Years ago, copyleft violations were often a mere misunderstanding; vendors intended to comply but made mistakes. In those “before times”, a simple request and short discussion often led to the complete, Corresponding Source (“CCS”) for the the distributed binary works (or, in the case of network-service copyleft, the deployed systems).





