Hello everyone,

I've been using offpunk for a while now, and I really like the overall
concept behind it. But I think that the refresh time/cache validity
functionality could be adjusted. 

Currently, it is only possible to set a single cache validity argument 
for both subscriptions and other lists.

I propose that there should be two separate refresh times: One for 
subscriptions and one for other lists. Also, I believe it is more 
intuitive if the default refresh time for the subscriptions is not 0 
(which makes them never update unless a --cache-validity argument is
used) because a user would expect for new items from their subscriptions
to arrive automatically if they sync regularly.

What are your thoughts on this?

On 24 mai 03 11:02, Siroj42 wrote:
>Hello everyone,
>
>I've been using offpunk for a while now, and I really like the overall
>concept behind it. But I think that the refresh time/cache validity
>functionality could be adjusted.
>
>Currently, it is only possible to set a single cache validity argument
>for both subscriptions and other lists.
>
>I propose that there should be two separate refresh times: One for
>subscriptions and one for other lists. Also, I believe it is more

Having multiple refresh times open a huge array of cemplexities. If two, 
why not three? If three, why not four? How to indicates them, how to 
choose them?

I believe that one single refresh time is really more intuitive.

Keep in mind that you could "freeze" a list to not refresh it. 
Personnally, all my "bookmarks" lists are frozen.


I use the "normal" list approaches for subscriptions where I don’t want 
every new item to be in my tour. For example, the lobste.rs XML feed is 
in a normal list so I can read the title of popular links and choose to 
read them or not. It also works really well for RSS feeds with contents 
in them instead of links to external articles.


>intuitive if the default refresh time for the subscriptions is not 0
>(which makes them never update unless a --cache-validity argument is
>used) because a user would expect for new items from their subscriptions
>to arrive automatically if they sync regularly.

This is a separate issue.

There’s a reason why the default refresh is "never": if, for whatever 
reason, you launch offpunk --sync and forget to add a refresh time, 
nothing bad happens.

With a default refresh time, if you forget to put it, suddenly, you 
launch a full refresh (which can be quite long) and could also have an 
impact on future refresh. For example, I run a full refresh every 
morning with a 16h refresh time. This ensure that I will not do a full 
refresh for the rest of the day while allowing me to run a full refresh 
between 8AM or 13-14h.

If I would run a full refresh with a default unknown time which is 
shorter than that, I would mess with the schedule.


Which also raises the question: what should be a default value?


>
>What are your thoughts on this?


>

-- 
Ploum - Lionel Dricot
Blog: https://www.ploum.net
Livres: https://ploum.net/livres.html