@sandwich Thanks for the nostr.watch service! I'm wondering if there's any documentation about what constitutes "spam protection" on the relay details page? (Our relay is members-only and thus spam-protected in my opinion.)

Anyone know what happened to the Electrum Cosigner Pool server? Seems to be down entirely now. Also, the last commit on

GitHub

GitHub - spesmilo/cosignerpool: server code for the cosignerpool plugin

server code for the cosignerpool plugin. Contribute to spesmilo/cosignerpool development by creating an account on GitHub.

was 9 years ago, which seems unrealistic for something that has been running in production for that long. 🤔

Signing an open-source manifesto on X (exclusively) is the most ironic and anti-open-source thing I can imagine. We have at least 3 popular open protocols for social media these days. Absolutely no need to use a proprietary, centralized, 100%-not-open-source service for that.

Apparently, this app offers a combined timeline for all of Nostr, Bluesky, and the fediverse:

TechCrunch

Openvibe combines Mastodon, Bluesky and Nostr into one social app | TechCrunch

Ahead of these potential competitors comes Openvibe, a simple aggregator for the open social web.

Should paid relays accept zap receipts, if the pubkey that signed the contained zap request is on the allowlist to post? I think it would make sense. I'm asking, because my Lightning account just received a zap with not a single relay in the list that it could post a receipt to: ["relays", "wss://nostr.wine/", "wss://theforest.nostr1.com/", "wss://filter.nostr.wine/?broadcast=true", "wss://purplepag.es/"]

There is no way to control user devices and the software they run for any of our open protocols, so there's simply no way for server providers to scan E2EE content transmitted via their services. Let them cripple WhatsApp and Signal. Why do you care so much?