There's a similar warning about not using hotel shower heads—advising either not to use them or to bring your own personal shower head to replace it. The reason is rather hard to talk about frankly.

I just eliminated 23 Nostr zombies using #PlebsVsZombies! 🔪🧟‍♂️🧟‍♂️ My Zombie Score™ was 10%! What's yours? 🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟩🟩 Follow and join the hunt at: 🏹 https://plebsvszombies.cc

If we're talking about things we can do at an individual level: 1. There are many things that are illegal but don't actually violate anyone's private property—if you've been in the habit of reporting such things, stop doing that immediately. 2. Encourage tax evasion. 3. Persuade others to join in on points 1 and 2 as well. 4. Advocate for, use, and spread the freedom-enabling technologies that make it easier for others to do these things. 5. Above all, stop voting. 6. Exclude, as much as possible, the voluntary Gestapo who can't be persuaded. In fact, there's one path that's the easiest way to put all of this into practice—one that requires no special effort and is even beneficial to do: save in Bitcoin and pay in Bitcoin.

I used to have this goal of building a sleek Nostr client like yours, so I'd pore over the NIPs. After reading through them multiple times, I came to the conclusion that I should find something else I'm actually good at haha

And this goes without saying, but... it's not just about tagging — the client also needs to look up the inbox relays of every tagged person and publish to those relays as well.

The reason the notification isn't going through is that the problematic note isn't tagging your pubkey. Also, per the Nostr standard spec(NIP), in order to send notifications properly, client is supposed to tag everyone involved — meaning all participants from the root note all the way down to that comment — but it looks like Wisp only tags the pubkey of the immediate parent note.

Most of my NIP-46 issues come from the OS killing my processes. It's never been an issue on Linux, but mobile has been a constant struggle

Just to clarify — this is a general statement; I don't know what this app does.

Right — logging in or signing up is really annoying. For most use cases, an automatically generated private key stored in the browser is enough, provided there's some protection against spam attacks (or the app doesn't need spam protection).