A solution was developed by a community member, submitted, and was almost ready to go, but it was blocked as a "distraction" and "rearranging deck chairs" [- @sneak]
I found the rationale to be lacking, as you can read in the github pull request comments.
I guess everyone has their own vision and preference for what is important for a community. Hopefully, in the end it is the community that benefits.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
If you don't want to see the things that people resteem, then just unfollow those people.
Resteeming is a person choosing to repost in their own feed.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Why does it have to be absolute?
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Well, part of it is because the way resteems are indexed is done in
steemdright now, and all of that code is being moved out of the p2p daemon (and into a Python daemon, incidentally) to support communities. Any changes we make to the current setup would get thrown away within 90 days.We're also going to revisit the design and UX of condenser in the next few months (mobile is the priority at the moment, but condenser is getting a facelift too) and the best way to integrate this desire from a UX perspective will be investigated.
Basically, I'm not sold on the idea that the feature represents the interests of the user doing the resteeming. They chose to put it in their feed, so anyone viewing their feed should see it.
Even if we decide that it's a UX win to break it out, it will need to be done in
hivemindand not insteemd.Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thanks for the reply . Fair point about the feed and intentions of those who resteem. I am still desperate to see a filter on profiles though.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
The reason I closed the PR at the time is because our team historically was pretty unfocused, and it's been an extremely important struggle for us to gain focus on the subset of things that we would like to work on that are critical for our success, given our limited resources.
Imagine a list of about 50 valuable things we could work on. We have to work on the 7 or 8 we have the team bandwidth to perform, and those 7 or 8 have to be selected based on what's most likely to help the platform succeed in the long term.
This means that many completely reasonable things to do will not be addressed this year, deliberately and by design, because they are lower priority than things like signup, retention, et c.
If we don't keep focus on the things we must do to grow and thrive, and continue to allocate our extremely limited developer attention on to "nice to have"s, our present opportunity would be squandered. It's a matter of prioritization and focus.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit