it now triggers an auth request after the matching filtered filter is returned, and even still it also adds the filtered ... oh i need to revise that too

unauthed reqs containing directory events also open subscriptions ... this may not be wise, perhaps i should change that so it doesn't do that actually

haha... so currently v1.2.9 version will still open a subscription to the unmodified filters in the request... the old events won't be returned but the incoming ones that match would be. closing this now with v1.2.10 

 just clarifying... unauthed requests containing directory kinds are processed, then after returning the results auth request is sent, which the client is free to ignore, and no subscription is created out of these requests, if the filter was modified it was because it wasn't authed so it just returns without starting a subscription on the filter