youtube-dl
oauth2-proxy
youtube-dl | oauth2-proxy | |
---|---|---|
28 | 98 | |
285 | 8,712 | |
- | 2.1% | |
0.0 | 9.0 | |
over 1 year ago | 3 days ago | |
Python | Go | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
youtube-dl
-
ERROR: urlopen error [Errno 11001] getaddrinfo failed
Notes: I'm not using vpns. I'm using a special version of ytdl designed for niconico. It has not been updated in over a year: https://github.com/animelover1984/youtube-dl
-
Youtube video analysis with youtube_dl inconsistent, sometimes giving errors
You might get more consistent results with a fork, most of which have already fixed this issue. Some popular ones are yt-dlp/yt-dlp, blackjack4494/youtube-dlc and animelover1984/youtube-dl. Please note though these might not be drop-in replacements
-
youtube-dl is (possibly) dead
Months before the lawsuit, there were plenty of people complaining that youtube-dl's maintainers closed issues without any reason given. Here is one illuminating example:
https://github.com/ytdl-org/youtube-dl/issues/23860
And there is also an entire fork that fixes the support for just a single provider, Niconico, because the maintainers ignored its issues.
https://github.com/animelover1984/youtube-dl
A quote from its README:
All code in this project is licensed solely with the condition that any portion of it is not permitted to be used in the main youtube-dl fork, either directly or indirectly. It is also not permitted to be used in any project that contains contributions from either remitamine or dstftw.
It seems that youtube-dl was a dysfunctionally managed project at the time of the lawsuit, and happened to ride out on the good PR for a couple of months, before returning to stagnation once again.
To me it sounds like a plugin system would have prevented centralization and the need for forks, but would have made distribution harder for average users.
-
Horahora: youtube-dl Frontend for Niconico, Bilibili, and Youtube
It does, I wrote the tool. I started https://github.com/animelover1984/youtube-dl to add features for Horahora.
-
downloading niconico videos problem
animelover1984's fork have a unique niconico extractor, supports livestreams
-
Niconico videos don't download because of Unable to find video URL error
In addition to animelover1984/youtube-dl, non-live videos work with yt-dlp as well
-
Having trouble with youtube-dl fork.
Hello. I'm currently trying to download some Niconico videos that will be deleted at the end of this month, using this fork of youtube-dl. However, when I try to run a command, I get this error:
-
Bilibili Playlist Downloading
Bilibili doesn't have playlists afaik. Do you mean channels/anthologies? If so, both animelover1984/youtube-dl and yt-dlp can download them
-
niconico / nicovideo.jp no longer working?
Other than animelover1984/youtube-dl, yt-dlp also works
-
How can I install animelover1984's youtube-dl branch on Windows?
Also, if you already have git installed, the easiest way is py -m pip install git+https://github.com/animelover1984/youtube-dl
oauth2-proxy
-
Keycloak SSO with Docker Compose and Nginx
Recently I looked into having a relatively simple SSO setup for my homelab. My main objective is that I could easily login with Google or GitHub auth. At my previous job I used both JetBrains Hub [1] and Keycloak but I found both of them a bit of a PITA to setup.
JetBrains Hub was really, really easy to get going. As was my previous experience with them. The only thing that annoyed me was the lack of a latest tag on their Docker registry. Don't get me wrong, pinned versions are great, but for my personal use I mostly just want to update all my Docker containers in one go.
On the other hand I found Keycloak very cumbersome to get going. It was pretty easy in dev mode, but I stumbled to get it going in production. AFAIK it had something to do with the wildcard Let's Encrypt cert that I tried to use. But after a couple of hours, I just gave up.
I finally went with Dex [2]. I had previously put it off because of the lack of documentation, but in the end it was extremely easy to setup. It just required some basic YAML, a SQLite database and a (sub)domain. I combined Dex with the excellent OAuth2 Proxy and a custom Nginx (Proxy Manager) template for an easy two line SSO configuration on all of my internal services.
In addition to this setup, I also added Cloudflare Access and WAF outside of my home to add some security. I only want to add some CrowdSec to get a little more insights.
1. https://www.jetbrains.com/hub/
2. https://dexidp.io/
3. https://github.com/oauth2-proxy/oauth2-proxy
3. https://github.com/alex3305/unraid-docker-templates
-
Multi client authentication with auth0 and oauth2-proxy
Authentication providers like Auth0 and Okta have become commonplace in software development. These providers help take this work off of your plate, and this can be made even easier by using a reverse proxy that provides authentication capabilities, like oauth2-proxy.
-
Why You Should Migrate to OAuth 2.0 From API Keys
There's also other problems you might run into when using JWT: - First using scopes for permissions like Slack does can generate a token so large that a server might refuse it (One of many examples: https://github.com/oauth2-proxy/oauth2-proxy/issues/644, any rational server won't allow unlimited sized header), in my company they did this with the convention of read:team:product:resource but if you're an admin and have every rights by default, then you can't use the generated token by default as it will be too large. I think Quarkus works that way and you might encounter some problems with you don't configure it correctly. - Second is that it will cost a lot of bandwidth to send this header each time you're doing something, and probably won't be the perfect answer for what you want to do (do you really have third parties calling your API ?) - Third is about security concerns, you might say that having your permissions in a token is not as bad as you might think but in case of a Man In The Middle attack, you could leak information about your company, process or business intelligence that could have been prevented. - Fourth and that'll be the last, is that you can't revoke a JWT. And if you say you can, then you don't need a JWT at the first time because it would defeat the principle of a self contained JWT.
-
Moving from Google workspace to Microsoft 365 and implementing Zero Trust
That is not how you do Zero Trust. You want to use an Identity Aware Proxy. There are lots of ways you can implement this with Google as your core auth. For example Pomerium or oauth2-proxy.
-
Microsoft launches Windows App for accessing PCs in the cloud from any device
I use self-hosted Apache Guacamole (RDP) through a reverse proxy with Google SSO (oauth2-proxy[0]). So easy to access my desktop from virtually any browser (mobile isn't the best though). This would be a good solution for gaming, but for other activities RDP is unbeatable imo.
[0] https://github.com/oauth2-proxy/oauth2-proxy
-
Best Practice For Serving Static (Frontend) Files with NGINX in K8s?
Meet https://oauth2-proxy.github.io/oauth2-proxy/ It could be deployed in the cluster somewhere and reuse it where needed. We do this to authenticate prometheus,alertmanager ui for useres
-
Any thoughts on implemented access control of self hosted front end apps?
At work, I've used oauth2-proxy as a sidecar container (on Kubernetes) for an app that has no authentication mechanism. Pretty straightforward, works well. I think this or Authelia is your best bet.
-
Authentik reverse proxy vs swag
BTW also keycloak and other similar products offer the oauth-proxy capability, I even used the original oauth2-proxy https://github.com/oauth2-proxy/oauth2-proxy for a while, but it was getting too difficult to maintain for me. I used for a while https://github.com/thomseddon/traefik-forward-auth that was a smart hack configuring a single upstream provider, but it look abandoned. So I was considering authentik but apparently it's just oauth2-proxy embedded in it, at that point why not use oauth2-proxy directly.
-
How to build Auth in 2023 with go?
Like auth basic? Mate, its 2023 get that RestAPI endpoint behind an OAuth proxy. github.com/oauth2-proxy/oauth2-proxy is a good one on a budget or use some cloud provider's ApiGateway and IAM services.
-
Pomerium or Authentik?
I use it in combination with oauth2-proxy, which sits in front of my network and the various services I host. https://github.com/oauth2-proxy/oauth2-proxy
What are some alternatives?
yt-dlp - A feature-rich command-line audio/video downloader
traefik-forward-auth - Minimal forward authentication service that provides Google/OpenID oauth based login and authentication for the traefik reverse proxy
spotify-downloader - Download your Spotify playlists and songs along with album art and metadata (from YouTube if a match is found).
vouch-proxy - an SSO and OAuth / OIDC login solution for Nginx using the auth_request module
twitch-dl - CLI tool for downloading videos from Twitch.
authelia - The Single Sign-On Multi-Factor portal for web apps
Simple-YouTube-Age-Restriction-Bypass - A simple browser extension to bypass YouTube's age verification, disable content warnings and watch age restricted videos without having to sign in!
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
funimation-downloader-nx - Download videos from Funimation via cli.
Docusaurus - Easy to maintain open source documentation websites.
udemy-dl - A cross-platform python based utility to download courses from udemy for personal offline use.
caddy-auth-portal - Authentication Plugin for Caddy v2 implementing Form-Based, Basic, Local, LDAP, OpenID Connect, OAuth 2.0 (Github, Google, Facebook, Okta, etc.), SAML Authentication. MFA with App Authenticators and Yubico.