Have you tried to comment in reply to @joe.public? When you do, you will find that your comment is invisible to you. The #irredeemables list doesn't just completely hide all @joe.public's comments and posts - which is why you don't see censorship - it hides your own comments from even you when made in reply to @joe.public.
For too long we have been censored and not noticed it. It's time Hive took control of it's speech from those that would make themselves the publishers of our words, determining who can speak, to whom, and what we are allowed to say.
This should not be done in darkness, but in the bright glare of our close attention.
But how is that even possible? Did he put some code into the blockchain during a hardfork to make it do that or how does it work?
A while back a spam war between @fulltimegeek and Bernie developed over a refund due @fulltimegeek which @themarkymark sent to @null instead. The #irredeemables list was created to totally censor all @fulltimegeek's accounts, and Bernie apparently now is able to use @themarkymark's sole option to control that #irredeemables list at will to censor anyone they want, without any limitation whatsoever.
I think the shortest route to the actual event referred to above would be to search for @themadcurator, which ceased posting around that time due to it's being a casualty of the conflict.
Stinc itself created the list, which prevents posts from listed accounts from being available to dapps using its APIs, (which includes all of them generally in use by affected communities) and now @themarkymark administers it for Bernie as best I can tell.
I remember that spam war!
If I recall correctly it broke out right around the day I tried to get some help from @fulltimegeek with doing Steem stuff in Java.
Horrible timing for me; he basically disappeared after that and I got no help from the only person I could find with any Java experience on Steem.
Wow. Was not aware of that backstory.