

I don’t think that it is the responsibility of KDE or Discover to perform blacklisting or cleanup here.
It is a upstream fuck Up by Canonical, again! The solution for this can’t be that developers of a frontend, like Discover, now reserve and use time and resources to add and maintain blocklists to clean up that mess that they didn’t created.
We should get our torches and pitchforks and put all the blame where it belongs, at Canonical!
No it would not, because as soon as they implement such a blocklists feature and provide official blocklists they take over responsibility (morally and in some countries even legally) to ensure that they provide updated filter lists in a timely manner.
Oh and then they have to implement something that vets and checks incoming scam alerts, to ensure that only valid claims are blocked. This will put unneeded strain on the personal and financial resources of KDE.