Earlier quoted context omitted.
Likewise, I co-maintain the only "fan" site on one of my all-time favourite composers/performers, and gave the engine a shot with a unique string query. While my text-heavy WP-driven site didn't seem to make the cut, the results were highly relevant in that they were links to former band members and collaborators - a couple of which I didn't realize existed. That being said, there were a few sites (including my own)…
The search engine doesn't actually do full text search, so maybe your query was too... unique. But do first of all verify that you haven't been hacked. There's about quarter of a million domains I've flagged that, besides their wordpress content, also host a ton of link spam crap off in some hidden folder. This reflects on the quality rating extremely negatively to the point where you may have not been indexed at all…
A search engine that favors text-heavy sites and punishes modern web design
421–430 of 735 posts
Re: A search engine that favors text-heavy sites and punishes modern web design
#422Re: A search engine that favors text-heavy sites and punishes modern web design
#423Earlier quoted context omitted.
Again it's a one man hobby project, I don't have a team of people to go through every formulation and every error message to ensure nobody can read them in a way that offends them. It's just me, writing code on an unfinished project that HN discovered. In this case, the code doesn't match the word regexp, like it may be a @TwitterHandle or a "comp.lang.c" with periods in it, or an unsupported Unicode range. It doesn'…
I must congratulate you on this achievement. That's certainly a useful take on search. Nonetheless, even when coding, one should also consider thoroughly the UX and how it would be addressing the others. Saying "unsupported word" is much more sympathetic than "needs to be a word" (where you define what a "word" is, and the general user is unaware of such definition).
> The term "𓀀" contains characters that are not currently supported
Re: A search engine that favors text-heavy sites and punishes modern web design
#424Re: A search engine that favors text-heavy sites and punishes modern web design
#425Wow, that's awesome. Great work! For a simple test, I searched "fall of the roman empire". In your search engine, I got wikipedia, followed by academic talks, chapters of books, and long-form blogs. All extremely useful resources. When I search on google, I get wikipedia, followed by a listicle "8 Reasons Why Rome Fell", then the imdb page for a movie by the same name, and then two Amazon book links, which are totall…
Imagine if you were looking for the movie.
Re: A search engine that favors text-heavy sites and punishes modern web design
#426Earlier quoted context omitted.
This got me thinking that maybe one of the other big reasons for this is that the algorithms prioritize newer pages over older pages. This produces the problem where instead of covering a topic and refining it over time, the incentive is to repackage it over and over again. It reminds me of an annoyance I have with the Kindle store. If I wanted to find a book on, let's say, Psychology, there is no option to find all-…
> is that the algorithms prioritize newer pages over older pages. They do? That would explain a lot - but ironically, I can't find a good source on this. Do you have one at hand?
The only definitive source on this would be the gatekeeper itself. But Google never says anything explicitly, because they don't want people gaming search rankings. Even though it happens anyway.
Re: A search engine that favors text-heavy sites and punishes modern web design
#427Such a relief to not wade through oceans of worthless crap any more.
Re: A search engine that favors text-heavy sites and punishes modern web design
#428Search for playwright waitForSelector and you land in pretty useless page. I'm all in for text websites, but something like playwright.dev documentation is top notch - fuzzy search being key thing.
Re: A search engine that favors text-heavy sites and punishes modern web design
#429Yeah so this is my project. It's very much a work in progress, but occasionally I think it works remarkably well for something I cobbled together alone out of consumer hardware and home-made code :-)
Re: A search engine that favors text-heavy sites and punishes modern web design
#430Earlier quoted context omitted.
Part of what I wanted to show with this project is that there is no such thing as an objective search engine. Even seemingly irrelevant technological decisions drastically impact the narrative.
Well the focus on text content isn't the only technical difference here. Google is obviously weighing hundreds of signals in its search results that your engine is not accounting for. These omitted signals are also relevant.
Certainly. And sometimes they're relevant in a good way, sometimes in a bad user-hostile way. Every search engine rquires discrimination and intelligent usage by the person doing the search, just in different areas.