Sorry, I erroneously sent a private reply, since I don't reply often enough to mailing lists to remember that "list reply" in mutt is different than "reply", and I thought others might be interested in my reply, so I'm reposting it here.
On Fri, Jul 05, 2024 at 01:11:36PM -0400, Jude DaShiell wrote: > they're also blocking elinks and w3m. Thanks for the heads up on links > though. It depends on the useragent. I, too, see it hang if I don't change the useragent string, but I have a number of aliases for lynx that present different useragent strings. A Firefox useragent also hangs, an Internet Explorer useragent gets a page that says my browser isn't supported, but here are a few that get the page with lynx: Firefox on Android: lynx -useragent="Mozilla/5.0 (Android 7.0; Mobile; rv:54.0) Gecko/54.0 Firefox/54.0" The long ago discontinued Sidekick, from T-Mobile: lynx -useragent="Mozilla/5.0 (Danger hiptop 5.0; U; rv:1.7.12) Gecko/20050920" Blackberry: lynx -useragent="Mozilla/5.0 (BB10; Kbd) AppleWebKit/537.35+ (KHTML, like Gecko) Version/10.3.3.2205 Mobile Safari/537.35+" I also got it to load using useragents for Chrome on Android, Firefox on IOS, and Safari on IOS, but those useragent strings are much longer, and I didn't feel like posting them here, either broken into multiple lines, or joined into one really long line, but they work. Interestingly, I have three different Googlebot useragents I found somewhere, which all hung, but I was successful with a useragent that was nothing but a nasty message about what kind of despicable people block browsers based on useragent, but I won't post that one here. Chuck
