-
@ Joel 🇨🇭
2025-05-07 09:47:05
I have no idea but here are some deeper insights on the log messages:
* **`wss://relay.mostr.pub/[Kind Kind1]blocked: author is missing a kind 0 event`**: This suggests that the relay `relay.mostr.pub` has a policy requiring the author of a Kind 1 event to have first published a Kind 0 event. A Kind 0 event contains the user's profile metadata (name, bio, picture, etc.). So, if someone is trying to post a note on this relay without having set up their profile first, it will be blocked.
* **`wss://relay.primal.net/[Kind Kind1]`**: This is a simple message indicating that a Kind 1 event was sent to the `relay.primal.net` relay. It doesn't explicitly say if it was successful, but the absence of an error message usually implies it was accepted for processing.
* **`wss://gleasonator.dev/relay[Kind Kind1]blocked: policy error`**: This indicates that the relay `gleasonator.dev/relay` rejected a Kind 1 event due to a policy error. The message is quite general, so the exact reason for the block isn't specified. It could be related to content filtering, rate limits, or other rules the relay has in place.
* **`wss://offchain.pub/[Kind Kind7]Policy violated and pubkey is not in our web of trust.`**: This message from `offchain.pub` tells us a few things about a Kind 7 event (which is a user's contact list). Firstly, it violated the relay's policy. Secondly, the relay specifically mentions that the publisher's public key is not in their "web of trust." Some relays implement a web of trust to filter content based on connections between users. If a user isn't connected to anyone the relay trusts, their events might be rejected.
* **`wss://eden.nostr.land/[Kind Kind7]Publish time out`**: This message from `eden.nostr.land` indicates that the attempt to publish a Kind 7 event timed out. This could be due to various reasons, such as network issues between your Coracle client and the relay, or the relay being temporarily overloaded or unresponsive.