nkanaev
Add 12 or 24 hour auto-refresh option
I think having the maximum auto refresh as 4 hours is very low. I don't need to ping 400 domains every 4 hours for a feed I check at most once a day. It is also just kinda rude to website hosters- as efficient as RSS and Atom might be.
Ideally the hourly refresh should just be an input field for the user to decide, but I can appreciate that this might be a huge rewrite of the relevant code. It should probably be straight forward to add to or change the available options, though.
Thank you :)
Can the synchronization function be separated out as an additional synchronization mode? Some cases like:
- Addition network setup needs before RSS sync
- More customized syncing frequency using crontab job to control ...
@xuboying If I understood you correctly, do you want to be able to trigger the refresh functionality without the UI? If so, will a cli flag/command suffice?
I see 2 options to solve this issue:
- Either adding new hardcoded values in the UI, like 8/12/16/24/48h
- Either adding a "custom" input in the UI, where the user can specify the frequency
But i concur that the current max 4h is maybe too quick! For my use case, by default, I would rather pick 12h.
Then, I also think that having the ability to define specifically each frequency for each feed could be nice, but to me this feature is less urgent that the feature of the beginning of my comment here.
@nkanaev sorry I missed you reply
In my use case, I need the flexible update methods, not only the frequency but also some network setup before sync, so the cli option would help I guess.
I've made some changes in the UI to support 12h and 24h intervals.
@xuboying As of flexible update methods, I'm not entirely convinced adding it as a CLI option is justified. You could, however, trigger refreshing externally by triggering the API endoing:
curl -X POST http://localhost:7070/api/feeds/refresh
This works only if you're not using authentication, though.