I agree on this one 
It’s a difficult thing to fix, and probably not suitable for a single forum thread. @peakvalleytech @ByteHamster (and anyone else interested), would you be fine with participating in a couple of ‘workshops’ (using our Jitsi instance)? The hackathon meeting earlier this year worked really well in hashing out some agreed next steps.
Wile @peakvalleytech seems to have done the analysis of all the issues listed in the relevant milestone, I haven’t done that and I don’t have a clear overview of all the user needs yet. I think it’d be very helpful to write out the different use-cases and take that as a starting point. Rather than starting with a solution, and then adding different opinions and considerations to the conversation.
By meeting a couple of times, we can follow a more structured approach:
- identify different user needs:
- describe the different user stories in the milestone issues
- list the accompanying acceptance criteria
- optionally, ask users (e.g. those that created & commented on the GH issues) for feedback
- identify possible solutions:
- draw up a ‘matrix’ of elements/decisions to make (e.g. global vs local maxima; coupling vs decoupling auto-download & removal)
- reflect on (list) other user requests and considerations (e.g. prioritisation)
- define one or more solutions, by identifying one or more sets of mechanisms & features
- write up (in slightly more detail than above) how each solution would work for the user
- pick the solution (or combination of mechanisms/features) that we think will work best
- write out & review the proposed implementation
- write out for each user story how it’ll work (what the user will do & experience), given the chosen solution, and if necessary, consider adapting the solution
- prepare mock-ups & explainers
- put the proposal with mock-ups for feedback to interested users
I realise this is a more work and will take a longer period of time. But I’m convinced this will help us end up with a solution that’s much more durable.
If you agree, I’d be happy with trying to draft the user stories, based on all the milestone issues.