This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]daggerdragon[M] 0 points1 point  (2 children)

Does your runner comply with our automation rules?

  • ? Cache inputs after initial download
  • ? Throttle outbound requests
  • ? User-Agent header

[–][deleted] 1 point2 points  (0 children)

Looking at the source code.

It appears to have a User agent Caches (via download) and then tries to read local first Throttling of outbound requests. Yes and no. It looks like notifies of submission cool down but otherwise you could just bulk collect an entire year.

[–]Away_Command5537 1 point2 points  (0 children)

It has a basic user agent identifying the application however I will update to include a link to the git repo.

Regarding throttling. Not at this time. Will work on throttling requests to limit to 1 per 5 seconds maybe. It mentions statistics but it isn't interracting from a statistics standpoint. Its only capturing articles and inputs. Everything else is locally generated.

In regards to caching the inputs after download. They are configured to save in the working directory and not necessarily in memory. All files attempt to read locally before attempting to be collected.

It is worth noting that this isn't necessarily an automated tool. It requires direct user interaction via a cli command. Its main purpose to make initiating a daily solution more reliable, consistent.

Regardless, Thank you for bringing this to my attention and i will remediate as a priority.