Removable-media auto-connect request for seravault-cloudsync

store-requests privileged-interfaces
1

Requesting auto-connection of removable-media for seravault-cloudsync.

CloudSync is a two-way file-sync application: users choose local folders to keep in sync with cloud storage providers (Google Drive, Dropbox, OneDrive, S3, etc.). Users routinely place sync folders on external or secondary drives (USB disks, /mnt, /media, /run/media) rather than under $HOME. The home interface does not cover those mount points, so removable-media is required for the app’s core function — without it, syncing a folder on an external drive fails silently under strict confinement. The app only reads/writes the specific folders the user has explicitly configured for sync; it does not scan removable media broadly.

2

Hello @dguedry,

Would you be willing to consider sticking with manual-connection for the removable-media interface, or is auto-connection heavily preferred?

Thanks!

3

If you don’t mind, auto-connection is heavily preferred. Thanks.

4

Hello @dguedry,

Given the described functionality of the snap, it does not fall cleanly into one of the listed accepted auto-connect use cases for this interface. However, I feel this snap has a solid argument for removable-media access and would like to consider making an exception.

In order to do so, due to the sensitive nature of the access removable-media provides, granting auto-connection requires trust in the snap publisher. If you would like to proceed, please first complete the vetting process described in this forum post and let us know here when the vetting process is complete.

Thank you for your understanding, please let me know if you have any questions.

5

I hear you. I was hoping to avoid the user’s having to open a terminal as this is intended for non-technical users.

  • A list of the snaps that you have, that should have a verified publisher associated with them. This is the first snap we’ve built. We do plan to deploy the seravault.com app to snap.

  • The institution, foundation or company that you are a member of or work for. Seravault, LLC

  • Your role within that institution, foundation or company. Founder

  • The group email address that should be tied to the Verified Account. development@seravault.com

  • The way in which your institution has worked, collaborated or partnered with us. If your institution, foundation or company hasn’t so far, let’s start a conversation. We haven’t. We’re a startup.

6

Verified publisher requests are handled separately and should be posted in the following category: policy-requests - snapcraft.io

Apologies for any confusion. Thank you!