"Hot" events

[Steve Meyers]

It seems to me that the "hot" events could use a re-think. It currently
orders by how many days removed we are from the event, modified by the
number of comments + the number attending. Since comments and number
attending tend to go up during/after the conference as feedback is left,
we end up with conferences that have been over for a while still showing
up as "hot".

I'm not sure what the best solution is. I don't think event comments
are particularly useful in determining "hotness". It'd be nice to keep
track of when users said they were attending, and then base the hotness
on recent activity (people saying they're attending, comments, etc).

Steve

[Joshua Thijssen]

Hi Steve,

There have been multiple attempts on finding good algorithms to find a
good "hotness" factor. Unfortunally, it's hard to find one, and
currently have a "good" algorithm results in major database penalties.

Saying this, it might be possible to see if we can "revert" the hotness
algorithm which takes lots of things in account (basically, the improved
version of the one i've created last year or so), and update the
event-table offline. This would mean we have a hotness-cronjob running
every hour or so (I doubt we need it run faster). This might work, as we
can use more advanced algorithms this way without loosing site performance.

[Elliot Ward]

I think it depends on whether we are measuring the heat of the event, or the heat of the event's incarnation on joind.in. If the former, I'd be interested if tweet rates offer close mirroring of such hotness.

--
You received this message because you are subscribed to the Google Groups "joindin-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joindin-developers+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Lorna Mitchell]

The hot events is a fun algorithm, as Josh says, quite a few people have had a shot at amending it, and it's much better now than it used to be.  The aim of the "hot" event is to get the events that people are looking for to appear on the front page of joind.in (which shows 6 events at the moment).  So the events which do have people marking themselves as attending, and commenting, are IMO the right events to send.  It's great if events are hot across the 'net beyond joind.in, but there are plenty of events which just use joind.in for free advertising.  For those events, we'll be using donated servers to run twitter stats to give preference to events who aren't using joind.in at all, they're not going to be leaving any data with us, and the people who really *are* using the site won't be able to find their own events so easily.

Patches welcome on the "hot" algorithm, but I currently would hesitate before merging anything that took into account data outside of our own right now.  Happy to be persuaded as always, though :)  Also Josh makes an excellent point - to calculate and cache those "hotness" results would help with performance, and would be well worth doing if anyone thinks they can handle the challenge.

Lorna

To unsubscribe from this group and stop receiving emails from it, send an email to joindin-develop...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Lorna Mitchell
http://lornajane.net