Yes and hopefully it takes awhile before malware makes it onto my system too.

Except the messages that are already deleted in Signal. I have a system. It works. Moving on.

Why not use Amber to store my bitcoin? If it is so secure? Well, because maybe at some point the device itself isn't secure.
I don't care because I use Signal with disappearing messages. If/When my device gets hacked, hopefully the hack left some trace or strange behavior that I pick up on. If it doesn't then it was probability very sophisticated. Most zero days leave traces.

I am not 100% sure if it leaked. All I know is something 'liked' a post in Amethyst that I did not recognize doing myself. And Amber was acting super buggy on my phone. It would pop up every time I try to use it. It was a huge pain just to post that my nsec got leaked. Then I wiped my phone for good measure. Amber is asynchronous so everything is a callback. I still use it, but I also swap out my nsec for fresh for privacy too. So at this point, I don't care if I loose my nsec. The PM messages would be nice to use but I don't use PMs for obvious reasons. I only use marmot or signal.

I have a hardware signer. I never use it. I have Amber, yet my nsec somehow leaked. I blamed Amber, but who knows with these things.

Except my key point: if I loose my nsec. Almost nobody in the bitcoin community fully trusts their nsec / seed phrase except in hardware wallets. We are constantly told to keep our seeds offline. Marmot solves this for PMs.

Yes and I use disappearing messages too. So whatever...

I assume it copies it directly from what exists in storage on my phone. If true then your statement assumes the implemented solution assumes actual perfect forward secrecy. I mean, if it was truly perfect forward secrecy than I couldn't write the messages down on paper as I get them and share with a friend.

Which explains why it doesn't exist in Amethyst. Marmot is an upgrade from Signal to make it decentralized. Signal has a feature (perfect forward secrecy). The way they work around that is linking a device from the main account, and offering to copy historical messages to the linked device. If the feature you want doesn't exist in Signal, it probably will never exist in marmot. Of course don't quote me on anything. I am barely a spectator in this space. I have just been burned by Signal's centralization so I prefer marmot.

... and see the same chat history.

So you are calling the feature a bug.

In marmot MLS this is a feature.

It wouldn't work unless White Noise supported adding users to an existing group. Pika supports this today, White Noise tomorrow. That isn't a problem with the protocol. The issue is with nuance between implementation details.

This is in white noise with two users and one chatbot