

Tech savvy would be to start your instances. Going through the process of picking an instance and registering there is no more tech savvy than registering with facebook or any other online site. The complexity keeping people away isn’t technical, it’s domain specific. People don’t know how to choose an instance because they’re not given enough information to actually tell instances apart.
As others have already pointed out, you can literally get the same result by using images as quotes. People could’ve been shitty even without the quotation feature because it’s not the feature on the platform that makes it shitty, it’s the people on the platform who decide to use it for a shitty purpose.
Not implementing a feature because morons may abuse it is not justification for not implementing a feature. It’s like saying we shouldn’t be able to reply to comments because someone might use that feature to directly send you hateful comments. Now, if the features primary purpose is (or primary use case ends up being) to use it negatively, then sure it shouldn’t be implemented. But I don’t see how quotation falls under this exception. In my eyes quotation is a net positive.
It doesn’t turn the platform shitty and if there are good moderators it also prevents assholes from trying to turn the platform shitty.