Leaderboard

I have most of my VM's set up to access a "shared" .vdi "hard drive". So my VM x86 was seeing everything at "E:\ProxHTTPSProxy_REV3e_PopMenu_3V1" whereas my host machine (x64) was seeing everything at "C:\Documents and Settings\Admin\Desktop\ProxHTTPSProxy_REV3e_PopMenu_3V1". I think we can all be on one PM. That way none of us report something we find that somebody else already found.

I'm personally of the view that some sort of local proxy is the ONLY way to solve the Cloudfare issue. A local proxy that can "appear" to be anything we want it to "appear" to be. Which FAR exceeds some third-grader knowing how to spoof a User Agent. It's above my skill level though

And to think many folks used to spoof FF 99 to "future-proof" their UA spoof. So, FF has finally caught up to Chrome version numbers. (Well, almost. My BlackBerry Priv is at Chrome V101.) Congratulations Does that mean they're going to slow down their version cycle now to stay in sync, or does that mean Chrome is going to speed up theirs? Oh, well; at least we can look forward to this: in another 160 years or so, both versions should catch up to the actual year, and they can finally drop all this silliness. The irony of all this is, it won't even work for its stated purpose; at least not for long. The spammers will quickly update their bots with the latest Chrome JS engines, and be able to pass the challenge. Surely Cloudflare and Gitlab know this; Chromium is open source, after all. News flash: humans (even this one) are not good at "mathematical challenges!" The only way to truly block bots is with an interactive captcha, which users understandably despise. So the only net effect will be to block folks from signing in unless they use Google's latest spyware er, "browser." (BTW, I wouldn't be surprised if common privacy protections, like canvas fingerprinting blockers, also stop you from getting past the Cloudflare "challenge." And don't even think about NoScript....) A better solution would be to just offer a captcha if the browser fails the "challenge;" that way you could still sign in with a non-evil browser, albeit with more annoyance. At least it still works (for now) in 360EE v12. I suppose there's a nonzero chance that UXP will get up to that level (and can then pass with a UA spoof) before Cloudflare updates their challenge to only work in Chrome 98+.

Hmm... so apparently this is why I can't access any sites on medium.com For about a year now, I get their "1020 Access Restricted" - owner may have blocked you blah blah Spoof user agent from Iron 70 to Chrome 98 and boom, now it works. The people who run medium.com are total freaking retards, there is no other logical or plausible explanation.

Hi my beta testers, @Dave-H, @NotHereToPlayGames and @mina7601, Dave found problems with my configuration program Configure PopMenu.exe and the starter program ProxyPopMenu.exe. They can't process paths with with spaces in them. All my tested paths didn't have any blanks. Therefore I had to fix both programs. Furthermore the documentation in my package still had to be completed. I did that now. Therefore I'll send you a PM with a link of new update package. This archive contains only those files which have to be exchanged. Cheers, AstroSkipper

Nothing new, the place I work at changed system requirements of the software produced there from specific versions of the browsers to "latest version of Chrome or Firefox" months ago. The era of explicitly supporting older platforms is long gone, no value is seen in supporting the old platform if the application in question can be run on the newest. Perhaps development was also slower in the past so supporting older platforms due to less differences from newer ones was easier. You'll be dead by then and WWW in its current form might as well not exist, if it even still exists by then, so hardly a reason to worry about!

Well, things look gloomy, indeed... I've read the following CF support article: https://support.cloudflare.com/hc/en-us/articles/200170136#browser-support and they plainly state: The "non-interactive JS challenge" GitLab are sending, as part of their CloudFlare protection, is meant to work on only the major villains, i.e. Chrome and "buddies" ... That article was last modified a month ago, possibly the same time GL log-in became broken... And it would seem that User-Agent-Sniffin' does play a role, in the initial detection at least, according to: https://support.cloudflare.com/hc/en-us/articles/204191238-What-are-the-types-of-Threats-#bad-browser https://support.cloudflare.com/hc/en-us/articles/200170086-What-does-the-Browser-Integrity-Check-do- https://support.cloudflare.com/hc/en-us/articles/204191238-What-are-the-types-of-Threats-#browser-challenge Indeed, when I spoofed Serpent 52 (via an extension) in my copy of 360EEv12, it too became unable to display the GL sign-in page ; back to its default UA and the GL sign-in page becomes accessible again (as told already in my previous post) ! Conversely, when I spoof "Firefox 100.0" in Serpent 52, I'm probably being served a JS challenge that can only be solved/passed by Fx 100.0 (or whereabouts), poor old St52 simply goes belly up...