Nostr Web Client

Yeah, I was considering nym a bitchat app

I still don't see the codes next to usernames, but this prompted me to try nym's nostr logins

nym spammed about 30 permission requests, including a permanent one that I now have to click past every time I get any permission request from any app on the same device

My main device has like 7 of these and my secondary device has 2, such a huge waste of time and energy. I've never been able to find anyone who knows how to remove these permanent permission requests once an app puts them in the queue. Do you know a way?

Reply to this note

Please Login to reply.

Discussion

🇵🇸 whoever loves Digit 4mo ago

This is the third device I've had infected this way, I was able to protect it until now by avoiding the other apps I knew caused this 😮‍💨

🇵🇸 whoever loves Digit 4mo ago

Now the name codes are showing up for me, but that's kinda irrelevant now

Luxas 4mo ago

The many permission requests are due to how it routinely reaches out to nostr relays to save/fetch settings data.

Try hard refresh to see the new changes

🇵🇸 whoever loves Digit 4mo ago

So you don't know a way to remove the permanent one?

🇵🇸 whoever loves Digit 4mo ago

Will take your advice to fix this on my current device by reinstalling my nsec in nos2x-fox, but that still means I have to avoid nym.bar on my other devices and keep it confined to this one. I hope you'll fix the bug that caused it in nym & help raise awareness to get whatever corresponding bug is in nos2x-fox fixed

Luxas 4mo ago

I don’t believe there is a bug caused by nym. I tested the extension on FF and it worked fine.

🇵🇸 whoever loves Digit 4mo ago

Seems like it only happens when apps spam permission requests like what happened with nym

Luxas 4mo ago

It literally doesn’t “spam” the request. If you understand how Nostr works, it makes sense. Every event needs to be signed by you. So, with an instant messenger every message you send must be signed and approved. This is why it’s important to select either always allow or some far longer time frame. That way it doesn’t keep requiring manual approval. But your extension/browser seems cooked and keeps showing the message. Let me know if you still have the issue once you reinstall the extension or maybe Diego can offer some insight.

🇵🇸 whoever loves Digit 4mo ago

"Permanent request" issue did not come back after reinstalling

However, login behavior was similar both times:

1. It requests permission to read my npub, I authorize that forever

2. It starts loading everything

3. It launches tens of permission requests simultaneously

I am glad it let me clear all of them this time instead of keeping one stuck 🤙

🇵🇸 whoever loves Digit 4mo ago

In case it helps, one more odd detail is that the number of actual requests seems way lower than the number of windows opened for requests both times. Can show you if you want