I had the same issue after last upgrade. Decided to run nostdress from nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 instead.

Reply to this note

Please Login to reply.

Discussion

No replies yet.