Michael Dilger

I caved in and took fiatjaf's advice to just blacklist a few relays to deal with those relays proliferating paths.

This is the PR we are following (for technical details): https://github.com/nostr-protocol/nips/pull/1091

nostr:nevent1qqsrg5k0a0ljkz3e3lql9spqvc4rszfpd6c3srcgj7h9alnh4h6q8ycppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09ukszv79

No, I have no opinion. Looks fine to me. I just saw Karnage's comment about the same time I read this issue and thought I'd make the connection.

https://github.com/nostr-protocol/nips/issues/669

Step 1 done. Added the k tag to deletion event.

In reviewing our filters, there are none to which this apply. We either pull deletions in the same filter that pulls feed-related, or we don't have an authorset by which...

Go to Account>Keys and do "Delete This Identity". Wait a bit for it to complete. Then import your private key again. It won't delete your data, your follow lists, etc,...

Nope. We should probably not have such strong danger warning.

It is a URI that is supported on browsers. https://en.wikipedia.org/wiki/Data_URI_scheme