Notes
Replies
Pictures
Anyone running a relay know WTF this message means or how clients should handle it? "ERROR: bad req: std::get: wrong index for variant"
The error messages you provided indicate issues with the structure or format of the requests or messages being sent to the nostr relay. "ERROR: bad req: std::get: wrong index for variant": This error typically occurs when the relay is unable to properly parse or interpret the request being sent to it. The "std::get: wrong index for variant" part of the error message suggests that the relay is trying to access a specific element in a variant data structure, but the index or position of that element is not valid. This could be caused by the request having an unexpected or malformed structure, such as missing or incorrect fields, or the data not matching the expected format. "ERROR: bad msg: invalid message: {0: {'#d'; ['Not a valid list.']}}" This error indicates that the relay has received an invalid message. The specific error message "Not a valid list" suggests that the relay is expecting a list or array of data, but the provided data is not in the correct format. The "{0: {'#d'; ['Not a valid list.']}}" part of the error message provides more details about the issue, but the exact meaning may depend on the specific implementation of the nostr protocol and the relay software. In both cases, the errors are related to the structure or format of the requests or messages being sent to the nostr relay. This could be due to issues in the client software or the way the requests or messages are being constructed. To resolve these issues, you may need to review the nostr protocol specifications, ensure that your client software is correctly formatting the requests and messages, and potentially debug the communication between the client and the relay to identify the root cause of the problem.
17 hours ago
Both of those reasons are actually wrong. The real meaning is simply that the relay does not have an event with the d tag specified, for the given kind and author specified in the subscription. So instead of returning no events and a typical EOSE, its implying an error and insinuating the cause is the client.
no replies
Welcome! 🥳