-
Notifications
You must be signed in to change notification settings - Fork 122
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
Please remove the CocoaPods ping #96
Comments
Adding the offending code for reference: LLDebugTool/LLDebugTool/DebugTool/LLDebugTool.m Lines 184 to 209 in 5775a43
The condition is defaulted to LLDebugTool/LLDebugTool/DebugTool/LLConfig.m Line 112 in 750ed3a
|
You can set |
Heh, yeah, I banned your pod page from showing on the CocoaPods website - basically someone shipped your pod to production and we get taken down by their users :D |
@orta I see. Thanks, My mistake, I will remove it tonight and release it on next version. 😆 |
@orta One more question, When I removed this code, Could you cancel banned my pod in future? I just wanted to push the new version to the user and add a property to turn it off. I don't think my pod has such a large number of users that would cause DDS attacks on Cocoa pods. So maybe cancel banned my pod in future? 😢 |
I'm not part of CocoaPods, just a random opinion: Technically, I believe you can have multiple podspecs files in the same repository, so that both the old pod name and the new one would get updates until a safe version gets largely adopted. |
Yeah, I'm open to removing that code but it's at many requests per-second today. It'll take a long time for developers to update your library, then to update their apps, then for users to update their apps. I have no idea when I can undo it though - perhaps once it starts looking like a request a minute or two. |
@orta I see. Thank you for telling me this. I'll fix it as soon as possible |
@orta I'm removed the CocoaPods ping and release a new version, How long will |
months, maybe years - depends on how fast people update really. |
So badly..... Does this affect people's ability to search and install my pod through cocoapods? |
@orta Is there no other way to solve this problem? |
Nope, not really - to give you some perspective: for every 1 normal website page view we get about 20 pings from this code (see the screenshot above) @Coeur's point that you can re-name your library is honestly one of the best ideas |
@orta Will this affect when For individual developers, the loss of renaming is too great. 😭 |
I believe the code Orta added only blocks your page on the CocoaPods website and not in trunk so install, etc should work. It’s probably easiest to try for yourself on a blank project :) |
Just the web page is blocked, everything else is the same |
Okey, All I can do is wait. |
Hi!
I think people are shipping this check to production devices and have been the cause of downtime on the CocoaPods website quite a few times. Last year I added code specifically to remove your pod from the website: http://cocoapods.org/pods/LLDebugTool
I don't think I can ever remove that code now, but at least you can remove the check to give our servers a chance to be less busy
The text was updated successfully, but these errors were encountered: