You're asking the right question.

Did nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z also blackmail you, threatening to doxx your sock puppets if you don't pay him 42 sats?

Reply to this note

Please Login to reply.

Discussion

Simple: average number of pubkeys registered with each Push Notification token (a device)

That's only google universal api? Not FDroid then, excluding Fdroid app users the stats right?

App* not api

Correct. Only for the Google Play version, both APK and app store.

Right cuz the firebase analytics. Got you. Thanks for clarifying

Not even firebase, just regular push notification server.

I see. Cool 🫡 good to know. Can you see the npubs 😅 don't wanna play with wireshark lol

So you can match them? Clearly Google could.

Any push notification server can. You have to get anything that happens with pubkeys x, y and z and send to device tokens 1, 2 and 3.

Couldn't client just register arbitrary id instead of npub with push notification server, and still be able to receive tokens 1 2 3 to correct device. It doesn't need to know npubs, that's anti-privacy (unless im misunderstanding what you both said). Im only using 1 nsec funny part. Just like to think this one through

You need to know which events to listen to on relays and where to send them to. Sending everything to everyone so that you can filter in the app will get you banned :(.

Ahhhhh, I see. Relay filtering per npub REQ of some kind. Hmmm fair enough.

FDroid is always there for those who do want the extra paranoia lolll just checking

So what goes to the push notification server in request. If someone is logged into Amethyst with just 2 nsec at a time, why do we need to receive notifications for the other account we are currently not switched to? Couldn't the push server client call be changed to do 1 nsec at a time. Register itself again when you switch? (Or it is already one at a time, but you just grouped by some unique client metadata to get 10% )

Vitor frennnn, I know you can do it 🦅

https://nostr.build/p/nb7679.mp4

Because it would be weird to not notify the account you are not currently using.. all other apps do all accounts.

Could be on option for users. Like Orbot but.... based on flag register one. And based on flag register one per account login. Default to 2, as in the old world. But give option for 1 in the new world. I tried 🙏

You did it for Orbot proxy. Same config store, except different .kt file is reading it, right nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8?

Can I try it?

I love this developer-talk out in the open. That's why open source protocol is better than platforms! #Nostr

Keep up the great work nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z. 💪

And also everyone who is contributing in some other way!

If you want **your** npub's notifications to your device, you better share them with the notification server.

The only way to avoid this issue is to skip notifications I think.

The app should probably warn the user upon adding a second account and invite him to disable notifications.