Comment 42 for bug 1054282

Since all traffic is routed through Canonical servers (or should be if I understand how things are supposed to work in the end) it becomes Canonical's problem, not Amazon.

Blaming the lack of options on the api is just an excuse to postpone something that must be done in the future, even more if other sources are supposed to become available over time.

My thought is that blacklisting is the only way to go. Google got this same problem on its instant search feature, since then, results never autorefresh if dubious words are detected on the query.

Stepping back, all this was not a public concern when shopping results shown only inside specific lens and not in the home dash. This shows how a small change in scope is going to impacting users deeply. I expect Canonical to be alert, communicative and gather feedback to start fixing things that were problematic or not good enough from the beginning.