Oh yes. I was considering that. I've stayed for a while with a convention solution - write and toggle replaces, but go adds to the history. You can build on top of that, but I think it's reasonable now.

It manages for you what you want to be in a history. Imagine example with an input which writes on each keyup to the history and going back letter by letter.

So when you click on a "link" it goes to the history. If you play with params on a single view it replaces.

What do you think?