It is my feeling that sentiment analysis has a ways to go. Here are a few of the comments I've made that the system has described as among my saltiest:<p><i>Oh, sorry, "nm" means "nanometer" to me, but of course nautical miles.</i> (Score: -0.5. Comment is entirely taking responsibility for misinterpreting someone)<p><i>Well, if he was trying 1M combinations every 40 seconds, for $7 per hour, and he didn't need to use hundreds of dollars per hour of commute time, let's say 10 hours = $70. That's 900M combinations per hour, so 9B combinations in 10 hours. If he was trying combinations using upper-case characters, lower-case characters, numbers, and let's say 20 symbols, that's 82 possible combinations for each one. We'd expect him to find the password after exhausting half of the search set, so we want log base 82 of 18B. That suggests 5 characters. If he let's say just used lower-case characters and numbers, that's log base 36 of 18B, which suggests 7 characters.</i> (Score: -0.32. Comment is 100% technical, with no meaningful sentiment.)<p><i>Sorry, I submitted this article earlier with the wrong link.</i> (Score: -0.27. System appears to regard legitimate, largely bloodless apologies as salty.)<p><i>Note that the article is from approximately 20 years ago.</i> (Score: -0.24. This is to some degree a critical comment, but it's a short, straightforward statement of fact.)<p><i>Probably too late to reply, but I mean things like :ets.method or :queue.whatever.</i> (Score: -0.20. Probably it's cueing off the first phrase?)