@katie Hey Katie, very sorry to hear that; we've been combatting some bots recently so we might have made a mistake there. Would you be okay sending your IP over a more secure channel so we can investigate? If so, which would suit you best? Thanks
@katie Response from devs is: this is most likely due to "search terms sent by searx users" rather than because of searx
@Mojeek This made me curious, what are the search terms that would get you banned from Mojeek?
Are there search terms one aren't allowed to search for using Mojeek? What are these search terms? And are banned search terms due to legal issues, controversies or moral viewpoints?
@katie the only two things we focus on is suspected bot traffic/automated search stuff and terms which relate to child abuse - this process when it comes to action is not foolproof.
We're checking the IP stuff now!
@katie Apologies, it looked like I was avoiding the end part of the question there. The automated searches are for business interest, because these searches do not provide us with any value. The child abuse stuff is a combination of the "legal issues, controversies and moral viewpoints."
From the amount of automated requests I've seen, which were forwarded to Mojeek since it used to be enabled by default - it's not anymore, I'm not entirely sure that banning my IP was a "mistake". It could simply have been something that made perfect sense.
Either Firefox/56.0, yes that specific version, is the worlds most popular browser, or something else is going on. I get why you wouldn't want that flood.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!