Drop PIA and AzireVPN from the supported providers #134
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The six typed providers are inherited from qomui unexamined. Keep criterion, decided for 0.9.2: a userbase that plausibly overlaps this app's, and integration knowledge that still matches the live API. Philosophy enters only as a predictor — people who run a niche Linux VPN manager skew privacy-conscious, so "popular with plausible users" and "independent provider" mostly pick the same set.
Verified against the live endpoints 2026-08-24:
/en/serverstable no longer exists (table-container: 0 matches today), so import is dead end-to-end — the scrape raises before the WireGuard section runs. The WG endpoints still answer (relay list 200 unauthenticated; legacy/wg/key upload answers 400-not-404 to garbage), so the rework drops the OpenVPN scrape and keeps the WG path. Probe details on #32.Dropping removes the typed add-flow entry, not the ability to use the provider: custom config import still covers anything. Under #23's name≠type schema a dropped type can return cheaply if someone wants it.
Deletion of
pia()/azirevpn(), theirSUPPORTED_PROVIDERSentries,resources/configs and gui references lands as its own PR before #23, so the base class covers four providers instead of six.Done across #136 (providers dropped) and #137 (legacy layout gone); #20 closed wontfix. The kept-provider lineup is recorded in the issue body.