Summary

When user 'A' blocks user 'B', user 'A' is being served the boosts from user 'B'.

Steps to reproduce

1. Block a user
2. Go to Newsfeed
3. Boosts from that user persist

What is the expected correct behavior?

Boosts should be blocked too.

Relevant logs and/or screenshots

https://www.minds.com/newsfeed/1002258011014168576 https://www.minds.com/newsfeed/1031185109487849472

added scoped labels

added scoped label

assigned to @edgebal

unassigned @edgebal

Unable to replicate, although I appreciate the urgency.

I made a boost locally, approved it, logged into a second user and blocked the boosting account - I no longer see the boost (as the env is scaled down there's only a few posts in the rotation at the moment).

Open to ideas or suggestions of what may have caused it, what activity types have been boosted etc so that the dots can be connected.

added scoped label

We'll have to keep isolating -- lots of users have reported this periodically. I'll add links as I come across them. eg: https://www.minds.com/newsfeed/1007592353455951872

I think the best option is to please do keep them coming. @brianhatchet's upcoming changed to the RBAC stuff should really make all of this work, quite well I believe (correct me if I'm wrong Brian).

So I think these bugs should just vanish in a matter of weeks.

assigned to @benhayward.ben

This is in this sprint, but whether it gets fixed this sprint is another matter, im gonna have to put effort into trying to replicate. So far no luck.

changed weight to 3

https://www.minds.com/newsfeed/1008717805662629888

mentioned in issue minds#744 (closed)

minds#755 (closed)

mentioned in issue minds#755 (closed)

minds#755 (comment 206460413)

added scoped label

What do you think @brianhatchet?

It's definitely happening, but what sort of timeframe are we looking at for the RBAC changes? We could add some front-end validation around the area.

Definitely covered in RBAC and definitely has to be done by next sprint. I'll move it onto the next sprint and assign it to myself

Closing in favour of that then

closed

reopened

Not fixed

Sorry, should have specified where it will be fixed instead of here.

&28

Feel free to keep it open if you want to keep an eye on it, but its not a card that I think will be picked up by a developer, as the solution is encompassed in that epic.

changed the description

@benhayward.ben @brianhatchet Take a look at this: https://www.minds.com/newsfeed/1031185109487849472

unassigned @benhayward.ben

Okay, this will happen once in a while for me if I dont REFRESH my browser directly after applying the block.

Firefox 68.4.1 esr

That kind of edge-case would make sense. Without navigating away from the feed also?

changed milestone to %Sprint::02/12 - Bartone Baboon

removed milestone

More reports:

https://www.minds.com/newsfeed/1074743303341051904 https://www.minds.com/newsfeed/1075072612853043200