making progress on the moderation/access control code for realy it now has a cache that keeps track of the follows and mutes of the designated relay owners, which are used to make decisions about accepting events and requests figured i'd keep it really simple, if the list is empty, it populates it, if a mute list or follow list is received that is one of the relay owner npubs, it empties the list so next time a req comes in it regenerates it before evaluating whether to process it - the working theory at the moment is that followed npubs are allowed blanket read and write access - other users can submit events if they tag one of the allowed users and then it checks that user's follow list and accepts it if the other user follows that user - other users can make queries where they are tagged if one of the users is on the follow list - any user on the mute list is denied read and write access - any event authored by one of the users on the mute list is rejected, and they are also not able to make requests - any event tagging one of the followed users that is also muted by that user is rejected one caveat this brings up is that for the other users submitting events, that isn't possible until they have submitted their follow list, so the inbox won't work until they have published their follow list... i might need to add another feature that scans the network looking for their follow event, or just make a tool that automatically scans the network and uploads all of the owner follows and the follows follow/mute lists gonna be a bit of work getting this to happen but i figure step by step... i'm almost certainly going to need that scanner tool made