I think we're making too complicated. Having it degrade is not necessary in my opinion since just because time passes doesn't mean better cubes will come out. A cube from 2015 still may be the best cube out there. To make it more simple and not overwhelm people with choices (which is the case right now), we should recommend 1, 2, or 3 puzzles per event (2x2, 3x3, 4x4, etc) and rate them as Budget, Great, or Expert. This way for each puzzle someone can make an easy choice. If we have 10 puzzles already rated as "Good", it makes it difficult to make a choice. In that case where 5 are "Good", let's just pick the cheapest one and make call it "Good" for that event. The point here is to keep a simple, updated post with the most suggested cubes by the community. What do you guys think about keeping it more simple?I like both ideas. Both are easily done. I already added "Class" where we can put budget, great, expert. Of course some budget cubes are super good cubes, and can get a high rating. And some expensive cubes are not so good and can get a low rating, so I think rating should stay, but a weighted rating from various users should be possible. Having it degraded is trickier though. Because for example the Weipo is still a top cube, but it's not the newest, so the rating would have gone down a lot over the last year. Which isn't fair, it still rocks. I don't think we should let cubes drop in rating automatically. If people change their mind about the ratings of the cube, it makes more sense for them to change their rating on it in the list.
Edit: Weighted average added. I put three names in the columns as examples. The function counts until column ZZ so that should be more than enough columns for everyone to get their vote in.
Agreed on both points. I think a release date is good, though not absolutely necessary as long as we keep the list updated each month or two.I am very interested in the recommendations from this list. Hardware-wise I am basically a noob.
Degrading on age for cubes is not something I would want. I would find it useful to have a property "releasedate" and a property "not commonly available anymore" so in the future we can filter the list on these properties