You have zero quantitative evidence that implementing a built-in parser in high-end duties will increase or decrease the amount of negativity already present in this game. The "pro-parser" posters in this thread have all achknowledged that, more than likely, things are going to remain just as they are, where as the "anti-parser" posters continue to act as if implementing a built-in parser in content where it matters is the equivalent to the end of the world, and that suddenly the amount of twats and toxicity is going to increase one hundredfold.
The only posters I have seen acting remotely negative in this thread are those against parsers, but they have yet to give any evidence to back up their claims outside of anecdotes. Because such evidence does not exist--they cannot see into the future, and see that people are going to just start kicking players because of a bad parse. Jerks will continue to be jerks, whether or not they have a parser to publicly use or not. Built-in parsers are not a green light for harassment. GMs would still continue to take action against any and all who are reported with sufficient evidence of harassing another person. That isn't going to change just because of a toggable feature in PF. Criticism isn't a form of harassment when delivered constructively, and if a person doesn't like parsers, don't join a PF where it's displayed that a parser is going to be used. Just like you wouldn't join a Lootmaster party if you dislike Lootmaster. It's that simple.
All of these are already punishable offenses now, although the first one has to be extremely cut-and-dry for it to not just be considered "differences in playstyle" (e.g., chat log evidence of a conspiracy to kick someone "because they are not good enough"). Regarding PFs, the party leader is allowed to set whatever restrictions they want; it's their PF. Regarding FFLogs, players can claim their character and opt to have all publicly uploaded logs hidden, as far as I'm aware.
This exclusion already happens. If you look in PF, there are plenty of parties that exclude: players under the minimum ilvl set by the PF leader, jobs the PF leader does not want in their party, players that have not cleared the duty trying to join groups looking to farm. The list goes on. And, in private parties, the leader is allowed to set whatever rules they want--it's their PF; not a DF group. That's why those options to limit jobs and set an ilvl requirement exist.This is the only way to make the parser safe. But most of you will argue with the "why I can't kick the under-performing player?". If you think this, you DON'T WANT a parse to see statistics and help improve, you want it to exclude people.
Not to mention, the "high DPS or kick" parties already exist. And they will always continue to exist, parser or no parser. It's not like the implementation of a parser is going to change their existence, and neither side can prove it will be an increase or decrease. Again, you cannot prove implementing a parser is going to suddenly increase the amount of harassment that already takes place. Nor can you make mass assumptions like the last paragraph of your post:
You don't have any evidence to back those claims up; so they really equate to little more than fearmongering.The majority of player base consider good being able to beat a duty, not the damage deal on them. Most people come to play and not worry much about things. Making a tool that can be potentially used to cause a negative atmosphere will cause that player stop play this game. Since majority are ignoring the parsing, the amount of player that can be lost due this will cause a heavy lost in money for SE. it is not only morality and education, it also also economic. Those player you mock, harass, kick because number are paying this game too. If they stop play, you know what will happen. A player who cannot play or is discriminate will stop play. They won't think "oh, maybe I can improve my DPS and I won't be kicked!", most of them they just stop play.