You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got a message from Sahil via email, this is his question/proposal:
Can we save multiple copies of the index (i.e. what happens when a page goes down, or link has 404? Will users be redirected to Wayback Machine?
My answer:
Not yet, up to that point we do not store the page completely so that you can re-visit it without a connection or take multiple versions into account. We only store the text so you can search it again.
But this is a feature planned for the future. (also excellent idea to connect it to the WBM!! :)
Additional to answer:
I think it's future stuff for now, but we definitely should consider it to store a readable version of a website and/or connect feed into WBM.
Well, the text itself is not so big, Its basically what we store in the DB. But storing a complete HTML to make it retrievable as it was is definitely big.
A reader version is thinkable, as it would pull the text that is already in the DB.
or just add an option in setting menu or in extension icon menu to store the page in your servers like Wayback machine does... the size won't be that much of a problem then or I think it will solve most of the problem the only disadvantage is privacy though ;(
I got a message from Sahil via email, this is his question/proposal:
My answer:
Not yet, up to that point we do not store the page completely so that you can re-visit it without a connection or take multiple versions into account. We only store the text so you can search it again.
But this is a feature planned for the future. (also excellent idea to connect it to the WBM!! :)
Additional to answer:
I think it's future stuff for now, but we definitely should consider it to store a readable version of a website and/or connect feed into WBM.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: