#orly #devstr #progressreport #update

i have now implemented a full ACL that uses a set of designated owner pubkeys, spiders to get their follow and mute lists, and spiders their follows to get their follows follows, then excludes the muted pubkeys from the followed follows list.

it has been done a great deal more simply than my previous form of this ACL algorithm, and will stay up to date with every followed users follows within a reasonable time window, most of the time, the spider list defaults to the most popular, public to read relays that many of them have spiders syncing up with many more relays, so this will now stay up to date with users follow and mute lists.

i should probably make the spider collect updates to user profile metadata (kind 0) events as well, since this is important for UI. possibly also to sync the users relay lists as well, so that users of the relay will always be able to reach the people they connect to. idk how complicated i want to make things with the spidering though, adding more than the default list of spidered relays could make the spider very slow, but at least to have their metadata and relay lists, then clients can do their thing.