Well yeah, people are changing frontends and warned others that Tesseract has that kind of blocklist and they don't support it. If people that used the tool didn't find out until now, it's mostly a communication issue from the dev. And to the user that knows none the wiser, opinions that they would've accessed if not for using Tesseract are essentialy not available. The option to turn it off is essentially hidden, and the user can't find out that information is being blocked (as seen by the reaction it caused in the threadiverse). It's censorship by omission of information. Even if they had good intentions, the way they went about it failed to communicate what the blocklist was about, and that information was being blocked in the first place.

It's also just kind of a silly thing to implement in a client. That's the perspective the memes are coming from. Usually, blocklists should be left to the instance administrators or users. The client should only easily allow such a list to be available.