-
Notifications
You must be signed in to change notification settings - Fork 94
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
Myfreecams #74
Comments
Yup, Someone decided to e-mail tech support and this was their response. "Our systems have detected you may be using a third party script to perform automated actions on MyFreeCams. |
Anyway to fix this ? I just had my ISP change my IP Address . for now |
Probably mfc implemented a protection against recording. |
ya there are alot bots on that site |
UWC must be doing something different from the normal web access to allow them to detect and block it. I know we are faking being a mobile device, I assume for a simpler API. For me sometimes it works sometimes I am blocked in Kodi for days. |
While I was watching The Boys on my Shield, I decided to try the site again on my laptop. I clicked on one cam and it ran for ten minutes without getting that message. I stopped that cam and clicked on another cam and it ran for 25 minutes before she logged off. I didn't receive a message. It could've been a trial run by MFC. Did they stop it because of their bottom line or analyzing their test run? @jdoedev123 as I stated before, I'm not that familiar with coding but have some tech experience. Can they detect that key strokes are not being made when accessing their cam girls? When I googled what that error meant, there was a user who admitted to recording their live streams for hours. Just my two "still trying to comprehend" cents... |
So this has been my experience so far So then I just change my IP and it's fine until I use the add-on again |
It seems my free cams is getting smarter
They keep blocking the feed and and telling me to call myfreecam support
It seems they're seeing my IP address
The text was updated successfully, but these errors were encountered: