Literally nobody asked for this to be removed. This is yet another dumb decision to remove something that caused no inconvenience to anyone.

I'm quite glad this post blew up, and people are 100% with smaller streamers with so much positive feedback, and I hope Twitch does listen and actually roll this stupid decision back. They don't need to intervene with how many people are in raids/hosts notification feeds as that can all be done on the Streamer's side with their Alert Notifications by setting the minimum for their alerts, these features are already available in Streamlabs, Streamelements, Muxy, Nightbot, Moobot, and many others, it doesn't need to be enforced on Twitch's end.

For everyone else who sees this post, please do reshare it, and upvote it, because this severely impacts smaller streamers.

I highly recommend this, if we streamers can just import a list of names to ban from the channel, preferably in JSON format to make it easier when importing names from a list it would make a huge difference and effort to thwarting problem users who come in mass to troll raid.

The reason I recommend JSON format is so that when you import a list of names to be banned, you can also include the ban reasons alongside those names you're importing, and it's a very easy clean way of doing things. ie;

{
"username": "john_doe123",
"ban_reason": "Bot spam"

}

Here's a better fix to the issue that still persists. Temporary fix to add to Stylus or GreaseMonkey.

.channel-root + .persistent-player[style] {
top: 0px;
left: 0px;
position: absolute;
width: 100%;
max-width: calc(100% - 0px);
max-height: calc(100vh - 130px) !important;
overflow: hidden;
z-index: 1;
height: auto;
transition: transform 0.5s ease 0s;
transform-origin: center top;
transform: scale(1);
}

Just to iterate, I'm not a CSS wizard, I just took what I knew and applied it to that to overwrite the site's default using a browser extension. Maybe Twitch can apply this as a full proper fix? since the person who wrote the code before isn't good enough, and uses far too many `!important` elements to their CSS code which is really unnecessary, because it's like you're trying to compensate for something which overrides previously defined elements for objects on the page.

bump this idea up

They had this feature before, but it never worked because Twitter kept changing it's API and broke it.