Sometimes I want to see resteems. Sometimes I don't.
Update in the works for the Steem Curation Extension.
I thought this would be a quick diversion before I start digging into author and reach metrics for the curation overlay.
Now you see them
Now you don't
And the checkbox/toggle disappears on pages with no resteems:
That was the next thing I was planning to include in Condenser 😊 So yes, I think it’s useful 😊
I was wondering when an extension change would collide with a condenser change like that.
Guess I'll deactivate that feature from the extension after it's available on condenser sites.
Chances are that I’ll try to implement most of your features - they’re all an improvement upon what we currently have 😊
That would be cool. Then I can add "front-end design" to my resume? 😄
I actually imagined a feature lifecycle like that some months ago. Rapid prototyping in the browser extension and then popular features get ported into condenser. The only challenge is that it creates pressure to find good new ideas for the browser extension.
Maybe it would be more "Product Manager" 🙂
I implemented most of the feature today. Unfortunately, it clashed a bit with my "pinned posts" carousel. Fortunately, it highlighted a bug in my "pinned posts" carousel. Very much an edge case, but a bug nonetheless.
I think that most of the features you're implementing should be ported. The percentage RC is available on Hive - a subtle ring around the user's avatar. I believe that the "Hide Resteems" equivalent is available on Blurt although I rarely look at either site to be confident of this.
I have wondered about looking at their codebases on GitHub to see if there's anything they've implemented that would be easy to port across but I don't think there is.
I don't go to either one very often, but I happened to see recently that blocktrades was talking about a new front end called "denser". So, they're apparently forked pretty far away now.
Yes, I think the option to switch off resteems is useful.
But I still don't know how I should deal with my personal needs.
In principle, resteems are not bad at all: if it's about special or very important articles or about making a new, obviously good user known who you would otherwise never meet within your little bubble. That's why I would leave resteems switched on. BUT: I have already pre-sorted. I only follow users who don't overdo the resteems. Anyone who forwards something every day, who forwards the contests or challenges (because it is sometimes even required - really annoying!) has NO chance of being followed by me.
Can I use your tool to distinguish between unimportant and important resteems...?! ;-D
That would be a useful enhancement. The "Steem mind-reading extension"😉. Long term, I suppose it would be possible to provide more useful filtering than all or nothing, though. Account lists could be maintained, for example, to filter resteems of posts from accounts that require resteems for their contests - similar to how ad-blockers maintain lists of advertising sites. This hadn't crossed my mind, and maintaining such a list is beyond my reach as a part-timer, but I'll keep this need in mind for future possibilities.
AI meets Steem. Steem meets AI. Steem is AI. Handmade AI... ;-)
Good idea. I feel the same way, sometimes resteems are interesting, sometimes not. I would leave resteems switched on by default and switch them off if necessary. So yes, I find this option useful.
Right now I have it set so it remembers the last setting if you leave the feed and come back again, so it doesn't currently have a "default-on" or "default-off" setting. I wonder if it makes sense to have another option to save the current setting as a default or if that would be overkill.
@the-gorilla may want to consider this point for his condenser implementation, too.
Oh, I thought there was a default setting with which the extension starts. If it remembers the last setting, great, that's all we need, I think.
Whenever I implement a default, it's usually the current implementation within condenser. For the "Hide Resteems", I'm torn between it just being stored in the session state (i.e. lost upon a page refresh) or within local storage (i.e. retained even when the user closes the browser). My implementation is fairly prominent though (same as Blurt IIRC) so it'll be clear which option is selected.
Ah... I just looked at blurt. I spend even less time looking at that site than I do at hive. I see now that I also need to add the show/hide resteems option to the blog page... I hadn't even considered that. Or else just wait for you to do it in condenser.😉
The default is tricky. I like being able to save the last setting between visits, but I could argue for a default setting, too.
I resteemed you ROFLMAO