Trails are interrupted about memex HOT 5 CLOSED

Not in the case of page visits. From what I understand it's a bit tricky to get accurate trails between the visits from the info we can get from the browser. The browser history API keeps some form of trails between VisitItems, via their referringVisitId key, but in the case of page visits in our extension, we are creating our own history of user activity that is not related to the browser's history.

In the case of imports, we are essentially converting from the existing browser history state to our model, and here we have access to whatever trails the browser stored. So they are brought over and the trails can be derived from referringVisitId and the browser VisitItem ID which makes up part of the ID of a visit doc in our model (our doc ID looks like visit/:timestamp/:nonce and, in imports, :nonce is set to the corresponding browser VisitItem ID, if that makes sense). However, this trail data isn't being used in anyway in the extension/s, yet.

from memex.

Trails between visit docs aren't currently recorded when user visits a page.

from memex.

I thought a visit item carries the ID of the last visit item? @Treora?

from memex.

from memex.

Closing this until we start with the feature around capturing trails.

from memex.