I would also limit it to information that is not readily available in the overview.
- Word count (the reading time usually depends on the number of words, so I could do without it),
- your feed-reach (whereby it is questionable whether the values are comprehensible for everyone),
- unique authors,
- the follower netword strength to combine both extensions,
- michelangelo3's comment-post-ratio I would very much like to see,
- when I am logged in, it would be nice if I could see how many times I have already voted for the author in the last 7 days (I know it would be a challenge).
I've been thinking about it for a while, and I've come up with some interesting things (powerdown, powerup, powerdown-powerup-ratio, etc.). For most of them, however, I don't think they are that important for daily curation.
I also like this one. I'll definitely see if I can incorporate it.
I like this, too:
But yeah, I'm afraid latency might be too high.
Longer term, I'm thinking that some high latency metrics about active authors could be collected by a supporting python script and stored in custom_json transactions from a designated account in order to offload the latency to somewhere where it doesn't matter, but I'm not sure if that model will work for multiple unique observers.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit