RIPE NCC, thanks for evolving the site! When it comes to searching, I agree with Andy that a search field on a web site leads me to believe that it searches that website*, and not some "external" databse – and I like to have it that way. To access the RIPE DB over HTTPS, I would like so see that as a second, and separate, search field, so that I can "tell the system" where I want it to search, e.g.: Search website: ...... Search RIPE DB: ...... Myself, I'm old enough to prefer the whois CLI tool to lookup stuff in the DB, but I know that I'm old-fashioned, and I do respect that HTTPS is easier for most people. Cheers, /Liman * With the obvious exception of search engines like Google. andy@nosignal.org 2024-01-21 10:16 [+0000]:
On 20 Jan 2024, at 21:06, Leo Vegoda <leo@vegoda.org> wrote:
I disagree. They are equally important. RIPE Database searches obviously need to be highly accessible but the site search is vital as the site is so big and old stuff is never removed. I look forward to a really good website search feature coming soon.
Thanks for making this point so eloquently. It’s what I thought too: I do expect the ripe website search tool to first and foremost search the ripe website, notwithstanding the benefit provided by and need for a really good web interface to the ripe db. I assumed I’d missed something and stayed quiet. Thanks also for helping me realise that I had a valid thought all along, Leo. :)
Andy --