As often reminded, that's probably a zoning issue. Here on a different continent I live in an area BESIEGED by supermarkets, but I buy most of my groceries at the baker (breadmaker) and fruit-and-vegetables shop down the street. They're more expensive but more convenient and higher quality. With the advantage of there not being a butcher as close-by, meaning I've been eating way more veggies since moving (and eggs, given those are sold in both stores). Now the issue is they're opening a new pedestrian path that leads straight from my home to the pastry shop on the neighboring block!

Walk me thru how the tariffs will work on that, will ya taco boy?

I’m sure publishers are all ears /s

Yes. I can't use lynx for most of the sites I am used to go with it. They are all protecting themselves with captcha and other form of javascript computation. The net is dying. Fucking thank you AI-bullshitery...

In those situations I usually enable 1.5x.

It is a possibility. Thanks for the input!

AI isn't math formulas though. AI is a complex dynamic system reacting to external input. There is no fundamental difference here to a human brain in that regard imo. It's just that the processing isn't happening in biological tissue but in silicon. Is it way less complex than a human? Sure. Is there a fundamental qualitative difference? I don't think so. What's the qualitative difference in your opinion?

I think the principle could be applied to scan outside of the machine. It is making requests to 127.0.0.1:{port} - effectively using your computer as a "server" in a sort of reverse-SSRF attack. There's no reason it can't make requests to 10.10.10.1:{port} as well. Of course you'd need to guess the netmask of the network address range first, but this isn't that hard. In fact, if you consider that at least as far as the desktop site goes, most people will be browsing the web behind a standard consumer router left on defaults where it will be the first device in the DHCP range (e.g. 192.168.0.1 or 10.10.10.1), which tends to have a web UI on the LAN interface (port 8080, 80 or 443), then you'd only realistically need to scan a few addresses to determine the network address range. If you want to keep noise even lower, using just 192.168.0.1:80 and 192.168.1.1:80 I'd wager would cover 99% of consumer routers. From there you could assume that it's a /24 netmask and scan IPs to your heart's content. You could do top 10 most common ports type scans and go in-depth on anything you get a result on. I haven't tested this, but I don't see why it wouldn't work, when I was testing 13ft.io - a self-hosted 12ft.io paywall remover, an SSRF flaw like this absolutely let you perform any network request to any LAN address in range.