Getting blocked at server level is more than “people that don’t want to see X”, it’s more complex than that. It’s more about server admins who do not want to see X and do not want to let others (others include everyone with their server addresses and other members of servers that federate with them) see X. The point here is blocking at server level propagates disruption of access to content down the chain of servers that federate with other servers.
This has implications for servers such as Medium as #Medium is NOT just another random server in the #Fediverse given its separate existence elsewhere on the #Web, so Medium on #Fediverse and #Medium on the web (call it ‘Mothership’) is expected to have a level of consonance to allow certain level of access to contents and policies. Each lives off the other and in the best of times respect the usage of each place where it operates.
For example, at this time, many people are exiting Twitter and setting up accounts on various #Fediverse servers such as #Mastodon sites, and if you traverse Mastodon accounts you will sense a tension between Twitter usage and content in #Fediverse. While it is a welcome sign to see Medium set up shop in #Mastodon, note that Medium allows only #Twitter integration with the ‘Mothership’ but users cannot log in to Medium with their #Fediverse credentials.
Besides, Medium IMHO should not blindly copy block lists as well. I hope you have these checks and balances in place @coachtony