[ SmokeDetector | MS ] Bad ip for hostname in answer, bad keyword in link text in answer, blacklisted website in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (274): Optimum Bluetooth range by Jamie Biswas on superuser.com (@Ollie)
@tripleee That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command if you really want to add the pattern you entered.
@Makyen mixed feelings, I like having code which is narrow enough to comfortably browse on various devices but the 120-character limit is neither here nor there; if we want to use it, the standard is still 80
@SmokeDetector Link to YouTube is to a video posted today with no views. There's at least a partial match between the username on SO and the name of the video author. While they might have a real question here, the question's effect and intent appears to be to drive traffic to the two videos which are linked.
@tripleee Yeah, the standard is 80. However, I'm strongly opposed to enforcing narrow line widths below what can be comfortable displayed on a fairly wide monitor. While there are benefits to having narrow line widths, my opinion is that enforcing narrow widths makes for less readable and less maintainable code.
Enforcing quite narrow lines commonly results in the programmers making choices to use shorter representations for the code in order to make it fit into a line without the need to deal with wrapping a line. One of the areas where this is quite noticeable is when selecting variable names. Short line lengths tend to get programmers quite used to using cryptic variable names instead of a variable name of reasonable length that indicates what the variable is/contains.
Using descriptive variable names is a significant step towards self-documenting code. Having the code be self-documenting makes it much easier for someone to pick it up later and update/maintain it after it's initially written.
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad keyword in answer, potentially bad keyword in username, username similar to website in answer (164): Android Studio virtual device not working by Genu Venue on superuser.com (@Ollie)
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add the pattern you entered.
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add the pattern you entered.
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add the pattern you entered.
[ SmokeDetector | MS ] Pattern-matching website in body, potentially bad keyword in body, potentially problematic ns configuration in body (98): Product Review Sites by user17643285 on stackoverflow.com
@tripleee That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer Append -force to the command if you really want to add the pattern you entered.
@tripleee That pattern looks like it's already caught by Blacklisted username Append -force to the command if you really want to add the pattern you entered.
