A forum for discussing and organizing recreational softball and baseball games and leagues in the greater Halifax area.
Gamers Lose It After 007 First Light Demands Hardware That Doesn’t Exist in System Requirements: 'Remember When Games Were Optimized?'
-
Or just ignore AAA and play indie. Which reminds me, I should see hoe Agent 64 is coming along.
-
Note that many game studios prioritize consoles first and whatever room there is to turn up or down the settings is what makes it to the pc version. When benchmarking level performance targets they're going to use console hardware. They're selling it for the Xbox series S, so that's probably going to be what the devs are considering as the lower end of a decent experience. So that means that an a580, rx 6600, or 2060 super will be more than good enough. The series S only has 10 gb of shared cpu-gpu ram, so it will have to run on fairly limited ram as well.
-
 Link complains about adblock.This is a new kind of Adblock detection that is being deployed on many blogs, some forums, and other websites and it’s the next generation. AdGuard or uBlock won’t save you because the way it works is outside the scope of those plugins. There’s essentially JS that happens before the page render that checks for resolution with fingerprinting servers. If this does not occur you get the error message about html-load.com or content-loader.com or whatever that looks like malware intercepting the page. If the page implements the JS poorly (eg the page renders _before_ the checks come back) it’s easily defeated with ublock by just blocking element and selecting the overlay. Though the page usually isn’t fully rendered it’s enough to read the content. Reader mode can often work in this scenario too. But on more competent blogs with actual tech support (like seriouseats.com, fuck you kenji, like you don’t have enough money), it’s implemented more competently and the page won’t render at all prior to the checks coming back. As a result a solution is to lie. It’s cumbersome but if you run adguard dns (or maybe pihole, if that can also do dns rewrites, not sure), you can rewrite the offending servers checked for fingerprinting you like: api64.ipify.org cdn.cookielaw.org id5-sync.com cdn.id5-sync.com dotdash-meredith.solutions.cdn.optable.co static.cloudflareinsights.com html-load.com content-loader.com To a null route on your network for all subdomains. Somewhere run a docker and rewrite them to resolve to that docker, run nginx on that docker and basically just have it return 204 to all requests you funnel to it. Now those sites run the JS, there is dns resolution, tls handshake, fetch and response, but no fingerprint or analytics. It’s not perfect, the error still occurs 1:5 tries, but closing tab and retrying almost always has the page render fine without issue. Just keep in mind that some of these will break other sites (specifically cookielaw.org and lots of shitty shopping sites) especially if you do this lazily and just route to nothing instead of something that can return 204. Fuck all advertisers, never turn Adblock off, steal all content, defeat any antiadblock measure, destroy the ad industry because they ruined the world
