Skip to content

It may be unclear that tahoe and magic-folder subprocesses are managed by Gridsync #422

@crwood

Description

@crwood

Gridsync aims to provide an interface for easily adding and automatically syncing folders to Tahoe-LAFS storage grids using Magic-Folder. It is not necessary, however, to know anything about Tahoe-LAFS or Magic-Folder in order to use the application (to the extent that, beyond certain error messages, the terms "Tahoe-LAFS" and "Magic-Folder" are absent from the UI). Nevertheless, past user feedback and testing sessions have indicated that there may be situations in which the terms "tahoe" or "magic-folder" become exposed to end users in ways that can cause confusion or concern. On Windows, for example, the Windows Defender firewall may prompt users to allow or deny connections to/from "tahoe.exe" or "magic-folder.exe" without otherwise indicating that such processes belong to or are necessary for Gridsync's operation. A user who is unfamiliar with Gridsync's underlying architecture thus might -- and has in the past -- become alarmed or otherwise confused by dialogs pertaining to processes with unfamiliar names.

In order to help avoid such confusions, it might be preferable to ship certain binaries with names that more clearly express their association with Gridsync -- for example Gridsync-tahoe.exe instead of tahoe.exe and Gridsync-magic-folder.exe instead of magic-folder.exe. Doing so would at least, in the case of the Windows Defender firewall prompts, help to communicate the association between the applications, encouraging users to make more informed decisions about which processes and connections to allow or deny.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions