8000 Optionally allow Nault to switch representative automatically · Issue #453 · Nault/Nault · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Optionally allow Nault to switch representative automatically #453

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Joohansson opened this issue Jul 25, 2021 · 4 comments
Open

Optionally allow Nault to switch representative automatically #453

Joohansson opened this issue Jul 25, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@Joohansson
Copy link
Member

When an account rep is flagged as bad it's up to the user to go through quite a few steps and select another rep. One way would be to let Nault handle it all automatically but it's too dangerous to remove the "human choice". Another way would be to let Nault randomly select a rep among a list of user-approved reps such as the "Representative Book".

The suggestion is to add a checkbox here: "Automatically switch rep".
image

Alternatively via an app settings:
image

Alt 1:
If an account rep is detected as offline or bad in any way, Nault could look in this list and randomly select a rep that does not have the "avoid" flag. It would then include the rep change in the next SEND or RECEIVE block for the affected account (yes, rep change can be included in any block type). The user would not be bothered at all but the downside is no specific rep change would be visible in the transaction history.

Alt 2:
If an account rep is detected as offline or bad in any way, Nault could pop up a notification that says "A non-recommended rep was detected for account abc: Do you want to switch to xyz?" with two buttons - CANCEL or OK. The suggested account xyz would randomly be selected by Nault from the trusted user list. The user needs to semi-interract to create a CHANGE-block but it will be visible in the transaction history and does not need to make a SEND or RECEIVE like with Alt 1.

If all reps in the user list are bad, Nault would not do anything but will still display the normal warning in the sidebar. Maybe display a notification: "Nault could not find a good rep to automatically switch to from your list, please revise it"

@Joohansson Joohansson added the enhancement New feature or request label Jul 25, 2021
@keerifox
Copy link
Member

#434 has to be done prior if this is to be considered

@mistakia
Copy link

I prefer Alt 2 as of right now as it maintains user control and has less probability of introducing unwanted side effects.

The side-effects of changing a rep outside of change blocks need to be better explored in order to make an informed decision on Alt 1 (could potentially break some RPC calls).

@keerifox
Copy link
Member

it's up to the user to go through quite a few steps and select another rep

all they have to do is press on the "Representative Change Required" and pick/paste a different rep which would be applied to all accounts that require a rep change

any other interrupting calls to action such as popup dialogues would be ineffective and intrusive

automated actions can be dangerous and may delay user transactions due to spam deprioritization

@milahu
Copy link
milahu commented Jan 9, 2024

it's up to the user to go through quite a few steps and select another rep

all they have to do is press on the "Representative Change Required" and pick/paste a different rep

as a nano-noob im like "???"
at least a link to some documentation would be nice
something like How to choose your nano representative

since my wallet is empty, i just use this workaround:
accounts → add new account

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants
0