Shared Ban List User Limit Increase
With the new Shared Listing rolling out, I immediately can see the 30 user limit being way too small for some communities, especially those with active-vigilant mod teams that are interconnected and share user information with one another. If the server is able to support it, raising it to 50 and steadily into 75 would be amazing just so we can have a larger network of mod support- and for the sake of sentiment, we look like we're even more supportive of each other :)
Agreed, 30 is way too low. If there is a technical reason why a maximum must be used, I think 300 is closer to reasonable. Think how many trusted friends you have on any social network. It's typically in the hundreds.
The Shared Bans release looks very promising. I think the idea makes a ton of sense and will be very useful in many many communities.
My one hang-up is the 30 relationship limit. It seems like a lot at the beginning, but I feel like you should have a separate arrangement for stream teams. Most stream teams would more than eat up that limit. Most of the people I would want to share information with would be in the same circles so the stream team would make the most sense.
If nothing else - you make it so that partners can have a much higher limit to accommodate the members of their team - then the members can match with the team leader and then pick and choose within the team who to share with.
I cannot imagine being a team leader and having to cherry pick who to share this very valuable information to.
Yeah, I think we're gonna need a lot more than 30 share relationships with the shared ban lists. Like, especially for BIPOC; LGBTQIA+; women. We're all going to hit the cap of 30 incredibly quickly.
Currently, we're only allowed to have 30 possible Shared Ban Info connections. This is great, but upping the number wouldn't solve a critical problem: large communities being targeted.
Rather than simply upping the number of possible connections, it would be great if a user could make their Shared Ban Info "public", allowing other users to subscribe to it. It would be a one-way connection, counting against the subscriber's total connections but not against the sharer
This would allow a community leader to effectively maintain a "master list" that could be easily shared with numerous people and should already work within the basic framework of what's been built.