803 karma · joined October 21, 2018
Placing a fuzzy tester like "hypothesis.strategies.characters" into the CI may also be revealing.
Just because it is technically possible, does not mean it is socially a good idea. Members and server owners should decide what can and cannot be done with their data. If you want a Mastodon server without limitations for experimentation, you can create one, and people can join if they consent.
25 years, now with preview images in file picker :)
If the user is faster, you can show something like cloudflare does when you visit through Tor.
On later submissions you can reuse the reputation from the cookie.
Respond by specifying clearly what would be required for this feature to land in your code.
This can be money, this can be someone stepping up to do it and maintain it, this can be technical requirements under which you can see this go into your framework. Yes, users opening issues are demanding, but as a github repo owner you can ask for anything as well and put up barriers that the user needs to solve to see it happen. They may be motivated too.
Specifying clearly the problems and what is needed to overcome them leads the user to appreciate you more. It will sharpen your thinking on why exactly you are saying no. And sometimes you will be surprised by someone actually making you happy by meeting your requirements.
You and OP ("the indians labelers don't know how to do it correctly") seem to want the former, so it would be good to state that goal upfront.
I wonder if that person ever took a CS class on ethics and the connection of computing and society, their compass is way off. But keep smiling into the camera.
A more interesting question would be how to build incentives in a winner-takes-all election system towards reducing gerrymandering, and to discuss what it would take to change away from a winner-takes-all geographical election system.