Oddbean new post about | logout
 feature is now added... with auth not yet performed, reqs that have kinds out of the list 

	ProfileMetadata 0
	FollowList 3
	EventDeletion 5
	Reporting 1984
	RelayListMetadata 10002
	MuteList 10000
	DMRelaysList 10050 (this is new from nip-17)

are permitted, and if any are present in a req from an unauthed client, all but these kinds are stripped from the req and forwarded to request processing (and count, of course)

i sorta feel like there should be a further flag that triggers so that after the request is delivered, the auth request is still sent but i think i'll just leave it like this, when requests are made that require auth, the request will be responded to with an auth request, but any requests that do contain these kinds in the kinds field will be processed without any notice or ok, false.

nostr:nevent1qvzqqqqqqypzqnyqqft6tz9g9pyaqjvp0s4a4tvcfvj6gkke7mddvmj86w68uwe0qyghwumn8ghj7mn0wd68ytnvv9hxgtcpzamhxue69uhk6mr9dd6jumn0wd68yvfwvdhk6tcqyqljz82ghrxxj48m7tsuk2tk6r2qzl2mynm4v6q4g0c7vdr626p8s5gw8rj 
 yeah, it was an easy change to make, it now checks if the filter was rewritten, and this only happens if it was not authenticated but contained directory kinds 
 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