🎵 Celiz Davidad 🎶

The way I've been thinking of making Recommendable more modular would be to split it up into multiple gems. My initial thoughts are a structure somewhat like... - `recommendable-core` would...

Sure; though I'm mostly concerned with the query interface, which changes enough between ORMs that we've gotta handle that. I'm not terribly fond of my current case statement that just...

I think extracting core is gonna be difficult, because I'm still not entirely certain exactly what will go in there. I'm pretty certain that the logic to compare users and...

Perhaps a C++ extension would be more sane? [It has sets](http://www.cplusplus.com/reference/set/set/) and [they can be ordered](http://www.cplusplus.com/reference/set/multiset/). Another option would be a C extension that uses the [JudyHS](http://judy.sourceforge.net/doc/Judy_3x.htm) structure

Ah, yeah. The reason for this is that all recommendation values (or the top N values if you've used `config.nearest_neighbors`) get stored in Redis. So if you've only been compared...

It's definitely sorted by highest score. Are you sure that 315 has a negative score, or a lower score than 1466? I'd inspect the Redis ZSET directly. Are there other...

Sorry, typoed that. I meant to ask if there are any other ratings (likes/dislikes) at play here.

Anyway, please do try to reproduce it in a codebase I can clone down and take a look at. Thanks!

Shoot, you're right: https://github.com/davidcelis/recommendable/blob/master/lib/recommendable/rater/recommender.rb#L21-L27 I thought that I was correctly sorting the records before returning them to the user, but that's not the case. So while that list does contain...

Good point. I think that at the very least, items with negative scores should never be recommended. I can definitely fix that much, but I'll need to think a bit...