Most promoted and blocked domains among Kagi Search users
71–80 of 502 posts
Re: Most promoted and blocked domains among Kagi Search users
#72Earlier quoted context omitted.
It often outranks MDN official docs which these days are very readable, in-depth, with examples, and a simple UI and the only time I click to inappropriately named W3Schools is by accident because it's the top result and I'm expecting MDN and then I click back and that's why I don't like it.
I have similar feelings about baeldung.com. It isn't that the content is inherently bad, but it is super annoying that when I search for a java class the first few results are from baeldung instead of the official javadocs.
Re: Most promoted and blocked domains among Kagi Search users
#73Re: Most promoted and blocked domains among Kagi Search users
#74Re: Most promoted and blocked domains among Kagi Search users
#75Same comment for CNN and wapo that I see are also there. Maybe I'd dont search current events enough, they all seem like odd things to block to me.
Re: Most promoted and blocked domains among Kagi Search users
#76This feature is Kagi's single best innovation in search. It's what makes their results so much better than Google's: where Google's results are usually drowning in garbage websites, Kagi comes built-in with a great set of spam filters, and on top of that you can adapt your own personal list of good and bad domains as you go!
Didn't Google have this feature like two decades ago (blocks, at least)? It's not quite a search innovation, more like a "caring about your users as a business strategy" innovation.
Re: Most promoted and blocked domains among Kagi Search users
#77 const boringDomains = [
"newyorker.com",
"nytimes.com",
"economist.com",
"wired.co.uk",
"bbc.com",
"aella.substack.com",
"hecolumn.substack.com",
"wsj.com",
"kqed",
"voanews.com",
"wusa9.com",
"noemamag.com",
"arstechnica.com",
"independent.co.uk",
"axios.com"
]
Array.from(document.querySelectorAll(".titleline > a"))
.filter(elem => boringDomains.some(domain => elem.href.includes(domain)))
.map(elem => elem.parentElement.parentElement.parentElement)
.flatMap(elem => [elem, elem.nextElementSibling, elem.nextElementSibling.nextElementSibling])
.forEach(elem => elem.remove())Re: Most promoted and blocked domains among Kagi Search users
#78I've never quite understood the w3schools hate. It can be quite useful. My most used page is this one when I need to jog my memory: https://www.w3schools.com/cssref/css_selectors.php It's much better than this one: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_selecto... Or any of the other results on the first page
Re: Most promoted and blocked domains among Kagi Search users
#79Earlier quoted context omitted.
Umm, according to the latest data, user choice is far less competitive than algorithms at stabilizing engagement metrics. Users' behavior speaks louder than what they believe in their little heads.
Can't tell if sarcasm or not.
Re: Most promoted and blocked domains among Kagi Search users
#80I actually did a smaller thing for HN. I have client side JS that blocks results from a few domains that seemed to promote low quality discussions and/or irrelevant submissions. const boringDomains = [ "newyorker.com", "nytimes.com", "economist.com", "wired.co.uk", "bbc.com", "aella.substack.com", "hecolumn.substack.com", "wsj.com", "kqed", "voanews.com", "wusa9.com", "noemamag.com", "arstechnica.com", "independent.c…