Live data from Hacker News

Shirt Without Stripes

github.com

171–180 of 639 posts

Re: Shirt Without Stripes

#171
post #162

Earlier quoted context omitted.

Because you want to sell shirts without stripes to customers who want them.

I expect most users genuinely looking for such a product would just search "plain shirt"

That is an inclusive search though. What if the user actually wanted to simply exclude stripes but wanted to see polka dots and paisley?

Re: Shirt Without Stripes

#172
post #21

Earlier quoted context omitted.

It would be really nice if the search engines would automatically apply the "-" when it sees the work "without".

I’m not so sure. What about a search query for “Doctors without Borders“ or “Men Without Hats“? Surely interpreting “without“ as the negative operator would ruin those searches.

IIRC if you use quotation marks in your search query, it would search for the exact match of that phrase without any search operators processed inside of it. So those scenarios you listed would still work fine.

Though I somewhat agree, I don't think that an average user even knows about existence of search operators in the first place, let alone being aware of this specific one and when to use it.

Re: Shirt Without Stripes

#173

https://www.google.com/search?q=plain+shirt https://www.amazon.com/s?k=plain+shirt on edit: https://www.google.com/search?q=shirt+-stripes

Yeah... As expected, negating the stripes on that last google search makes no apparent difference for me, and "plain shirt" has an entirely different meaning from "shirt without stripes".

Re: Shirt Without Stripes

#174

Probably not surprising that most people don’t know, but negative keyword search works on all these platforms: shirt -stripes

it actually does work though. keywords will need to be generated whether manually, from the manufacturer, or from image analysis.

Search engines are indexing content based on [edit]STATIC [/edit] keywords, though.

The author's intent exceeds both the capabilities and intended use case of search engines.

The query "shirts without stripes" if interpreted by human would require any search system to not only analyse the keywords and tags (of the products/images), but also the content, which is an infeasible task given its dynamic nature.

So the author wants: select all shirts where content analysis of returned images yields no stripes.

This is a context-sensitive image/product search based on arbitrary, dynamically created criteria and shows that user isn't aware of what the search functionality does as opposed to exposing weak "AI". [edit]To clarify: you cannot add all possible keywords/criteria in advance[/edit]

Re: Shirt Without Stripes

#176
post #162

Earlier quoted context omitted.

Because you want to sell shirts without stripes to customers who want them.

I expect most users genuinely looking for such a product would just search "plain shirt"

Assumptions like this is what makes search so terrible for many many companies.

You can't assume that customers would type one thing or another - you need to gather lots of query log data and see what you find. You'd be surprised how much variation there is, but once you do have this data you can then find patterns to cover lots of (but not all) cases.

Re: Shirt Without Stripes

#177

Earlier quoted context omitted.

Every systems sucks at NLP. It is an extremely hard problem and we are nowhere near matching the human cerebral cortex.

Generally, yes. But you can go very far and cover a lot of cases when you stick to a narrow domain and common patterns that customers of your product will typically use.

My reaction to Siri is either amazement at how well it worked or disgust in its failure on seemingly simple queries.

Re: Shirt Without Stripes

#178
post #13

The point of this isn't asking how to apply boolean search operators, it's showing that the largest AI-focused companies in the world absolutely suck at NLP.

Why would you really apply NLP to a search engine though? Generally speaking a weighted keyword search is good enough 95% of the time and requires significantly less resources to perform.

Perhaps it's considered "good enough" because users balk at performing NLP-style queries when they find they almost never work properly.

Re: Shirt Without Stripes

#179
Google Photo's search is a similar source of amusement for me. While it's quite good, it also fails fairly regularly and sometimes amusingly. For me "turtle" includes understandable mistakes like fish, a snail, and a rock that does look a bit like a turtle. However "turtle" also includes this, a picture of sequined slippers reflecting light?! https://i.imgur.com/4aSlA4B.jpg

I'm guessing one of those reflections looks like a turtle? Or maybe a pattern on the floor, wall, or rug?

Although there are examples where I'm unsure if the AI is dumber than my 4yo or smarter than me. This is a result for "truck": https://i.imgur.com/JcgXZAG.jpg

Even (especially?) my 4yo knows those are Brio trains, not trucks. However, trains have components called trucks! https://en.wikipedia.org/wiki/Steam_locomotive_components I'm unsure whether or not any of the wheel assemblies on these toy trains are considered trucks, so either the AI is extremely smart or slightly dumber than a 4yo.

Re: Shirt Without Stripes

#180
I get the author's point, but if you think about it, a search engine is a database that serves you results you want to see. Why should a search engine be fine tuned towards things you don't want see?

If it's meaningful for some reason, then it works:

https://www.google.com/search?q=woman+without+makeup&tbm=isc...

If it's an user error (like a dumb query) it fails and it shouldn't be a surprise:

https://www.google.com/search?q=sea+without+ships&tbm=isch

Post reply on HN