Some type of sampling might be interesting, where the chance a message gets displayed in global is inversely related to how much the pubkey posted recently. Will naturally tend to quiet the noisiest bots without blocking completely.
Bots running on nostr are the new microservices
No, metadata is exposed on nostr no matter if you use a VPN or not
Just attempted to create a new GitHub account and was immediately flagged as suspicious. Definitely warming up to the idea of a nostr-based GitHub. These companies have essentially robbed the commons.
I was thinking of ways to hide DM metadata on nostr and was wondering if it might be useful to have a new type of event which simply wraps a kind 4 event in another layer of encryption (let's call it kind 16). This would enable DM forwarding services to exist that obscure sender and receiver.
It could work like this: a user sends a kind 16 to some middleman service where the encrypted content is a kind 4 event intended for some other recipient that would otherwise be sent on the clear. The service opens the "envelope", sees the original event, re-encrypts it and sends along to the intended recipient (possibly with a delay to prevent correlation based on timing). The client then knows to decrypt the message twice in order to display the content to the user.
If enough people use a service like this it would allow everyone to hide in the crowd. It could even be possible to create "message joins" on nostr where several DMs are forwarded simultaneously to make it even harder to match sender and receiver. Or to add additional hops by recursively wrapping kind 4 (so kind 16 can contain either kind 4 or another kind 16).
I'm seeing this as well and not sure why
If the state doesn't consider bitcoin a valid currency that means we can't break any gambling laws using it to place bets
Nice #Amethyst update, looks the audio issue is fixed 🎶
There is VSCodium that has telemetry removed
Is anyone else having their audio killed by #Amethyst? I'm having to reboot my phone to get it back.
Wow, terrible. I thought their service couldn't get much worse.
Massive performance regression in latest #Amethyst, and sometimes videos decide to hijack your audio. Not the best update.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1lrl3r3a86drcx4wnknghfedywduh4yrw5j4xr25md0qx2tq759aq8stqua The unfollow button is acting weird on Amethyst, sometimes it doesn't work at all
Sometimes you may want to follow an account without that information being public. Anyone thought about implementing private follows? Could even just be a client-side thing.
Let's commit random zaps of kindness to welcome newcomers #grownostr
I think there is a bot that scoops these up whenever they're posted in public
Users would then be able to DM back and forth using any combination of random npubs and not leak any meaningful metadata.
I was thinking some about the metadata issues with nip 4 and was wondering if we could use a new nip that builds on nip 4.
We could send DMs as before only the decrypted content would contain proof that it was sent by the owner of a different npub. Clients could then verify this proof and display the message as though it came from that other npub.
Don't post about BTC or monetary topics with hash tags like #grownostr. People use these partly because they want to *escape* the BTC echo chamber.