name: linkyfy
description: Linkyfy is a PySide6 desktop application for LinkedIn automation. It uses Selenium and undetected-chromedriver to launch and control a real browser session, supports persistent browser profile data, and supports authenticated proxy workflows.
snapcraft: PRIVATE
upstream: PRIVATE
upstream-relation: Original developer and publisher
supported-category: none / requesting reviewer guidance
reasoning: Linkyfy currently needs classic confinement because it depends on discovering and launching a real host browser installation rather than only software bundled inside the snap.
In its current architecture, the application:
- detects browser binaries from standard host system locations
- launches and controls an external Chrome/Chromium process through Selenium and undetected-chromedriver
- relies on persistent browser profile/runtime state for automation workflows
- supports authenticated local proxy workflows that are part of normal operation
Because of this, the currently available interfaces under strict confinement are not sufficient for the app in its current design. Supporting strict confinement would require a significant redesign of how browser execution is handled.
I understand that strict confinement is generally preferred over classic.
I’ve reviewed the available interfaces, and the app still requires host browser discovery and host browser process control, so strict confinement is not sufficient in its current form.
Also, I believe this classic request may already have been approved, but uploads for the linkyfy snap are still failing with:
(NEEDS REVIEW) confinement ‘classic’ not allowed
Could someone please confirm whether the classic snap declaration has actually been applied in the store for the snap name linkyfy and for this publisher account?