-
Notifications
You must be signed in to change notification settings - Fork 64
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
dismiss all pending dialog requests #3
Comments
There is a button "forever" but it doesn't prevent a popup-flood the next time around, so I'm not sure what it does. Or maybe the plugin falls victim to my "delete all cookies when I close the browser" setting? |
I think this happened if you didn't already have a permissions object saved and you try to set permissions for new host. just ran into this and making pr now. as far as 'forever' is concerned, you can only have one permission at a time per host it seems. is of you say authorize reading pubkey forever, but then say authorize decrypting messages for 5 min, the later permission will overwrite the former. @fiatjaf would you be interested in me updating permissions to be level specific per host? |
@eskema can you confirm this is fixed for you now? if so should we close this issue? make sure your nos2x extension is updated to 1.5.2 |
I did a quick test, and I still get one dialog popup per message on the first run. |
you using firefox or chrome? works for me on chrome. |
@eskema are you still experiencing this? I haven't had it happen since the fix. |
I haven't been messing with kind-4 so don't really know if it's resolved.. feel free to close this if you think it's resolved, as I don't think i'll use the same method anyway and I should be able to avoid this even if not resolved.. |
It is not resolved. |
right now, everytime there's a
window.nostr.nip04.decrypt
, it opens a dialog and we have to go one by one. It would be better to have an option to act on all requests at once, otherwise, this can be very painful in the future if there's a high number of messages to decrypt.The text was updated successfully, but these errors were encountered: