@JeffSchaller Please don't rework the actual data, or at least not just new data. We do search through the why text data from time to time. Having some of the data in one format and other parts of the why data in other formats would make that substantially more complex. Changing the display of the data would be fine. Would it be sufficient for the display of the why data to be restructured similar to how FIRE displays it?
I've been intending to add that formatting to MS, at least as an option, but haven't gotten to it, yet.
Note: In experimenting with the formatting used to display the why data, I found it easier to quickly scan with the "position <character offsets>: detected watch/blacklist text", because in most cases that pushed the detected text out beyond the detection reason horizontally, which made it easier to scan, almost as if it was a separate column.
@tripleee Please define which data you feel is crucial and define highlighted. Are the ones you feel are crucial for you crucial for everyone (not saying that your desires are any more or less valid, just pointing out that I believe there is variation in what people think is important in that data; I've toyed with being able to allow users to define their own formatting)? What, other than bold (which is what FIRE currently does for both the detected text and watch/blacklist reason names), would you want for highlight formatting? Using lots of formatting tends to very quickly get quite noisy. In development, the FIRE formatting did try using some additional highlighting and formatting for other reasons, but it fairly quickly became harder to quickly glance at it and see at least the data I was interested in, which was the watch and blacklist detections.
[ SmokeDetector | MS ] Blacklisted website in body, link at beginning of body, potentially bad ns for domain in body, potentially bad keyword in body, potentially bad keyword in username, +1 more (213): Commercial Association Management by LivinginTown on es.stackoverflow.com
The quota_remaining property was not in the API response. Error: no method found with this name at 14:53:10 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:53:59 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:13 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:27 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:42 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:57 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:55:11 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
@SmokeDetector Ha! I had an error on my machine when accessing the SE API at the same time. Finally confirmed 100% that it's not just SD. The response text from the SE API was:
{"error_id":404,"error_message":"no method found with this name","error_name":"no_method"}
For the request from my machine, the response status was 400, with statusText: "Bad Request". The request was a GET with URL: https://api.stackexchange.com/2.3/posts/74602372?site=stackoverflow&filter=!6Ej2_CgmrX5)M.Re9-.fPyFSl2tFcpjZg8yP6diQYcnc-u0LWz.FvWIhd-d&access_token=<valid access token>&key=<valid API key>&_=1669620009465
