3 ms·

Official author moved to GitLab and his commits are GPG signed with his key https://gitlab.com/dstftw/youtube-dl/-/commits/master https://gitlab.com/dstftw/yout

by agilob 6y ago

Official author moved to GitLab and his commits are GPG signed with his key https://gitlab.com/dstftw/youtube-dl/-/commits/master https://gitlab.com/dstftw/youtube-dl/-/commits/master

contravariant 6y ago
I wonder why they called it a "Temporary youtube-dl repository". Are they still planning to go back to GitHub if things work out?
- agilob 6y ago
  We can't open issues or PR there, it is a read-only repo.
  - Arnavion 6y ago
    TBH given the state that the issue tracker on GH used to be in, I would understand if they never opened up the issue tracker to the general public again. That issue tracker was a great way to lose faith in humanity, just from the sheer number of people who couldn't follow instructions to search for existing issues before opening new ones, or to provide all the answers the issue template asked for.
    - anuila 6y ago
      Open source is bad enough. When open source meets the general public you can enjoy a nice disaster cake.
      - londons_explore 6y ago
        A neat way to solve this is with a team of bug triag-ers. Get the developers to never look at a bug unless it has the "triaged' label. Then have trusted volunteers who read each bug, assist the bugreporters to get stack traces and whatever is necessary, dedup, and then finally apply the label. It's a good task for people who have some technical expertise but aren't yet confident to be submitting their own PR's.
    - julianlam 6y ago
      Sounds like something a bot could be set up to handle... Duplicate stack trace? Close and link. Missing relevant info? Close.
  - kristopolous 6y ago
    I'd like there to be a platform/plugin part where people host site patches and fixes and the user can integrate what they'd like. A decentralized approach. It supports dozens of sites btw. That's what I'm specifically referring to.
- kundi 6y ago
  Github MUST get it back. Otherwise this will initiate the potential collapse of their service
  - dewey 6y ago
    > Otherwise this will initiate the potential collapse of their service I think you are overestimating the amount of repositories that are affected by DMCA takedown threats (erroneous or legit).
    - jlokier 6y ago
      I think they're not referring to number of repos affected. I think they're referring to the stain on GitHub's reputation as a reliable place to host open source projects (controversial or not).
  - adkadskhj 6y ago
    It already is for me. I preferred other hosts tbh, but i was using Github mainly because it was a popular resume-oriented host for the projects i'd like to advertise as such. However given that i work on some P2P services that could be argued scrape and/or distribute, i'm heavily debating moving. A nice host for a potential employer to view is not worth being DMCA'd. I hope this causes a lot of additional desire to decentralize these portions of the dev workflow stack. Potential solutions exist, but no one cares.. i hope we collectively start caring more, and adopting solutions.
  - delfinom 6y ago
    Why exactly? Gitlab will take down the repo due to DMCA all the same. (Along with any other US ran service, and even many European ones) If you want to escape US law, feel free to use gitee.com located in China. Or, push your politicians to change the laws. Microsoft has no way of overcoming the DMCA law themselves, other major companies have continued to lose lawsuits. It doesn't help that mega monopoly entities like Disney want it to stay taht way and will bribe politicians and others.
    - 6y ago
- m-p-3 6y ago
  I could see them hosting their own git instance in a country where DMCA requests are worth jack-shit.
x0x0 6y ago
The commits aren't gpg signed though? The verified thing seems to be some weird gitlab stuff. eg if you clone that repo, and run git log --show-signature 34299510b git says the commit is unsigned. That said, I have been able to find clones of the youtube-dl repo elsewhere with HEAD 416da574e, and the 3 commits the gitlab repo adds on top of that seem innocuous. git log -p 416da574e..HEAD just shows a regex fix and then version bumps.

by agilob 6y ago

Official author moved to GitLab and his commits are GPG signed with his key https://gitlab.com/dstftw/youtube-dl/-/commits/master https://gitlab.com/dstftw/youtube-dl/-/commits/master

contravariant 6y ago

I wonder why they called it a "Temporary youtube-dl repository". Are they still planning to go back to GitHub if things work out?

agilob 6y ago
We can't open issues or PR there, it is a read-only repo.
- Arnavion 6y ago
  TBH given the state that the issue tracker on GH used to be in, I would understand if they never opened up the issue tracker to the general public again. That issue tracker was a great way to lose faith in humanity, just from the sheer number of people who couldn't follow instructions to search for existing issues before opening new ones, or to provide all the answers the issue template asked for.
  - anuila 6y ago
    Open source is bad enough. When open source meets the general public you can enjoy a nice disaster cake.
    - londons_explore 6y ago
      A neat way to solve this is with a team of bug triag-ers. Get the developers to never look at a bug unless it has the "triaged' label. Then have trusted volunteers who read each bug, assist the bugreporters to get stack traces and whatever is necessary, dedup, and then finally apply the label. It's a good task for people who have some technical expertise but aren't yet confident to be submitting their own PR's.
  - julianlam 6y ago
    Sounds like something a bot could be set up to handle... Duplicate stack trace? Close and link. Missing relevant info? Close.
- kristopolous 6y ago
  I'd like there to be a platform/plugin part where people host site patches and fixes and the user can integrate what they'd like. A decentralized approach. It supports dozens of sites btw. That's what I'm specifically referring to.
kundi 6y ago
Github MUST get it back. Otherwise this will initiate the potential collapse of their service
- dewey 6y ago
  > Otherwise this will initiate the potential collapse of their service I think you are overestimating the amount of repositories that are affected by DMCA takedown threats (erroneous or legit).
  - jlokier 6y ago
    I think they're not referring to number of repos affected. I think they're referring to the stain on GitHub's reputation as a reliable place to host open source projects (controversial or not).
- adkadskhj 6y ago
  It already is for me. I preferred other hosts tbh, but i was using Github mainly because it was a popular resume-oriented host for the projects i'd like to advertise as such. However given that i work on some P2P services that could be argued scrape and/or distribute, i'm heavily debating moving. A nice host for a potential employer to view is not worth being DMCA'd. I hope this causes a lot of additional desire to decentralize these portions of the dev workflow stack. Potential solutions exist, but no one cares.. i hope we collectively start caring more, and adopting solutions.
- delfinom 6y ago
  Why exactly? Gitlab will take down the repo due to DMCA all the same. (Along with any other US ran service, and even many European ones) If you want to escape US law, feel free to use gitee.com located in China. Or, push your politicians to change the laws. Microsoft has no way of overcoming the DMCA law themselves, other major companies have continued to lose lawsuits. It doesn't help that mega monopoly entities like Disney want it to stay taht way and will bribe politicians and others.
  - 6y ago
m-p-3 6y ago
I could see them hosting their own git instance in a country where DMCA requests are worth jack-shit.

x0x0 6y ago

The commits aren't gpg signed though? The verified thing seems to be some weird gitlab stuff. eg if you clone that repo, and run git log --show-signature 34299510b git says the commit is unsigned. That said, I have been able to find clones of the youtube-dl repo elsewhere with HEAD 416da574e, and the 3 commits the gitlab repo adds on top of that seem innocuous. git log -p 416da574e..HEAD just shows a regex fix and then version bumps.