Update PiNozCam listing for the 1.1.0 stable release - #1480
Conversation
Refreshes the description, hardware speed table, and screenshots (Telegram/Discord remote control, OctoPrint interface) for the current 1.1.0 release, narrows the OS list to Linux/macOS (actual support), and points the archive URL at the 1.1.0 tag.
jneilliii
left a comment
There was a problem hiding this comment.
would like @jacopotediosi just to take another look at the pre-built binary part of this solution. also, one question for @foosel about the cloud attribute tagging and any possible concerns from her.
| homepage: https://github.com/DrAlexLiu/OctoPrint-PiNozCam | ||
| source: https://github.com/DrAlexLiu/OctoPrint-PiNozCam | ||
| archive: https://github.com/DrAlexLiu/OctoPrint-PiNozCam/archive/master.zip | ||
| archive: https://github.com/DrAlexLiu/OctoPrint-PiNozCam/archive/refs/tags/1.1.0.zip |
There was a problem hiding this comment.
Good catch, thanks -- reverted to archive/master.zip. master now always mirrors the content of the latest tagged release (that's part of what this same release cycle did), so the branch link stays correct without needing a PR every future version.
|
|
||
| # Developed with the use of Artificial Intelligence. | ||
| attributes: | ||
| - ai-developed |
There was a problem hiding this comment.
not sure if the cloud attribute should have been flagged because of the telegram integration before. but now, with the discord integration as well looking for @foosel to chime in here.
There was a problem hiding this comment.
Given that for any other plugins connecting to either Telegram or Discord we have the cloud tag applied (at least as far as I can see), this should also be applied here.
It is optional, yes, but this is about transparency.
There was a problem hiding this comment.
Makes sense, thanks -- added cloud to the attributes list.
Per @jneilliii's review comment: the registry's own registering guide says the archive URL should always point to the latest release, and recommends using the branch download link with a branching strategy that keeps only the latest release there -- not a pinned version tag that would need a manual PR every future release. master now always mirrors the latest tagged release's content, so archive/master.zip is correct going forward.
foosel
left a comment
There was a problem hiding this comment.
As mentioned in my reply to @jneilliii, needs the cloud tag too.
Optional Telegram/Discord integrations upload camera images and print status to a third party. Consistent with how other plugins connecting to those services are tagged, per transparency norms.
|
Will review ASAP, I'm currently under a heavy refactor of the Telegram plugin but should be available again in a few days... Sorry for the delay |

PiNozCam just cut its first true stable release (1.1.0), so this refreshes
the plugin's listing to match current reality:
README (Telegram/Discord remote control, on-device detection, mask
zones), removing stale references to settings that no longer exist
(Max Failure Count, old sensitivity thresholds).
Raspberry Pi 5/4/CM4, Jetson Orin, and the RK3566/RK3588 NPU boards.
current OctoPrint tab/settings panel (the old screenshots were outdated
PNGs).
osnarrowed tolinux+macos(was previously also listingwindowsandfreebsd, which the plugin has never supported — itships a prebuilt native binary with no Windows/FreeBSD build).
archivenow points at the1.1.0tag instead ofmaster.zip, soinstalls from this listing pull an immutable, released version instead
of whatever happens to be on the default branch at install time.
ai-developedattribute (the plugin was developed with AIassistance) and a
privacypolicylink, per the registrationrequirements.
Front matter validated locally with
.github/scripts/validate_front_matter.py --check-id-match --check-asset-match(404 files, 0 fails).