When you type something without many results, the DDG proxy will ask if you want to search for the specific term that you looked up. If you click on this button, instead of putting quotation marks around the text, it puts " which doesn't do anything but jumble up your search.
When you type something without many results, the DDG proxy will ask if you want to search for the specific term that you looked up. If you click on this button, instead of putting quotation marks around the text, it puts `"` which doesn't do anything but jumble up your search.
A solution that can be done in development is to remove the word inside the "" from the href on the server side. I expect lolcat will likely address this in the frontend rewrite they have been mentioning for sometime now.
A solution that can be done in development is to remove the word inside the `""` from the `href` on the server side. I expect lolcat will likely address this in the frontend rewrite they have been mentioning for sometime now.
Yeah I fucked up, the duckduckgo scraper wasn't decoding the html entities and the frontend wasn't escaping the string. woops
It's fixed now, thanks for the report
Yeah I fucked up, the duckduckgo scraper wasn't decoding the html entities and the frontend wasn't escaping the string. woops
It's fixed now, thanks for the report
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When you type something without many results, the DDG proxy will ask if you want to search for the specific term that you looked up. If you click on this button, instead of putting quotation marks around the text, it puts
"which doesn't do anything but jumble up your search.A solution that can be done in development is to remove the word inside the
""from thehrefon the server side. I expect lolcat will likely address this in the frontend rewrite they have been mentioning for sometime now.Yeah I fucked up, the duckduckgo scraper wasn't decoding the html entities and the frontend wasn't escaping the string. woops
It's fixed now, thanks for the report