-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teamliquid's new domain tl.net usage broke the corresponding plugin #2416
Comments
This is just a simple regex change, unless they've changed their site's layout. The plugin also still uses the deprecated logger calls and needs to get updated. Btw, what is the policy on these kinds of wrapper/proxy/alias plugins? I can remember that we had a discussion about this a few months ago, but I can't find the thread. Doesn't this technically violate the third point here?
My personal opinion is that these plugins are rather pointless, but at the same time they've existed for a long time now and there are people who are using them. |
@bastimeyer From what I remember the only reason we kept any of the teamliquid stuff was basically because it was grandfathered in. One of us (probably me since I hate this sort of rehost bloat and I'll happily take the heat) brought up getting rid of these specific types of plugins during some discussion and we came the the conclusion we would allow old plugins to stay, but wouldn't permit future restream plugins like this to exist. If we ever want to bring down the hammer I'll be happy to put teamliquid and vaughnlive as number one on the chopping block. |
There's a major issue now where teamliquid's new domain tl.net usage has completely broken the corresponding plugin:
The text was updated successfully, but these errors were encountered: