NotHereToPlayGames
MemberNotHereToPlayGames last won the day on February 3
NotHereToPlayGames had the most liked content!
About NotHereToPlayGames

Profile Information
-
OS
Windows 10 x64
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
NotHereToPlayGames's Achievements
3.5k
Reputation
-
-
Just for fun... I am not a gambler, just kinda finding the "hypothetical bet" a tad fun... I'll publicly post that yeah, Duke is going to win, but "if I were a gambling man", I would put $100 on Boston College (ie, that Duke will NOT win by 27 or more points).
-
You need to read the full post or not read it at all. So I'll repeat the part that you didn't take into account with your BIASED post above... Excluding VM browsers (primarily Roytam releases) which get hit with Cloudflare, clears itself in 24 hours, then gets hit again, but clears itself in 24 hours.
-
Interesting. The only Cloudflare captcha I'm ever hit with is my water sewage billpay web site. First encountered last November and the only fix was to upgrade Chrome from v136 to v138 (but laned on v140 due to other nuances). I was hit with it again just a couple of weeks ago and the only fix was to upgrade from Chrome v140 to v141 (but landed on v144 due to other nuances). I cannot list the URL because it reveals the city that I live in. That one web site is my only Cloudflare headache. Excluding VM browsers (primarily Roytam releases) which get hit with Cloudflare, clears itself in 24 hours, then gets hit again, but clears itself in 24 hours.
-
Of course it is! They are different sessions, different cookies. I'm failing to understand the obsession. I'm done here, I really do not need the obsession.
-
The tracker will be different with each browsing session. Google is tracking your searches, not your browser. I never said that the tracker will be "identical". It is generated BY GOOGLE each and every first visit per COOKIE. Delete the cookie and you get a new "tracker". First cookie: Delete first cookie, let Google set second cookie:
-
My Browser Builds (Part 5)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
I don't think that it is regional advertising causing that error. I get that error in most recent B/S 52, B/S 55, and PM/NM 28. Only one of the three (brand new profiles, first run on all three) gave a geolocation warning (which was denied), but I forget which one of the three. I have to assume that the other two simply allowed the location-reveal, but I did not verify. -
Found this - https://www.topendsports.com/sport/betting-tools/spread-calculator.htm This answers most of my curiousity. A local team has been VASTLY OVER-RATED and (admittedly) it has become FUN ENTERTAINMENT to watch them NOT live up to that over-rated hype! Sure, it's nice that they've been WINNING, but they have NOT been winning by the double-digit margins of the "betting lines". On a "standard VIG" [ie, -110] (no clue what that is, kind of doesn't matter for sake of example), we can "back-date" FIVE wins by this team but FOUR of those wins DID NOT BEAT THE SPREAD. Game 1 >>> spread of -18.5 (ie, if they don't win by 19 points or more, then they lose in terms of the bet) Game 2 >>> spread of -16.5 Game 3 >>> spread of -8.5 Game 4 >>> spread of -14.5 Game 5 >>> spread of -12.5 The team won all five of these games, but did NOT cover the spread of games 1, 2, 4, and 5. My FUN ENTERTAINMENT was "gentleman's bets" with a coworker. For "bragging rights". My "working theory" to my coworker was that our local team would NOT cover DOUBLE-DIGIT SPREADS. So we were technically "betting, but no money, just bragging rights", on only games 1, 2, 4, and 5. I *won* but she now mocks me for there being no "money" on the line. So if the VIG is always -110 "standard", the spread calculator link posted above would have paid out in this manner if $100 was bet on game 1, the winnings then bet on game 2, the winnings then bet on game 4, then the winnings bet on game 5. Game 1 >>> $100 bet, payout would have been $190.91 Game 2 >>> $190.91 bet, payout would have been $364.56 Game 4 >>> $364.56 bet, payout would have been $695.98 Game 5 >>> $695.98 bet, payout would have been $1,328.69
-
Yep! I remind my brother of that ALL THE TIME. He's big into lottery tickets, swears up and down he wins more than he loses but I can't get him to SPREADSHEET IT for PROOF. Because I keep telling him "that's how the game is played". Make you FEEL LIKE you are winning so that you keep buying.
-
Generally speaking, you should never get a Cloudflare captcha on any MODERN web browser that UPDATES ITSELF every few weeks. The problem is for those that prefer to NOT run these auto-updates. All it takes is a browser that is THREE OR FOUR versions "old" to TRIGGER the Cloudflare captchas. I've never witnessed anything but a checkbox that checks itself, zero user interaction, when at work (where the IT dept forces me to reboot my laptop 25 times in any given 30 day month all in the guise of "updates" for this or that).
-
Yeah, I actually have come to hate hate HATE sports! I *literally* NEVER watch anymore (but scroll scores via web browser instead). It was different when I was a kid, but nowadays, every commercial break is sponsored by a GAMBLING COMPANY with tiny fine print at the bottom for those with "gambling addictions". Then there are things like https://www.nbcnewyork.com/news/sports/list-players-coaches-sports-betting-gambling-allegations/6408736/ And this https://www.cnn.com/2024/06/15/sport/sports-betting-gambling-professional-athletes-dg You can't even watch "news" programs that are supposed to cover "sports" without them also covering GAMBLING and be SPONSORED by GAMBLING COMPANIES. I'm waiting for these to become ILLEGAL ADVERTISING (like cigarette commercials, not technically "illegal", but so HEAVILY regulated that no manufacturer bothers to "advertise").
-
But I feel like the TIME that was spent to demonstrate this PROOF is time WASTED. Because my name doesn't begin with a "D" so answers, despite 100% accurate and true, will never be "liked". Yeah, that was a rib-jab.