RE: Steem Curation Extension: New version available with more info for curators

You are viewing a single comment's thread from:

Steem Curation Extension: New version available with more info for curators

in hive-151113 •  6 days ago 

What I noticed, if SHOW RESTEEMS is disabled, posts from accounts I follow will be hidden if they have been resteemed.

I've just started to implement this for my next condenser release and hadn't considered this. Thanks for highlighting it 🙂 That could be a bugger to fix on condenser... although a simple rule of "don't hide if post author is followed" feels simple in principle... and in theory, this list should be available to the page because the "following list" is required to retrieve the feed 🤔

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:  
  ·  6 days ago 

in theory, this list should be available to the page because the "following list" is required to retrieve the feed

I don't think that's necessarily available at the condenser layer. I think the following list is sorted out by the blockchain or hivemind, 'cause you can retrieve someone's feed using "curl" or the get_feed API call. If curl doesn't need to know the follower list to show a feed, I guess condenser doesn't either(?).

My work-around was to check if the feed owner follows the resteeming account using the get_following API call, and then to cache the answer for 30 minutes to limit network calls, but I'm not sure if that's really feasible in condenser. I'll be keeping my eye out for a better solution in the browser extension, too.

Fortunately, it's at condenser level. The component is already calling the "getFollowingAsync" which stores the muted accounts:


const mutes = state.global.getIn(
['follow', 'getFollowingAsync', username, 'ignore_result'],
List()
);

So I can use this to get the accounts followed too:


const following = state.global.getIn(
['follow', 'getFollowingAsync', username, 'blog_result'],
List()
);

Which works great for my own feed...

image.png

But since it's querying the username and not the person's feed... ah... I've thought of the answer whilst typing this (I think)...

  ·  5 days ago 

Hivemind has to insert the resteemed posts into the user feed at great effort, and now you want to remove them again at condenser level. That's not nice... ;-D

In my opinion, the most efficient solution would be to introduce a parameter in the feed query that returns the feed without resteems. I don't know right away whether we would then be able to switch quickly. But I would assume so.

Hivemind has to insert the resteemed posts into the user feed at great effort, and now you want to remove them again at condenser level.

Ha ha! Yes. That's exactly what I want to do 😉

The code's should be pretty quick since the "following feed" appears to be in the state and all I'm doing is adding / removing a CSS class during the render.

I've nearly got it working... hopefully tomorrow I'll be able to complete the task 🙂