-
Notifications
You must be signed in to change notification settings - Fork 573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NIP-01 what is the max length of subscription_id? #240
Comments
Whatever relays want to allow. I was running a relay I wouldn't allow more than 64 characters. |
I only allow 20 characters on mine. If it is larger than that the relay responds with a |
gossip client uses 32 characters, 16 representing the time, 16 being random. I guess we aren't talking to @barkyq 's relay. |
Whoops @mikedilger I will update that :) I just figured that, since it only needs to be unique per websocket connection (on my relay), more than 20 chars was a bit overkill, and that is 20 bytes on every returned event... |
I also just revealed that I do not use |
your right @barkyq they don't have to be 32 characters. I could just use 2 characters and count up from zero. |
It's your call, I will change the |
No, no you're right. No I mean I'm right that you're right. :-) Let's both make the change. |
Sounds good. Thanks for letting me know. |
what is the max length of subscription_id?
is there a limit?
The text was updated successfully, but these errors were encountered: