lunasorcery

as seen on cohost!

30-something poly kinky queer mess
recovering former game dev
dating: @estrogen-and-spite & @RobinProblem


personal blog (with rss!)
moonbase.lgbt/
other website
tiredand.gay/

looks like @nes-pictionary is starting to post repeats, but there’s plenty of drawings in the pool that still haven’t been posted; gonna spend some time today reworking the selection logic to try to mitigate that a bit

right now the logic is:

  • pick four drawings at random
  • post whichever one has been posted the fewest times

I think a reasonable improvement might be:

  • pick several drawings at random (like idk maybe a few dozen?)
  • narrow that list down to the ones that have been posted the fewest times
  • if they’ve never been posted (ie posted 0 times) post one at random
  • if they have been posted before, post whichever one was posted least recently

You must log in to comment.

in reply to @lunasorcery's post:

I think the second alg will tend to get locked into a fairly consistent order.
How about:

  • drop the most recent X posts, to avoid tightly spaced repeats after it restarts
  • narrow that list down to the ones that have been posted the fewest times
  • pick one at random

Yeah, I think that’d be better.

Thinking about it, my second algorithm could also end up posting recently-added drawings twice in a row in rare cases, consider a situation where:

  • every drawing in the pool has been posted twice
  • I add a new drawing to the pool
  • it gets picked as part of the random set
  • since it’s been posted the fewest times (0), it gets posted, increasing its post count to 1
  • six hours later, it gets picked as part of the random set again
  • since it’s been posted the fewest times (1), it gets posted again

Your approach of excluding the N most recently posted drawings would completely prevent that.

I wasn't even thinking about adding new ones to the set, but that's a good point. My version has the weird property that a new post will come to exactly every Nth time until it catches up. It's probably better to not consider the total number of times a post has been posted, just if it has come up in the current round or not.