0.2.41 - cloud 403 fixed on audit-blocked OrcaSlicer builds

Fixed cloud print failing with HTTP 403 and an empty camera feed on OrcaSlicer builds that block the plugin from its own config file (reported from an A1 on Windows 11, OrcaSlicer 2.5.0-alpha).

When OrcaSlicer's plugin audit denies the installer all access to obn.conf, the client_name rewrite and the log_to_file default were skipped, so a stale client_name = OpenBambooNetworking made the cloud answer 403 on print registration and on the camera mint, with no obn.log to diagnose it.

The installer now applies block_cloud, log_to_file and client_name through the library in a single call that runs outside the audit hook: prints work without hand-editing obn.conf, and obn.log exists for the next report. A config created fresh at install time also gets log_to_file = 1. Explicit user values are never touched, and older libraries keep the previous behavior.

Libraries rebuilt from open-bamboo-networking 85c2b52 on all three platforms.

0.2.40 - H2D cloud print fixed (auto PoP retry on 403)

Fixed cloud print failing with error -3120 on H2D printers (issue #6 and the OrcaCloud comments): POST /v1/user-service/my/task answered HTTP 403 to the bearer-only request on every region, and the mytask_pop = auto default only attached the proof-of-possession header pair on the CN cloud.

The plugin now retries that call once with the pair attached whenever the first attempt comes back 403, so H2D printers print without any config edit. Explicit mytask_pop = 1 / 0 in obn.conf still win on the first attempt, and every printer that worked before sends the exact same first request.

Libraries rebuilt from open-bamboo-networking 8979ec3 on all three platforms.

0.2.39 - compliance disclaimer, ClusterM-only credit

Compliance disclaimer added (issue #7): README and OrcaCloud page now say the bundled library embeds credentials that are not yours and that you alone are responsible for ensuring your use complies with the applicable terms and law. That warning previously existed only in the upstream fork readme.

extract_key_from_dump.py is now credited to ClusterM/open-bamboo-networking and its contributors, at the script author's request that he not be named or linked.

0.2.38 - attribution and AGPL licensing fixes (issue #7)

• Attribution and licensing corrections after issue #7: the README, OrcaCloud page, and plugin description now state up front that this plugin is an installer around ClusterM/open-bamboo-networking, link sponsors for the upstream author, and credit mitchcapper for extract_key_from_dump.py.
• Dropped the "clean room" claims. The bundled library embeds a Bambu Lab application client secret to auto-fetch signing certificates, so it is not a clean-room implementation and is no longer described as one.
• Every package (plugin zip and all three wheels) now ships the full AGPL-3.0 license text (LICENSE.AGPL) plus a NOTICE naming the upstream projects, the AGPL-3.0 terms that cover the bundled binaries, and the exact source revision they are built from. The repository license badge now reads GPL v3 (installer) / AGPL v3 (native libs).

0.2.37 - 2026-10-19

• Linux installs now honor XDG_CONFIG_HOME when locating the OrcaSlicer data directory (issue #5). On Flatpak builds OrcaSlicer reads its config from ~/.var/app/<app-id>/config/OrcaSlicer, while the installer hardcoded ~/.config/OrcaSlicer, so every library copy landed in a directory the slicer never loads from.
• The "run OrcaSlicer as administrator" install hint now only appears on Windows; Linux and macOS get a folder-permissions message instead.

v0.2.37 - Flatpak/XDG install path + Linux error wording

0.2.37 - 2026-10-19

• Linux installs honor XDG_CONFIG_HOME (issue #5): on Flatpak builds the libraries now target ~/.var/app/com.orcaslicer.OrcaSlicer/config/OrcaSlicer/plugins, the directory OrcaSlicer actually loads from, instead of the hardcoded ~/.config/OrcaSlicer.
• The "run OrcaSlicer as administrator" hint is now Windows-only; Linux/macOS installs report a folder-permission problem instead.

v0.2.36 - audit-blocked obn.conf access reported instead of silent skip

0.2.36 - 2026-10-18

• Clearer installer feedback: when OrcaSlicer's plugin permission system blocks the obn.conf access, the install message now says so and gives the one-line manual fix, instead of the client_name rewrite being skipped silently while prints keep answering HTTP 403. If you see that message, allow the permission prompt OrcaSlicer shows for the plugin (or set client_name = BambuStudio in obn.conf yourself), restart, and print again.

v0.2.35 - cloud print 403 fix (stale client_name)

0.2.35 - 2026-10-17

• Fixed cloud print failing silently with HTTP 403 (The client does not have access rights to the content.) on installs whose obn.conf came from a pre-0.2.28 plugin. Those configs still contain client_name = OpenBambooNetworking, which Bambu's cloud rejects on the print endpoint while every other call works, so the printer receives nothing and no error reaches the slicer. The installer now rewrites that stale line to client_name = BambuStudio. Update, then press Install / Update Open Bamboo Library once and restart.

v0.2.34 - working Copy Path button + obn.log by default

0.2.34 - 2026-10-16

• Fixed the Copy Path button on the plugin tab doing nothing. It is clickable right away now, refreshes the status itself if the path was not loaded yet, and always shows you the path even when the clipboard is unavailable.
• The installer now enables diagnostic file logging by default (log_to_file = 1 in obn.conf), so the obn.log file bug reports need actually gets created. The plugin tab also shows the exact obn.log location. An explicit log_to_file line you wrote yourself is left untouched.
• No networking library changes; the native binaries are the same as 0.2.33.

v0.2.33 - leaf derived platform identity

0.2.33 - 2026-10-12

• Fixed HTTP 403 on the remote camera request and, when the proof-of-possession headers are attached, on cloud print registration, on macOS and Linux, with nothing to configure. The plugin now reads the platform from the signing certificate it actually holds and reports that, instead of the host operating system. The certificate the bundled library fetches is the Windows one on every operating system, so macOS and Linux clients used to present a Windows certificate next to their own platform header, and Bambu's cloud rejects that combination.
• The cloud_os_type key from 0.2.32 stays as an override. It only matters now if you placed your own certificate by hand.
• Networking libraries updated on all three platforms, rebuilt from open-bamboo-networking da9d91f.

0.2.32 - 2026-10-12

v0.2.32 - cloud_os_type platform identity

0.2.32 - 2026-10-12

• New optional cloud_os_type key in obn.conf (windows, linux or macos). It fixes HTTP 403 on the remote camera request and, when the proof-of-possession headers are attached, on cloud print registration, on macOS and Linux: the bundled library requests the Windows signing certificate on every operating system while the request header reported your host system, and Bambu's cloud rejects that combination. Leave the key empty to keep the current behavior, Windows hosts are unaffected either way. After changing it, restart the slicer and upload the print again, the identity has to stay the same from upload through dispatch. LAN connections do not use it. Contribution from prateek, merged upstream as a7ba1a3.
• Networking libraries updated on all three platforms, rebuilt from open-bamboo-networking a7ba1a3.