Hello, yes that was my expectation and the reason I opened this discussion :)

It wouldn't be hard to hide child comments. Very simple recursion. I think it's another reason related to concerns about the first person providing false information, etc.

Hi, got it! :) Here's an AI generate suggestion:

To hide child comments in GitHub discussions using recursion, you can write a custom script or use a browser extension that modifies the page's CSS or JavaScript. Here's an example of how you could implement this using JavaScript:

1. Open the GitHub discussion page where you want to hide child comments.
2. Open the browser console by right-clicking on the page and selecting "Inspect" or by pressing Ctrl+Shift+J (Windows/Linux) or Command+Option+J (Mac).
3. In the console, paste the following JavaScript code:

function hideChildComments() {
  // Select all comment threads
  const commentThreads = document.querySelectorAll('.js-comment-container');

  // Iterate over each comment thread
  for (const thread of commentThreads) {
    // Get the depth of the comment thread
    const depth = thread.dataset.commentDepth;

    // Check if the comment thread is a child comment
    if (depth > 0) {
      // Hide the child comment
      thread.style.display = 'none';
    }
  }
}

// Call the function to hide child comments
hideChildComments();

This script will select all comment threads on the page and check their depth. If a comment thread has a depth greater than 0, indicating that it's a child comment, it will hide that thread by setting its display style property to 'none'.

Note that this approach relies on the current structure and class names of GitHub's discussion page. If GitHub updates their page structure, this script may not work anymore.

Also, keep in mind that modifying the behavior of a website using custom scripts or browser extensions may violate the website's terms of service. Use this script responsibly and ensure that you comply with GitHub's terms of service.

Please never answer someone else's question using AI. Not only is it not genuine, but it is often inaccurate. This is an inaccurate situation. Refreshing the webpage after changing stuff in the developer console would return it to normal. The content is served from the server, and changing stuff in the developer console only changes the local copy. That server provides a new copy when the page is reloaded. Again, please never answer someone else's question again using AI. It is not only not genuine but also inaccurate. It is better to let someone else answer than you answer using AI.

My intent was to try and use resources openly available to help. I am new to entering the Discussion chats here on GitHub and I appreciate the etiquette lesson. Message well received.