Discuss Scratch
- Discussion Forums
- » Advanced Topics
- » How to code a suprise carousel for older projects?
- Failord
-
Scratcher
1000+ posts
How to code a suprise carousel for older projects?
I have posted a main topic about this suggestion. Discuss it here.
This topic is just to talk about getting it to work.
If you just make it pick from all 3 million projects at once, it might slow down the front page. My solution? A system I call “pooling.”
At the beginning of the day, a group(or, pool) of projects is randomly selected from all eligable projects. Then, when you load the front page, it picks out of the pool randomly. The pool could have 50 projects, or, if you want to reduce repeats farther, 100 projects. If a project loses eligability, it can drop out of the pool and replaced with another project.
Just like a real pool of water, where molecules evaporate and condense into it, it could randomly decide to replace projects in the pool. This would also lower redundancy. Perhaps there colud be a certain percent chance that a project will drop out when viewed, to make room for more projects.
Every project that enters the pool would be “marked” for the day, so that it is barred from the pool in subsequent days until the mark is removed. The mark would be cleared off of all projects at the end of the week.
That way we have a changing, dynamic, fair pool for the “Older projects” carousel I suggested.
This topic is just to talk about getting it to work.
If you just make it pick from all 3 million projects at once, it might slow down the front page. My solution? A system I call “pooling.”
At the beginning of the day, a group(or, pool) of projects is randomly selected from all eligable projects. Then, when you load the front page, it picks out of the pool randomly. The pool could have 50 projects, or, if you want to reduce repeats farther, 100 projects. If a project loses eligability, it can drop out of the pool and replaced with another project.
Just like a real pool of water, where molecules evaporate and condense into it, it could randomly decide to replace projects in the pool. This would also lower redundancy. Perhaps there colud be a certain percent chance that a project will drop out when viewed, to make room for more projects.
Every project that enters the pool would be “marked” for the day, so that it is barred from the pool in subsequent days until the mark is removed. The mark would be cleared off of all projects at the end of the week.
That way we have a changing, dynamic, fair pool for the “Older projects” carousel I suggested.
Last edited by Failord (May 16, 2013 20:20:08)
- Failord
-
Scratcher
1000+ posts
How to code a suprise carousel for older projects?
Bump! And please look at the root post for my idea, linked above!
- elfin8er
-
Scratcher
100+ posts
How to code a suprise carousel for older projects?
Hm, this seems like a good idea. However, I think we'd get a bunch of people's “test” projects, or projects that aren't (no offence) very good. Maybe it would work better if it took the views to likes ratio? That way if a project has 15 views, and one like, it would be more likely to get into the pool than if it had 15 views and no likes. Likewise, a project with 1000 views and 1 like, would be less likely to get into the pool than a project with 25 views and 1 like. This would sort of give projects that aren't that popular, but of good quality, a better chance of getting more popular.
Last edited by elfin8er (May 16, 2013 21:41:28)
- Hardmath123
-
Scratcher
1000+ posts
How to code a suprise carousel for older projects?
But with the new views system, view-love ratios don't say much (a good project would get a lot of views, too, since you play it again and again).
- Failord
-
Scratcher
1000+ posts
How to code a suprise carousel for older projects?
Hm, this seems like a good idea. However, I think we'd get a bunch of people's “test” projects, or projects that aren't (no offence) very good. Maybe it would work better if it took the views to likes ratio? That way if a project has 15 views, and one like, it would be more likely to get into the pool than if it had 15 views and no likes. Likewise, a project with 1000 views and 1 like, would be less likely to get into the pool than a project with 25 views and 1 like. This would sort of give projects that aren't that popular, but of good quality, a better chance of getting more popular.
But with the new views system, view-love ratios don't say much (a good project would get a lot of views, too, since you play it again and again).
Exactly. I feel like it shouldn't discriminate too much. The idea is making it fair. And the fewer good projects that show up, the more likely you are to click on one than if a bunch show up. I think.

- shelter
-
New Scratcher
42 posts
How to code a suprise carousel for older projects?
good idea
but seems complicated
but seems complicated
- Failord
-
Scratcher
1000+ posts
How to code a suprise carousel for older projects?
good idea
but seems complicated
It could work. Besides, if you don't want to see complicated stuff, look in a section of the forums besides Advanced Topics.
Last edited by Failord (May 17, 2013 20:04:59)
- Paddle2See
-
Scratch Team
1000+ posts
How to code a suprise carousel for older projects?
Since this topic hasn't seen a new post from the topic owner in a long time, I'm going to assume that it is dead and close the topic. If it still is alive, the topic owner just needs to use the Report button to ask a mod to reopen it 

- Discussion Forums
- » Advanced Topics
-
» How to code a suprise carousel for older projects?