For the time being, we've removed personalized hot ranking. In general, we don't have enough people zapping, and especially people zapping consciously/honestly, such that it makes that big of difference in practice. (Also, the way we were doing would've complicated some of the enhancements I made in this release, and the enhancements I made will give way to more efficient personalized ranking.)
Speaking of enhancements:
- Each territory has its own trust graph now. In effect, this means that even if a post doesn't rank high on the homepage, it can still rank high in a territory.
- e.g. if someone creates a ~bip300 territory it can have a life of its own even if the majority of stackers never want to participate in the territory
- Each stacker has an independent trust score for each territory they zap in.
- You might zap well in ~Stacker_Sports according to consensus, but zap garbage posts in ~bitcoin, and this allows for such granularity in scoring
- Similarly, post zapping and comment zapping each have independent trust scores.
- You might zap great posts in ~bitcoin, but horrible comments, or vice versa, and this allows for such granularity in scoring
- Comment zapping by trusted comment zappers, now slightly boosts the ranking of the comment's ancestors
In summary, for each territory, a stacker zapping in that territory gets four trust scores:
- post zapping trust according to global consensus
- comment zapping trust according to global consensus
- post zapping trust according to the consensus of zappers in the territory
- comment zapping trust according to the consensus of zappers in the territory
This will probably need refining after some live experiments, but this is the direction we're headed in.
The only other meaningful change here afaik was fixing reply costs for the automated monday ~memes post which led to the 10 sat reply cost set by the founder being ignored (due to a case sensitivity issue ~memes vs ~Memes)
View all commits here: https://github.com/stackernews/stacker.news/commits/master/
Since starting the Open Source Contributor Award Rules (OSCARs), we've paid a total of 20.5m sats to 41 contributors for 186 contributions! View a nearly up to date list of contribution awards here: https://github.com/stackernews/stacker.news/blob/master/awards.csv
Previous release: #904497
CREATE INDEX IF NOT EXISTS some_idx ON some_table(some_value DESC NULLS LAST)
is NOT equivalent toCREATE INDEX IF NOT EXISTS some_idx ON some_table(some_value DESC)
.second4-hour there.pandas
inpython
, but no one uses that for a production database.