@getrickey@willissss@robingood Thanks Robin for taking the time to re-record that video, that is really useful. Unfortunately it relates to the issue I mentioned in point 1) above. It's an issue Google have introduced in their latest versions of Chrome which ironically conflicts with their own sign-in functionality. Agh.
@robingood We think we may have been able to get a fix in for this - could you try signing in at https://footnoteapp.com now? Thanks
Report
Offers a much better way than the History of your browser to capture, organize, save and search through all of the info you navigate through daily.
I need to test it further but it looks as a very interesting tool I'd probably adopt for keeping better track of what I have gone through and re-find more easily content that it is important to me.
It has a few shortcomings in my tests:
Even though I am logged into Google, I cannot login into the app and see my history
I need to open a new browser or clear cache and cookies.
When I click on "Mark Current Page" there's no visual indication of whether my command has been registered or not.
@robingood Hi Robin, thanks for the feedback.
1) The login issue is a bit of an intermittent bug. Does the solution you mention above work every time?
2) We don't currently support cross-sessions between web-app and extension with sign-in intentionally. This is because the extension essentially relies on always being logged in in order for it to be automatic. Of course accessing your own reading could be a lot more sensitive so signing out of that view independently we saw as preferable for our base case (though of course it could potentially be improved).
Report
@rubengmurray Hi, 1) yes. The one that works all the time is opening a new incognito browser window. There it works always.
2) Not very clear at all. In plain words?
@robingood
On 1). This is unfortunately an issue that needs to be fixed by Google themselves as we use their sign-in. It was introduced by them relatively recently in Chrome (https://github.com/google/google...). Using Safari or Firefox appears to have no issues. Unfortunately not a lot we can do about this in the short-term :(
On 2). We weren't sure that maintaining sign-in between the website (viewing) and the extension (recording reads) was the best thing for users. Imagine that a user signed out of the website and didn't sign into it again for a week - the extension wouldn't have remembered any reads in the intervening period.
Report
Would be happy to provide further detailed feedback and bugs as I use it. Feel free to contact me directly at Robin.Good@masternewmedia.org
Footnote
Footnote
Footnote
Footnote
Footnote
Footnote
Footnote
Footnote
Footnote