I am no longer able to use Google with Lynx
1–10 of 333 posts
Re: I am no longer able to use Google with Lynx
#2With with lynx not.
Re: I am no longer able to use Google with Lynx
#3Re: I am no longer able to use Google with Lynx
#4Re: I am no longer able to use Google with Lynx
#5Any reason people prefer lynx over w3m or eww?
Re: I am no longer able to use Google with Lynx
#6Serious question, why search Google in your terminal with Lynx as opposed to `googler`? The actual result pages can still open in Lynx but the experience of navigating the results is very nice.
Re: I am no longer able to use Google with Lynx
#7https://www.brow.sh/ is a console-based browser that claims to support modern standards. Perhaps that is what we should be using.
(I am now prepared for 6 comments replying to me saying that anything that can be implemented with HTML from 1999 should be, and a list of search results can be. I guess. If all that stuff works for everyone, why did we invent new stuff? Just because? Or perhaps it wasn't really as amazing as well all remember.)
Re: I am no longer able to use Google with Lynx
#8Another person notes that ddg is inferior. Maybe people get used to a certain way of searching with Google that doesn't translate to ddg. Haven't noticed a drop in quality myself and I think I might have been retrained to use different patterns and techniques in structuring my queries.
Re: I am no longer able to use Google with Lynx
#9I find that I physically cannot navigate to the links in the page except the first few at the top.
But.
On the pages I get, the ... structure is still 100% intact. It's buried in a table and div soup, but it's there.
So, I argue Lynx parsing bug!
The author of this article would have done well to save and diff the working/not-working HTML they received. :(
Re: I am no longer able to use Google with Lynx
#10Curious, I installed lynx just to check this out. I find that I physically cannot navigate to the links in the page except the first few at the top. But. On the pages I get, the ... structure is still 100% intact. It's buried in a table and div soup, but it's there. So, I argue Lynx parsing bug! The author of this article would have done well to save and diff the working/not-working HTML they received. :(
Should they be expected to make their own ‘re-Googler’ to fix the page so they can use it again?