Bambu Lab Authorization Control System: Difference between revisions
→Impact on professional users and print farms: Fix line feed character warning |
→The OrcaSlicer-bambulab fork: grammar mistake: ".. made public a fork.." to ".. made a public fork.." |
||
| Line 227: | Line 227: | ||
===The OrcaSlicer-bambulab fork=== | ===The OrcaSlicer-bambulab fork=== | ||
On April 23, 2026, the developer Pawel Jarczak (GitHub user <code>jarczakpawel</code>) made public | On April 23, 2026, the developer Pawel Jarczak (GitHub user <code>jarczakpawel</code>) made a public fork named OrcaSlicer-bambulab at <code>github.com/jarczakpawel/OrcaSlicer-bambulab</code>. The fork restored the ability to send print jobs from OrcaSlicer directly to Bambu Lab printers without routing through Bambu Connect.<ref name="xda-jarczak" /> According to Jarczak's own description, the fork worked by reaching the printer through a Linux-side workflow Bambu Lab had not yet disabled, and was built on publicly available Bambu Studio source code combined with the developer's own integration layer; it did not redistribute Bambu Lab's proprietary networking plugin binaries.<ref name="jarczak-readme" /><ref name="3druck-jarczak">{{Cite web |date=30 Apr 2026 |title=Developer ends OrcaSlicer fork after Bambu Lab threatens legal action |url=https://3druck.com/en/programs/developer-terminates-orcaslicer-fork-after-bambu-lab-threatens-to-sue-32156744/ |url-status=live |access-date=4 May 2026 |website=3Druck.com}}</ref> | ||
===The cease and desist=== | ===The cease and desist=== | ||