You should shoot a note to your old friend Devil's Advocate if you don't get this resolved here. That Harvard comp sci Ph D may come in handy.
You should shoot a note to your old friend Devil's Advocate if you don't get this resolved here. That Harvard comp sci Ph D may come in handy.
If you've made a change that you think should have stopped the issue, it's possible that the remaining redirect cases are the result of caching. Without knowing how ads & assets are served for letsrun it's hard to say exactly what is being cached where to cause this problem. In theory once that cache expires or is otherwise invalidated for all users, the issue should go away.
Tried to download uBlock Origin from the Play store, but it keeps popping up with another Ad blocker to install (Rocketshield). Doesn't seem to "let me" download it.
Never saw that before.
You don't have to get it from the app store (I don't.) Go to the actual browser app (so Chrome, Firefox, or whatever) and click on the menu. Addons should be in the menu by settings. Click on addons and then search for uBlock Origin from there. On Firefox I think it's one of the main ones already there. You can do this on mobile and desktop.
Stats.gangsta_the_real_1 wrote:
MeHereYouWhere?! wrote:
Did you try restarting the phone?! ;)
Also, did you try jiggling the handle?
THAT WAS FRICKIN' FUNNY DUDE, WELL PLAYED!!!!!!!!!!! LOL!!!!!!!!
Actual information from website, includes Chromium-based, Firefox, Edge, and Safari.
Chromium: from Chrome store, Opera store, or manual. If you manually download it, you will need to unzip the file, meaning you need a computer.
Firefox: Addons
Edge: Microsoft Store
Safari: Manual
Rupp thread. Android. Got the Walmart bit.
bikeforums.net is having a similar problem though not so bad as here. You might contact them and see if they have any insights on solving the problem.
shame on you! wrote:
this.
shame on the capitalist pigs, trying to exploit their customers.
Exploit their customers who pay nothing.
Imagine if you went into a restaurant and were served food for free and then complained when the restaurant asked if you could take a look in the kitchen to help them with a problem they were having.
rojo wrote:
Exploit their customers who pay nothing.
Imagine if you went into a restaurant and were served food for free and then complained when the restaurant asked if you could take a look in the kitchen to help them with a problem they were having.
These average joes have no idea what goes into the upkeep of a website that has beaten all odds and lasted about 20 years. These are the same cowards jumping for every witch hunt they can sink their fangs into and run away with their wild theories that populate search engine results. This is the platform that allows them to live out their toxicity using ad block and cheating the overall system.
I thank you for your years of service to the running community but for the very reason you vented frustration you should put the anonymous trolling aspect of this site to an end. If they dont come back that is for the better. Some of these people are 49-year old losers living at home and driving beat up red vans just waiting for the opportunity to bandwagon a new SFH or Mike Rossi story.
On a more relevant note, the redirects are probably killing search engine ratings as well. Web crawlers don't take kindly to being redirected to shady sites. Consider changing how you are presenting these ads.
On LetsRun, no one turns 50. Sure there are high school kids and such. But once you turn 49 you stay there quasi-indefinitely. I’ve been 49 for 3 years myself. I don’t have any kids and I only work and run. Some people call me a jerk. I call myself someone who buys into the process.
Just had a redirect.
4PM EST
HTC U11 (Android)
Kris Krinkle wrote:
If you've made a change that you think should have stopped the issue, it's possible that the remaining redirect cases are the result of caching. Without knowing how ads & assets are served for letsrun it's hard to say exactly what is being cached where to cause this problem. In theory once that cache expires or is otherwise invalidated for all users, the issue should go away.
+1
Either that, or you are being trolled.
Kris Krinkle wrote:
If you've made a change that you think should have stopped the issue, it's possible that the remaining redirect cases are the result of caching. Without knowing how ads & assets are served for letsrun it's hard to say exactly what is being cached where to cause this problem. In theory once that cache expires or is otherwise invalidated for all users, the issue should go away.
I said similar on the first page. Something they may want to do to expedite this process is to add filetimes to the referenced CSS and JS files. They use PHP here -- because it is easy -- so have a look at the following:
http://php.net/manual/en/function.filemtime.phpFor example, they have the following line (script tags witheld):
src="
http://www.letsrun.com/forum/responsive/js/notMobile.js?version=011017"
Instead they can use the echo filetime($file_location) at the end of the file and achieve the following:
src="
http://www.letsrun.com/forum/responsive/js/notMobile.js?1512253068"
Which fools the servers and devices to reload a "new" referenced file every time the file is saved.
Internal CSS files should be the same as well as any images that they intend to overwrite.
Embedly screwed up my post.
Old file name:
hxxp://
www.letsrun.com/forum/responsive/js/notMobile.js?version=011017
Desired file name:
hxxp://
www.letsrun.com/forum/responsive/js/notMobile.js?[echo
filemtime($file_location)]
which would be:
hxxp://
www.letsrun.com/forum/responsive/js/notMobile.js?1512253058
All internal CSS files and frequently overwritten images should do the same.
F--- embedly, cheap
Has anyone tried this? If so, were they successful in getting data? I’m pretty immobile due to compartment syndrome surgery so would give this a try but if it didn’t help before I don’t want to waste my time...