Pastelland Forum

Can confirm everything seems to be working fine, including search.

Thank you!!! ^^

I can confirm there's no 500 error anymore in search.

But...

Sometimes, something weird happens now, like this one, for example:

"The following words in your search query were ignored because they are too common words: submachine."

Too common??????????????????? So that's why you refuse to show search results??? *burns search for this blasphemy!!!!!!*

Is there a way to turn this weird "defense system" off? lol

I just checked, right now the threshold for common posts is at 15%, meaning that words appearing in more than 15% of posts are considered too common. We could try setting it to 20-40% (or deactivating it), but the search index would probably get considerably larger so I don't know how it would affect the searching speed.

In fact, the 15% setting is itself new. It was 5% before Sublevel asked, so I tried rasing it to 15% and rebuilding the index, but it turns out the word "submachine" is (surprisingly) really common around here. I'm currently rebuilding the index at 20%, we'll see if it works.

Edit: So, 20% wasn't enough either. Not sure if I'll try pushing it further.

wonder, what this "submachine" thingy is and why this word is so popular on this forum...

Yeah, I wonder which users insert it in their posts the most often.


c:

Search works again?

Fantastic!

Kaly_Ths wrote: ↑

16 Feb 2021 10:06

I'm posting this here and if you have any further suggestions, we can move it to another thread.

My browser shows me this when I try access the site through the WiFi of my block.

Screenshot_2021-02-16-09-52-52-744_com.android.chrome.jpg

Btw, I stay in a university campus doing an internship in the nearby school. So, they have something of a shared network I guess (?) and it counts this website as not safe for visiting?

So, trying to resolve some kind of https issue that Kaly_Th is is having.

Basically the browser is saying something is wrong with the ssl/tls certificate used to serve the website over https. The operative word here is "browser". It's not the network that's saying the website isn't safe, something goes wrong with the connection such that Chrome thinks the connection is unsafe. Normally, I would suspect a mistake in the website configuration - lots of things can go wrong with configuring https - but the fact that the error happens on one network but not the other would seem to rule this out.

Could you first verify that there's actually a https:// component in the address, then, click "advanced" and send whatever more detailed error information you see?

So, I tried to login today via WiFi and everything seems ok so far.

Ok, so apparently it propably had to do with my browser not being updated yet. I think yesterday it did automatically and now I think I can connect fine, for the moment at least.

I'm really sorry if it seems confusing enough. I'll check once more if I see the banning message again.

Ok here's the advanced;