-
This is a new kind of Adblock detection that is being deployed on many blogs, some forums, and other websites and it’s the next generation. AdGuard or uBlock won’t save you because the way it works is outside the scope of those plugins. There’s essentially JS that happens before the page render that checks for resolution with fingerprinting servers. If this does not occur you get the error message about html-load.com or content-loader.com or whatever that looks like malware intercepting the page. If the page implements the JS poorly (eg the page renders _before_ the checks come back) it’s easily defeated with ublock by just blocking element and selecting the overlay. Though the page usually isn’t fully rendered it’s enough to read the content. Reader mode can often work in this scenario too. But on more competent blogs with actual tech support (like seriouseats.com, fuck you kenji, like you don’t have enough money), it’s implemented more competently and the page won’t render at all prior to the checks coming back. As a result a solution is to lie. It’s cumbersome but if you run adguard dns (or maybe pihole, if that can also do dns rewrites, not sure), you can rewrite the offending servers checked for fingerprinting you like: api64.ipify.org cdn.cookielaw.org id5-sync.com cdn.id5-sync.com dotdash-meredith.solutions.cdn.optable.co static.cloudflareinsights.com html-load.com content-loader.com To a null route on your network for all subdomains. Somewhere run a docker and rewrite them to resolve to that docker, run nginx on that docker and basically just have it return 204 to all requests you funnel to it. Now those sites run the JS, there is dns resolution, tls handshake, fetch and response, but no fingerprint or analytics. It’s not perfect, the error still occurs 1:5 tries, but closing tab and retrying almost always has the page render fine without issue. Just keep in mind that some of these will break other sites (specifically cookielaw.org and lots of shitty shopping sites) especially if you do this lazily and just route to nothing instead of something that can return 204. Fuck all advertisers, never turn Adblock off, steal all content, defeat any antiadblock measure, destroy the ad industry because they ruined the world
-
This works on some sites but not all in my experience. Nothing works on all 100% of the time. My method generally works on all sites I’ve found that use this script (which is an increasing number and definitely on all dotdash Meredith sites like this/seriouseats/thespruce/etc) but it doesn’t work 100% of the time. I don’t know why. But anything that can defeat it should be promoted and that’s definitely much easier, should be tried first
-
This is a new kind of Adblock detection that is being deployed on many blogs, some forums, and other websites and it’s the next generation. AdGuard or uBlock won’t save you because the way it works is outside the scope of those plugins. There’s essentially JS that happens before the page render that checks for resolution with fingerprinting servers. If this does not occur you get the error message about html-load.com or content-loader.com or whatever that looks like malware intercepting the page. If the page implements the JS poorly (eg the page renders _before_ the checks come back) it’s easily defeated with ublock by just blocking element and selecting the overlay. Though the page usually isn’t fully rendered it’s enough to read the content. Reader mode can often work in this scenario too. But on more competent blogs with actual tech support (like seriouseats.com, fuck you kenji, like you don’t have enough money), it’s implemented more competently and the page won’t render at all prior to the checks coming back. As a result a solution is to lie. It’s cumbersome but if you run adguard dns (or maybe pihole, if that can also do dns rewrites, not sure), you can rewrite the offending servers checked for fingerprinting you like: api64.ipify.org cdn.cookielaw.org id5-sync.com cdn.id5-sync.com dotdash-meredith.solutions.cdn.optable.co static.cloudflareinsights.com html-load.com content-loader.com To a null route on your network for all subdomains. Somewhere run a docker and rewrite them to resolve to that docker, run nginx on that docker and basically just have it return 204 to all requests you funnel to it. Now those sites run the JS, there is dns resolution, tls handshake, fetch and response, but no fingerprint or analytics. It’s not perfect, the error still occurs 1:5 tries, but closing tab and retrying almost always has the page render fine without issue. Just keep in mind that some of these will break other sites (specifically cookielaw.org and lots of shitty shopping sites) especially if you do this lazily and just route to nothing instead of something that can return 204. Fuck all advertisers, never turn Adblock off, steal all content, defeat any antiadblock measure, destroy the ad industry because they ruined the world
-
 Link complains about adblock.
-
I realised that this is what i hate the most about A.I. I keep thinking: wait, this was written by A.I?! I have a friend, and we don't talk too much anymore, but i keep thinking that he kinda changed. Sometimes in a good way, sometimes not so much. He showed me something he wrote to proof read and look if it's correct. Just looking at it, i knew that he didn't write that. It was weird, over the top and it was a "professional" letter, but it used weird emojis to get the point across. Then i suddenly realised, that he told me that chatgpt helped him with something, and i thought it was a joke. And that made me realise that people casually just use A.I for all kinds of shit, and it's not just something people on the internet do.
-
This is a new kind of Adblock detection that is being deployed on many blogs, some forums, and other websites and it’s the next generation. AdGuard or uBlock won’t save you because the way it works is outside the scope of those plugins. There’s essentially JS that happens before the page render that checks for resolution with fingerprinting servers. If this does not occur you get the error message about html-load.com or content-loader.com or whatever that looks like malware intercepting the page. If the page implements the JS poorly (eg the page renders _before_ the checks come back) it’s easily defeated with ublock by just blocking element and selecting the overlay. Though the page usually isn’t fully rendered it’s enough to read the content. Reader mode can often work in this scenario too. But on more competent blogs with actual tech support (like seriouseats.com, fuck you kenji, like you don’t have enough money), it’s implemented more competently and the page won’t render at all prior to the checks coming back. As a result a solution is to lie. It’s cumbersome but if you run adguard dns (or maybe pihole, if that can also do dns rewrites, not sure), you can rewrite the offending servers checked for fingerprinting you like: api64.ipify.org cdn.cookielaw.org id5-sync.com cdn.id5-sync.com dotdash-meredith.solutions.cdn.optable.co static.cloudflareinsights.com html-load.com content-loader.com To a null route on your network for all subdomains. Somewhere run a docker and rewrite them to resolve to that docker, run nginx on that docker and basically just have it return 204 to all requests you funnel to it. Now those sites run the JS, there is dns resolution, tls handshake, fetch and response, but no fingerprint or analytics. It’s not perfect, the error still occurs 1:5 tries, but closing tab and retrying almost always has the page render fine without issue. Just keep in mind that some of these will break other sites (specifically cookielaw.org and lots of shitty shopping sites) especially if you do this lazily and just route to nothing instead of something that can return 204. Fuck all advertisers, never turn Adblock off, steal all content, defeat any antiadblock measure, destroy the ad industry because they ruined the world
-
> AdGuard or uBlock won’t save you I'll just do what I always did on websites that think they have a say in the matter: leave and never come back.
-
That seems the most likely.
-
