search

Wetbikeboy2500 / Resurgence

This aims to fix and enhance the Scratch website
MIT License
6 stars 1 forks source link

Consider using DuckDuckGo instead of Google Search #33

Open infinitytec opened 6 years ago

infinitytec commented 6 years ago

Why?

  1. Easier to theme
  2. No ads required
  3. Privacy
Wetbikeboy2500 commented 6 years ago

Sounds good but I won't be able to work on it till next week. You would also have to figure out the duckduckgo api.

infinitytec commented 6 years ago

The basics to setting up a search box are here: https://duckduckgo.com/search_box

ZenithRogue commented 6 years ago

Unfortunately, with the thing that @infinitytec suggested you cannot use it as an iframe.

Because of the way we generate our search results, we do not have the syndication rights to allow you to host our results on your site (e.g. in a frame). When your users click on the results they will be instead taken to our site. Please see our partnerships page for more info on guidelines and getting in touch with us.

infinitytec commented 6 years ago

Perhaps replace the search page entirely. The search bar can be replaced with a DDG one.

Wetbikeboy2500 commented 6 years ago

I am back at a computer and have taken some time to think and investigate the use of DuckDuckGo. Firstly, the current Google search is pretty easy to use and robust, and It also has tabs that can search specific parts of the site with great speed. I also have a little bit of control of the theme of the search results, but I currently don't find an issue with its aesthetics. I also haven't seen any adds yet but I may be wrong on this one. If we were to switch to DuckDuckGo it is going to be a fair amount of work with it only producing a slow result. We can't use the api to they have since the search results are restricted. I have also tried using their api to search just the scratch site, but I had no luck in it returning a positive result. There was a good post on Stack Overflow that ended up saying that you are going to have to parse the html version of DuckDuckGo to get the search results. If we have to parse all the html for the DuckDuckGo searches it is going to take some time and we may also run into issues of it being to slow. Even if it can produce the results fast enough, we would still have to design our own framework for the results to go in that can work and function properly for multiple search pages and different categories. That is why I am going to try and stick with Google for now since the overhead is minimal and it can give a fair amount of features for a search engine.