#Amethyst users, should Global filter explicit/sensitive content (NIP-36) by default?

Reasoning: Lots of people don't onboard friends/family members because of porn/NSFW on Global

Pros:

- Cleaner experience

Cons:

- "Algorithms"

O Brasil vai lançar um foguete

Cuba também vai lançar

Brazilians are now discussing if I am a communist or a libertarian to decide if they want to use Amethyst or not.

Should I tell them that I ate a CUBAN sandwich at Bitcoin 2023?

Modifying a Phillips coffee machine to accepts satoshis, updates coming soon and eventually source code #coffeechain #lightning

Running a routing node doesn't make sense for an individual. Even at 1 sat/vbyte it was impossible for me to break even after I had a few force closures. Routing benefits greatly from economies of scale, and most individuals do not have enough capital to compete.

Also currently the lightning network is underutilized and has the potential to grow massively. As it grows every channel will be able to provide more value to the network and thereby its operators.

It's still in a bit of a bootstrap phase since there aren't a lot of places to actually spend sats with lightning yet. Once there's a higher level of adoption and we can start buying coffee or whatever irl with lightning we are going to see an explosion in capacity and the entire landscape will change.

On the new idea, the nostr master key would generate a new key for every device. The user wouldnt be able to export it. When you change phones, people would be forced to rotate their keys for the DMs, not for the rest of nostr. Their profile stays the same, but messages go somewhere else.

If we then add private groups (nostr doesn't have this yet) we could add all device keys in the same "group" so that all your DMs can be seen by all your devices.

I'm new to nostr and the whole decentralized world, so my question might be trivial.

When the time comes to change the device would you lose the network you built? Could you sign up to the new device with the same use name and still be verified?

One issue I see for less developed countries, like Brazil, is that cell phones are stollen all the time. It's not rare cases of people buying a new phone to have it stollen the next month. I device based identification would be very impractical for this scenarios.

You sent them an email explaining the issue.

If a goal is widespread adoption, I suspect this would work against that.

I think what people want is easy messaging but without spam/scam. Not difficult messaging. “Was it on this phone? That phone? Was it on the desktop computer? Which browser? No, must be the tablet. Nope not there either. What the heck happened to that message I want to re-read?!”

What if DMs were device-based?

We could use a secret from the device to create a new private key to use exclusively DMs. Since the new DM key can stay in the device's secure element, there is no way for any other device to access your DMs, even if you keys leak (they will inevitably do).

Pros:

- avoids leaking DMs when the nostr key leaks.

- DMs that expire when the phone expires

Cons:

- users cannot migrate the DM history to a new phone/client

With private group DMs, we could add all device keys in a single DM message so that current devices of a user can read the DM history.

Same thing. Connection is firmer on new computer but it still locks itself up.