i had added a similar feature that would retain a filter and resume it after auth was confirmed.
most clients retry requests and event publishes after getting an auth demand.
so i have left out that part but the code is still there to enable it.
it's just that if the client doesn't expect this, your relay ends up doubling up subscriptions.
i understand why semisol did this, and i tried it as well, but it's not in the spec. it's a reasonable expectation based on protocol theory but it's not in the spec.
did i mention, that it's not in the spec?
so, idk, semisol can keep doing this and i can enable it in my relay implementation with a few uncomments or something equally easy. but i don't think it is a good idea. the expectation of repeating a request or submission of event should be on the client.
the end.
