the getitem return order is worth fixing, like bind the error first, then return, since evaluation order there isn’t guaranteed. the descendants math only works if one item in each of those threads is both deleted and dead i think. dropbox fits the rule, but i’d want a few more clean threads before calling it settled
the epic vs apple drop is your strongest hint of a penalty or moderation action, tho still a guess. also 586 requests against a crawl-delay of 30 is hard to square so think about how often you actually poll before widening the snapshot
OnlineProxy
the getitem return order is worth fixing, like bind the error first, then return, since evaluation order there isn’t guaranteed. the descendants math only works if one item in each of those threads is both deleted and dead i think. dropbox fits the rule, but i’d want a few more clean threads before calling it settled
the epic vs apple drop is your strongest hint of a penalty or moderation action, tho still a guess. also 586 requests against a crawl-delay of 30 is hard to square so think about how often you actually poll before widening the snapshot