The problem is atm we've no service that's updating seeders.
So they'll only ever show what they are on the initial ingestion

It's not the responsibility of the consumer. Its sole purpose is ingestion of torrent data from the queue. We need a new separate service that handles updates of seeders periodically

Ideally this would be wrapped in pm2 in the container as it allows execution of a task on a cron schedule ala: pm2 start update-seeders.js --cron "*/15 * * * *"

Do you wish to hold this merge until thats done?

No we can add it if you'd like 😃
It's just they'll all say 100 as the dmm ones are hardcoded lol

So open an issue for seeder updates & link this issue?

Aye good idea

Sorry I'm out atm 😃

No we can add it if you'd like 😃 It's just they'll all say 100 as the dmm ones are hardcoded lol

Would it be better to put a non-positive value or a different placeholder there to indicate that it is not currently accurate except on ingest?

#73 this is a good idea. Tagging the issue here for clarity.

Feels like this one should be closed, @purple-emily ?