Ghost FTP 0.95.48 — Windows/Linux cloud sign-in and stability (development Preview)

Adds a clear Connect Cloud flow in the desktop Sites workspace for Google Drive, OneDrive, Dropbox and Box: choose provider, authorize in the system browser, then save the resulting account as a Ghost FTP connection.
Existing PKCE/S256 + CSRF state, native loopback redirect and OS-keychain storage are preserved. A valid public OAuth client ID is required: a centrally registered ID when available, or a user-provided public application ID in Advanced setup. Never request a client secret or cloud password in the application.
Saves per-account public OAuth application IDs alongside tokens inside the OS credential store so refresh still uses the correct client ID after a restart; older stored tokens remain readable.
Provides explicit feedback when a cloud provider has no configured application ID, and protects saved accounts from failed-profile cleanup.
Hardens Box pagination against oversized/inconsistent folders, limits credential-sensitive HTTP diagnostics for Box, Google Drive and Shopify; adds focused regression tests.
Windows/Linux only: Android and macOS production features and data remain unchanged except version metadata synchronisation for CI.
Pending: full native CI, real OAuth consent with registered provider apps, refresh after relaunch, token revocation, Secret Service migration with backward compatibility and target-OS visual approval. This work must not be presented as final stable production.

Credential-based provider setup (Windows/Linux)

Guided native-connector forms for Amazon S3/S3-compatible storage, Backblaze B2, Cloudflare R2, Google Cloud Storage, WebDAV and Nextcloud.
Read-only actual provider listing / WebDAV PROPFIND test with finite timeout and generic redacted errors. Saving without verification is explicitly labeled as such for accounts with restricted list permissions.
B2 endpoint and Nextcloud DAV path generation, GCS service-account file picker and OS-keychain password storage; no client-side persistence or made-up OAuth for object stores.
MEGA and Proton Drive offer official external CLI documentation only; not a native filesystem integration. Proton's third-party commercial SDK support remains pending.
Live-provider E2E, credential lifecycle, rate limits, Android/macOS parity and Linux Secret Service migration still require independent validation.