Expansion of "Personalized Results" to 5000 entries, perhaps as a 'pro' feature?

MYZuo

Currently the limit is 1000 entries, as this is the max that can be put loaded into the regular server cache at a time (from what I understand with my conversations with Vlad).

There's demand for more room, though I'm unsure of the amount in percentage terms. I personally would be interested in this feature.

The cost of using servers with larger cache sizes, to store the expanded list in-cache, might be more costly, though how much so I'm unsure of.

So I'm proposing to add this feature, possibly as part of a higher priced 'pro' offering if the economics don't work for offering it at the current pricing. This could be implemented by itself or with other neat 'pro' features.

Vlad

MYZuo Filtering based on this list is a costly operation. If everyone had 5000 items in the list we would need massively more infrastructure.

Perhaps it can be a feature of the Ultimate plan but it sounds weak on the pricing page. more thoughts welcome

MYZuo

Vlad There could be additional power-user features included to make it more appealing, such as being able to filter entire TLDs.

For example there are a lot of spammy results on newer 'themed' TLDs such as .space, .cfd, and so on.

Giving the ability to filter every result on a certain TLD would be a really unique feature no other search engine offers.

Another possible feature could be contextual filtering, where the for example the filter only applies if # of tracker is > X or if # of trackers is < X.

m789

I really wish I can do more than 1000, I'm already at the limit and consider this feature vital to my experience - there's so much junk sites out there!

frin

Personally what I do is, I only block it if I see a site coming up repeatedly that is useless to me, or if it is one of those copying sites where for example they take answers from StackOverflow and just duplicate it on their site. In a few months I am still at 42/1000.

I can understand why you would just want to get rid of entire TLD, but I hope they don't do that for the sake of people who set up legitimate sites with those unfortunate TLDs (with a few exceptions, like .xxx).

Regex could be useful, but it might be computationally expensive.

I have propsed a detection feature that might be of use when dealing with massive block filters, helping to clean them up and get back some of the filter space: Display when a particular personalized block last showed up in results that required filtering

zora

I really hope that you can find a way to optimise your filtering code in order to allow for >1000 entries. For me, it is not just a productivity, but a safety feature. I’m a trans woman and heavily rely on domain blocking so I don’t have to see headlines that deny my humanity whenever I’m researching self-ID laws or whatever.

By the way, I’m so thankful that you expanded the filtering to videos! This will be a blessing for my mental health.