3 ms·

I find it gross that dstftw (the core youtubedl maintainer) censored the part about youtube-dlc from that issue.

• theon144 6y ago
  CTRL+F'ing `youtube-dlc` comes up with several hits - was there more that is missing now?
  • dependenttypes 6y ago
    Check the edit history of the first post.
  • zo1 6y ago
    You can look at the edit history of that comment. You'll see that dstftw edited it to remove references to the youtube_dlc repo. https://github.com/ytdl-org/youtube-dl/issues/26462#issue-688126722 https://github.com/ytdl-org/youtube-dl/issues/26462#issue-68... Unfortunately, can't find a way to link to the edit in question directly. You'll have to click once there to see the diff.
    • saagarjha 6y ago
      Being able to edit people’s comments on GitHub is nice as a maintainer but removing information and completely changing people’s comments is really nasty. Any such effort should be clearly justified, preferably with a visual “edit message” that goes along with the smaller “edited” text.
      • u801e 6y ago
        I don't think that editing comments that you didn't make should ever be a feature. This is something that could easily be abused to make it appear that someone else said something they didn't actually way.
        • pfranz 6y ago
          I can see what you're saying in principle, but what if a bug is opened with "this stopped working for me" but evolves into a very specific issue? Should the maintainer open a new bug, link to it and close the old one? In practice, I find it really useful to tidy up the top message of a bug report (but /really/ like seeing history of it). I also see cases where users spam raw logs into updates and tidying it up (perhaps making the log portion an attachment or changing formatting) makes it much clearer for future-you and other collaborators.
          • yencabulator 6y ago
            Then there should be a "non-message" textfield up top, that doesn't pretend it's the original report, or forge its author.