I don't know if it's just happening on the client side.

Let's see what #[4] explains. 👀

Very useful!!

Hey, you hide me in this video!! 🤣

In relation to this new version:

- how is this user muting works? Is it published to relays in some muted-list, so that it can be reused in other clients?

- did you change something in notifications? It looks as I don't see some posts liked.

Thanks again for your work!!

👏

#[4] has just published a new version of Amethyst with user muting and post reporting, so timely!

I don't know the technical details of the implementation, though.

Deletion is telling the relays and other clients to delete the note.

But there's no guarantee all of them will comply, of course.

An (optional) PIN/biometric to open the app and to show the privkey could be a good addition.

Is this a push for self custodial?

🤔

Bolt12 is a step in that direction.

Maybe to export/show the privkey?

See a detailed explanation in the NIP itself:

https://github.com/nostr-protocol/nips/blob/master/09.md

No hay un grupo (public channel) en #nostr todavía?

Deletion is telling the relays and other clients to delete the note.

But there's no guarantee all of them will comply, of course.

NIP-05 allows to define an alias for a pubkey. It's not verification in any way.

The key is 'the key' (pun intended), not the DNS alias.

Thus, I think that domain owners should not revoke keys.

cc #[2]

NIP-28 Public Chat

So that some discussions happening in Telegram now can move to #nostr.

Some clients support automatic uploads to some service, as Amethyst or Iris.

#nostr

Cc #[6] ?

Try

https://nostr.build/profilepic.php

By #[4]

😉

Cc #[4]

True. As they hide note1 right now.