I also need to open up a little more around here and not be afraid of weirding people out or over-do-ing it.
I really like it here though and I have lots of ideas.

Yeah. I do know a bit about how numbers and stuff works. I do that professionally.fluffy wrote: CRay: The big problem with a simple +1/-1 is that it unfairly biases really high (or really low!) scores towards older content. The Elo rating scheme is much more fair, as newer and overlooked things can move much more quickly to its natural rank within the ecosystem (and part of its effect actually causes natural churn at the extreme edges, since if you have an established high-rank item that goes up against an unestablished or low-rank item, the low-rank item actually gets points no matter what - in the chess world, a newbie going up against Kasparov will give the newbie a lot of points no matter how it turns out, while Kasparov loses points just by merit of having gone up against the newbie anyway).
What I'd be afraid of with standard scoring systems (+1/-1, average rating, etc.) is you'd normally have a few very deeply-entrenched songs that stay at the top, without any breathing room for new things to show up. This is what happened with SomeSongs, for example. Elo has a built-in "freshness" factor that has nothing to do with arbitrary things (like "ratings in the last week" or whatever), and that combined with a random-pairing what's-better system means that you aren't just going to have people listening to the top few songs and going "yep, still like it" and keeping them cemented there.
I'd help if I could. But I'm more of a hardware developer. HEY OH!Lunkhead wrote:Oh, and that leads me to another idea for a way to rejuvenate the community: more software developer activity.
Mike Lamb likes this.ken wrote:I think the main thing is that we implement a way to "like" things and also to become a "fan" of things. This seems to be a very successful model on other popular sites.
I don't have a straightforward way to access the number of songs, or fights or artists, for that matter. I do make that available in the HTML for the homepage, though, so it would be pretty straightforward for me to add a "stats" endpoint that would return those numbers if you'd like.fluffy wrote:Ah, and /fights.json gets the list of all fights with entry counts. Perfect. Could that also be extended to give the number of songs in the archive? (I know I could compute it myself, but you already have the number of entry rows in the database available, presumably.)
Presumably you'd prefer if anyone who queries /fights to cache it with a fairly large TTL (looks like the query takes a little while, in any case), but that's straightforward and it's not like the data changes more than once a week.