Will look into it in detail shortly, but would it make more sense to treat the links I upvote as the ones I "liked" rather than the ones I open? Or, is this how it already works?
It's more nuanced than that. I'll often click through a link or comment link and immediately leave. Often times the title was link-bait and I'm not actually interested in the content, or the content was disappointing even if the topic was interesting.
Doesn't seem to be doing anything for me. Installed it, clicked on a ton of links from hacker news, clicked on "more" a few times, and don't see anything recommended. The extension is definitely installed; I can see the small icon in the omnibox when browsing HN. Is there anything else I need to do?
Does the data not persist between visits? I used this yesterday and it highlighted some posts, but today I got on HN and nothing is getting highlighted.
Yes, you have to. :/ I tried to explore ways to grab the data without needing to click it, but I needed a well defined action (going to the next page is valid to me) that would tell the classifier to train on the data. I'll see if I can find multiple ways to direct certain actions to train the classifier.
Naive Bayes is an online classifier anyway, training on click would be the equivalent of clicking a single link and then clicking next. I don't see why it would be hard to do...
It should only be two times. Two pages of results is enough. And no there is no way you can tell it you don't agree, but that sounds like something I can explore. :)
When did you download it, if at the time when I said it was updated try to download it again. What OS and browser version are you using?
Can you go to the extensions page, click the background.html file, inspect elements, console, and type in hnClassifier.getClassObj() and post the output.
Look at the local storage, by typing JSON.parse(localStorage.getItem('classObjs')) and tell me if it looks similiar to the output above.
If you had the older version, please go to the extensions tab and click reset data.
Same here. When I saw the post, I was wondering if it is the same person, because the other hacker also used the same algorithmic implementation for the recommendation engine.