### #Amethyst v0.73.1-alpha: New Private Message & Small Groups Protocol

This is an **alpha** release of the new GiftWrapped DMs. Please do not consider anything to be actually private until we have a **stable** version. This is early and there might be bugs that leak information.

You can activate this mode by clicking on the Incognito icon on the Chat screen. For now, only Amethyst supports this NIP. Thus we recommend only testing with other Amethyst users. Coracle and 0xChat are finishing their implementations in the upcoming days/weeks.

The claims of this new method are:

- Messages are encrypted with a superior XChaCha algorithm to each participant's public key individually.

- Chat participant identities, each message's real date and time, event kinds, and other tags are all hidden from the public.

- Senders and receivers cannot be linked with public information alone.

- Minimal trust in counterparties: Counterparties cannot expose verifiable details of your message, including the metadata, without exposing their entire user and all of their other messages (private key)

- There is no central queue, channel or otherwise converging event id to link or count all messages in the same group.

- There is no moderation role (i.e. no group admins, no invitations or bans)

- There is no chatroom secret that can leak or be mistakenly shared

- Messages can be fully recoverable in any client (that implements NIP-24) with the receiver or the sender's private key

- The protocol's messages can flow through public relays without loss of privacy. Private relays can increase privacy further, but they are not needed.

- The protocol is extensible to make any other event kind fully private (private likes, private reports, private long-form content, etc)

This implementation is very similar to how Slack manages direct DMs to multiple users. If three users are having a conversation and want to add a fourth person, the forth's user will not see the past. This guarantees maximum privacy: only the receivers of a message at the time of writing will ever be able to decrypt it.

In the near future, we will implement Forward Secrecy through:

- Users will be able to opt-in for "Disappearing Messages" that are not recoverable with their private key

- Users will be able to also opt-in to sharing messages with a new key exclusive for DM backup and recovery.

Details:

- Support for NIP-24 Private Messages and Small Groups

- Support for NIP-59 Gift Wraps & Seals

- Support for NIP-44 Versioned Encrypted Payloads

- Support for XChaCha encryption algorithm

- Fix: Loading of Alby's NWC URI

- Fix: Only requests notification permission once.

- Fix: Show reposts and reactions in search

- Fix: Signed byte used for array slice inside the TLV by nostr:npub1xpuz4qerklyck9evtg40wgrthq5rce2mumwuuygnxcg6q02lz9ms275ams

- Fix: Global feed only shows events from Global-active relays by nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h

- Updates Dutch translations by nostr:npub1w4la29u3zv09r6crx5u8yxax0ffxgekzdm2egzjkjckef7xc83fs0ftxcd

Download:

- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.73.1/amethyst-googleplay-universal-v0.73.1.apk)

- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.73.1/amethyst-fdroid-universal-v0.73.1.apk)

Humm.. we haven't changed anything lately (no new versions).

You can try going to Settings/Apps/Amethyst and hitting Force Close to reset the memory use.

Nothing like waking up with a new micro app: Nostr-native URL Shortener. 🚀

nostr:nevent1qqszrzwlzc588vxeuaz48jl575q657e8rl8g64c52sa6xwkch2y9pvqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg80cdlf07j044neu3jt0fscgqym0nrkqkkwkrzl266xf54es6nq7qpsgqqqqqqs3mmku8

Most clients don't have a disk database. And followers can easily get into the GB of information for more visible accounts.

Not even linktr.ee will survive Nostr 😂

Nostree introduces Kind:30303 for Link Lists.

If they accept domain redirection, I can point amethyst.social to them today.

https://nostree.me/npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

ohh, it's a link tree!

What are link lists? 🤔

This will fix that issue. Because the app will use the relay list from the profile you are visiting instead of using your relay list. So, it is guaranteed that you will have something to download.

Then do it, let's see if they go for it.

it's still their choice.

* decide..

Let the users what's good for them or not.

You have no idea what mobile phones can do :)

What about Umbrel?

Do you want to see people actually using their Umbrel to host their data and allow other people to download info directly from the person's main repo?

Seriously, decentralization is better.

And you are ok with being ruled by 5-10 large relays? Your data is their property. They can do whatever they want with your stuff.

Huge no, no to me.

Then let's make sure people can use their nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct effectively.

NIP 65 is not only for relaying.io. It's a great way to disperse all notes into millions of relays.

Self-custody is always better. Harder and costlier, but better.

Let's hope more people deploy single-click relay services. :)

nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c and I re-wrote NIP-65 to make it easier to implement. Amethyst will be moving to the "Gossip model" as soon as we finish this Private DM/Group workstream.

Then we say goodbye to the old infrastructure that centralizes in large relays.

Together with nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 's new relaying.io service, we can finally start claiming a healthier decentralization in Nostr.

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

Always a pleasure working with nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

nostr:nevent1qqsdqxnzhtpnaceqvjt9fmzech8dzezter4mk2wev67rsctfyyk0r6gpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgsrqsqqqqqp6vj7ng