Avatar
Vitor Pamplona
460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c
Nostr's Chief Android Officer - Amethyst Social

Yes, that is very likely to happen.

However, privacy is not a binary thing. There are benefits to hiding most of your stuff while accepting that leaks will happen here and there.

That's why we designed the new DM protocol in such a way that even if the user re-broadcasts the outer or the inner event, it would still not leak any message or metadata information.

Because rebroadcasts will happen.

It's an idea that comes and goes. Hopefully with the new simplified NIP-65 with an inbox marker for private relays like that people start to publish relays that can actually support it.

I really want a paid relay that accepts everything but authenticates users to download events and you can only download if it has a p-Tag to the authenticated user.

In that way, when people send GiftWrap messages to that relay, my user is the only one that can download those messages from the relay. No one else can "watch" and count how many private likes, private zaps or messages I have.

FYI, I I am not sure if you noticed, but we are changing the JSON encoding to a bytearray concat for the gift card and the seal.

More info on this PR ( I have to update the nip24 pr)

https://github.com/nostr-protocol/nips/pull/716

Is anyone using Amethyst on a large tablet? If so how do you envision the app using the screen space? Are there any Tablet native apps out there worth taking a look?

As long as the Iris version doesn't allow anyone with your keys to change it, it should be fine. The thing you want to avoid is to tell all your friends the iris address IS you and then your keys leak and the attacker not only gets your keys but also your NIP-05. All your friends will think they are talking to you. Not only because it comes from your PubKey, but also from a valid NIP-05.

Ideally the password that allows changing the NIP05 is completely unrelated to your keys, managed completely separately.

No, NIP-05 exists to prove an npub has some control over a domain name. If the Jeff Bezos key has a jeff@amazon.com and we know that 'amazon.com' is not owned by a random scammer, we can say that this is the real Jeff.

However the way people currently use NIP-05 with these random domain names is not effective at all. If I have vitor@plebs.com and you don't trust plebs.com have my id verified, the nip 05 is just useless.

No, the goal is not to verify if a user is real. That's for NIP-05 to do. The shield is to deal with **impersonation of the people you follow**. You marked a PubKey as a contact by following it. Clients should tell you when you are talking to the PubKey you marked or to somebody else that has the same picture and name.

The shield is placed partially outside the image where users can't draw. They could use a 20% smaller image with the shield but that will be visibly off to app users.

The goal of the shield is to fight impersonation of the people you follow. We shouldn't mix it with a similar symbol for those who follow you.

Otherwise, an attacker can follow you to create just enough trust for you to think you are talking to the real Jack.

Replying to Avatar L

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

Sorry to be so demanding but is it doable?

(Not really sorry 😜)

Possible through a DataVending Machine for a small amount of sats per call.

Too easy to fake. I can just create an image with the circle in it and pretend to be somebody else.