What info would you want to see here?

in hive-142124 •  2 months ago 

If you were curating Steem posts and you had a button available in the Steem Curation Extension to click or to mouse-over in order to see an overlay with more information about a specific post before deciding whether to click all the way into it or not, what additional information would you want to see?

I'm thinking of things like:

  • word count / reading time
  • number & value of bid/delegation bot votes
  • Age of the author's account
  • List of top tags
  • number of resteems
  • feed-reach (author's follower count + sum of followers of all resteemers)
  • Number of unique authors in the reply thread
  • Some engagement metric (along the lines of [# comments / median vote value])?

I was also thinking of the follower network strength, but that might take too long to calculate for some authors. We'll see...

A "stretch goal" might be to eventually incorporate some AI feedback, but I think that's pushing it, at least for now.

In the end, I'll be highly constrained by the size of the overlay and by the need for speedy collection, but it should be possible to give curators some additional useful information.

In short, what other information would you like to see in an overlay pane like the one below?

Also, would you want the overlay to be available for posts, comments, and replies? Or just for posts?

Obviously, this isn't the final look. Just exploring at this point.

Please let me know if there's anything else you'd like me to consider including?

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

That's pretty nice👌 I feel like we can usually get a sense of the tags from the title, so they’re not a priority for me.
Word count can be too much detail and it might even make people avoid longer posts, pushing writers to keep things too short. On the other hand, reading time is useful, no surprise in the post.
While reputation score shows the author’s standing, it could create bias against newer writers.

My top choice would be bot vote info, since it helps spot whether a post is organically popular or boosted by bots.

Thanks for the feedback! I thought of reputation score, too, but that's already visible on the left, so I don't think I'll need to repeat it. I have mixed feelings about word count, too. I think it's useful information, but it's too easy to convert it from a data point into a screening threshold. I also like reading time.

I definitely think the bot vote info will make the final cut, if I have a fast enough way to calculate it.😉

I'll probably play around with displaying tags. They could take up a lot of space, though, so it may turn out to be impractical to include them.

You're welcome, excited to hear the bot vote info might make it in. It’s super useful 😊
Yes, I agree with you about reading time, as I said before I believe that is also useful option.

As for tags, if they take up too much space, it’s probably best to leave them out.
Looking forward to seeing how it turns out👍

What I would find quite interesting would be the comments/posts ratio. Easy to calculate and yet this value (usually) gives a good indication of the extent to which an account is involved here. The theory is that if someone writes more posts than comments, then their participation or interest in the work of other users is not particularly high.

And of course, exceptions prove the rule :-) remlaps-lite only has a C/P of 0.9 as you can see here. (small example follow list to show the C/P value)

number & value of bid/delegation bot votes

Probably wouldn't be that easy, outgoing delegations (in % of total SP) would perhaps be a sufficient indication in this context.

Where did you find the number of comments? It's coming up as zero wherever I've checked so far:

$ curl -s --data '{"jsonrpc":"2.0", "method":"database_api.find_accounts", "params": {"accounts":["remlaps"]}, "id":1}' https://api.steemitdev.com | jq -S '.result.accounts[] | .post_count,.comment_count'
3400
0

Update: Never mind. I found it.

I found it.

Yes exactly, that is also the query I use. 🖖

Making progress.😀

And of course, exceptions prove the rule :-) remlaps-lite only has a C/P of 0.9

lol. This doesn't surprise me. I am very much a lurker when it comes to social media. I do like this statistic, a lot, though. I will definitely try to include it. Thanks for the suggestion!

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.

michelangelo3's comment-post-ratio I would very much like to see,

I also like this one. I'll definitely see if I can incorporate it.

I like this, too:

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).

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.

From my experience as a curator, I can say that a word count would be very helpful. No, not because the curators only support posts with more than 300 words. This is already in the past. It's just that if the post is not about visual art and it only contains, say, 10 words, it will save the curator time and he won't even review it. Curators are also people and they mostly always lack time 😄.

Information about bot voting will also be invaluable for optimizing the work of curators.

One of the curators' tasks is to distribute votes as widely as possible, including by geography of authors. However, I don't think any extension is capable of telling which country the author is from. But maybe you can indicate in which language the post is? It will probably be possible to do this at later stages with the involvement of AI.

I also thought about location and language. There are JavaScript language libraries that can report back on the text's language, but I'm not sure if that can be incorporated into a browser extension. I'll look into it, but I have a feeling that it might be challenging in this context.

Sounds like a useful tool.

Would it be possible to include beneficiaries, and also whether the author is currently powering down?

Beneficiaries are already available if we click on the payout amount, so I probably wouldn't want to repeat that here. Power down status is definitely possible. Personally, I'm not a fan of using powerdown or club status in curation decisions, but I know many people feel differently, so it probably does make sense to include it here.