Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - High Priority Structure Notifications #850

Open
Dyn0mike opened this issue Dec 28, 2021 · 0 comments
Open

Feature Request - High Priority Structure Notifications #850

Dyn0mike opened this issue Dec 28, 2021 · 0 comments
Labels
complexity/high This task has a high complexity level core/jobs General things related to jobs flow packages/notifications Issues related to notification package or its dependencies. todo-no-milestone Low priority, but not closed

Comments

@Dyn0mike
Copy link

An optional feature for people uses SeAT for structure notifications.

When turned on it should take any toons with in-game roles to receive structure notifications and process their notification ESI calls independently.
It should space each toon out even across CCP's cache time, so a structure notification is never a full ten minutes late.

Assuming CCP caches data for ten minutes and a corp has ten toons that can receive structure notifications:
Each toon should be polled every ten minutes with a spacing of 60 seconds between each toon.

With this setup, a structure notification should take an average of 60 seconds to be received by SeAT.

@warlof warlof added complexity/high This task has a high complexity level core/jobs General things related to jobs flow packages/notifications Issues related to notification package or its dependencies. labels Dec 28, 2021
@Crypta-Eve Crypta-Eve added the todo-no-milestone Low priority, but not closed label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity/high This task has a high complexity level core/jobs General things related to jobs flow packages/notifications Issues related to notification package or its dependencies. todo-no-milestone Low priority, but not closed
Projects
None yet
Development

No branches or pull requests

3 participants