Skip to content

Recommend separate functions/commands for "uninstall" and "deregister"  #18

Description

@effofexx

To reduce the chances of accidental deregistration and to increase flexibility, I recommend creating separate functions/commands for uninstall and deregister.

Regarding accidental deregistration, the prompts do warn users this will happen but many of them do not pay close enough attention. It's not necessarily intuitive that an uninstallation will result in deregistration imo. I've seen at least one user in the discord who did this while attempting to uninstall the software only, and ended up losing 250 EVR.

Regarding increased flexibility, separating the two functions could allow users to attempt to fix an installation without needing to complete a full transfer installation.

We've also seen several cases where deregistration failed during uninstallation. This means in order to receive the rebate, users need to go through the whole process of reinstalling Evernode, and then attempt to uninstall again. Ideally a user could have the option to deregister when the host is not active at all.

Recommended Implementation:

  • Executing a deregister command would trigger uninstallation at the same time (no need for the SW if you're not registered)
  • Executing the uninstall command would provide the option of deregistration, but not required
  • Deregistration should be possible without a fully functional & active installation of Evernode

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions