EDDN: *time* delayed sending of data
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 182
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
I have a horrible feeling looking at this will also entail finally addressing https://github.com/EDCD/EDMarketConnector/issues/665 as well.
The option to delay sending EDDN data until docked is overkill. I'd rip it out entirely, but I'm sure that would upset some very vocal users and cause them to just linger on the previous version.
So, instead let's introduce a *new* option to be able to delay sending to EDDN until some user-defined number of minutes 'later'. The thinking here is that *some* users of it will only want to hide that there's an active user in those systems at the time they're there.
Contributor guide
Research direction
Start by reviewing the existing EDDN sending and docked-delay behavior, then read issue #665 for related requirements. Determine how a user-defined delay should interact with the current option and define completion around configurable delayed sending without breaking existing users or data delivery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100