Also: there are use cases that go beyond filtering and sorting in the background.

Suppose someone you don’t follow DMs you. How do you know whether this DM is worth your time and attention? One method is just to hide the DM if the WoT score is below some cutoff. But what should be the cutoff? There will never be one right answer. So a better method is to show the WoT score next to the author, obtained from Trusted Assertions as the 0-100 rank metric, like Amethyst is doing. The end user can decide whether a score of 10 or 50 or 95 is worth looking at. Maybe I have a lot of free time today, so I’ll read the message if rank is above 10. But tomorrow I’m busier so it’ll have to be 90 to catch my eye. And in the case of personalized GrapeRank, a 50 for me may not be a 50 for you, because you and I may have selected different GrapeRank parameters. My “rigor” parameter may be set to a low value (by my choice), so when I see a score of 50 on amethyst, it means “this user is followed/trusted by 5 moderately trusted users”, whereas your “rigor” may be set to a high value, so when you see the same score of 50 on amethyst it carries more weight, bc it means “this user is followed/trusted by 100 highly trusted users”.

We can’t give users control over their user experience if our philosophy is to hide the number crunching and make all the decisions for them.

At the same time, we ALSO need to make it super easy for the end user. If they don’t want to look under the hood, they don’t have to. Which is why GrapeRank comes with default preset parameters. But showing turn numbers, like I described here and like amethyst is doing, will oftentimes be better than simply filtering and sorting under the hood.

Reply to this note

Please Login to reply.

Discussion

The DM example IS filtering.

If you do it manually every time, based on the score you see on the screen, one could send you 1M DMs...

What I am saying is that we can hide the numbers from the head of people, and place a threshold selection in settings and teach how to use it.

I feel like our discussions too often fall into the following pattern:

Me: we’re building a new thing called an automobile. It will get you from city A to city B. It’s awesome.

You: The bicycles I sell are great for getting around town. No one needs automobiles.

Me: ok. Let’s have both. Bikes for short distances, automobiles for long distances. It’s not either-or, it’s both-and.

You: For the specific use case that I’m focused on, getting around town, bikes are awesome. Therefore automobiles have zero use cases. No one will need them, ever, for anything.

🤷🏻‍♂️

Mate, you are misreading what I am saying, again. I haven't even mentioned Vertex, because it's not relevant in any way to this conversation. The provider is totally and absolutely irrelevant.

I am talking about HOW to display these ranks. I don't like the idea of displaying them, whether they come from Vertex, or Brainstorm, or whatever.

Design discussion.