Timeline is cluttered up by autosave

[bpcurse]

Describe the bug
When a card's description is edited in detail view, autosave is active quite often. Every autosave action is logged to the timeline.

To Reproduce
Steps to reproduce the behavior:

1. Go to the detail view of a card.
2. Write something in the description field or change something.
3. Wait approx. 3 seconds.
4. Repeat steps 2 and 3 several times
5. Look at the timeline. It is cluttered up by unnecessarily logged minor changes of the same "card editing session".

Expected behavior
Autosave actions should not be represented in the timeline.
Changes to a card's description should only be logged to the timeline if the detail view is closed, opened and edited again. Maybe there should even be an additional timeout for this?

Screenshots

Deck 0.5.0 / NC 14.0.4

[putt1ck]

Alternative option: record autosaves within a single time period; this reduces clutter but allows for the (definitely apples to me) use case where you make a change but then get distracted by other information flows and don't close the detail view i.e. open card, add information to detail view, then an email arrives (or a telephone call, or a visitor, or a baby, or...).

You will eventually close the the card or detail view, but the timeline of events would now be wrong and potentially out of sequence.

A 10 or 15 minute time period would greatly reduce the clutter while providing a useful timeline within the activity stream (card/Deck and central NC)

[bpcurse]

@juliushaertl A question in general, regardless of the solution you are working on:
Could the autosave function be a bit less "aggressive", or would this bring up other problems in user collaboration?