Suggestion About Base64 encode can be decoded on search bar

[ハオフ]

Greetings mods and devs. So just found out that the links i encode using built-in Base64 encode can just be searched up using the search bar.

For example, if i searched Alezonyth on search bar, it shows the base64 encoded text on the search results
The thing is, using Base64 is to hide the creators name from plain sight so they can't search their name easily, but if it still doesn't hide anything. That's a bit useless isn't it?

So if i may suggest, text with encoded base64, shouldn't be able to be decoded just by searching on search bar.

Sorry if my explanation is bad, here the example of picture

 

[Checkmate]

I'll see what I can do

 

[Checkmate]

Thank you, this is confirmed a bug and it will be triage.

 

[ハオフ]

Thank you <3

 

[Checkmate]

This had been fixed

 

[anioshi200us]

@Checkmate would it be possible to allow this behavior for Elite / recognized member? I don't think creators would manage to get Elite or recognized.

 

[Checkmate]

@Checkmate would it be possible to allow this behavior for Elite / recognized member? I don't think creators would manage to get Elite or recognized.

Sorry, this is not possible due to budget problem, I'd technically maintain two index, and one index cost 64GB ram x 3 servers, that's a total of 192GB of ram for the one index for search system alone. This already cost more than a kidney on today's ram price.

 

[anioshi200us]

Sorry, this is not possible due to budget problem, I'd technically maintain two index, and one index cost 64GB ram x 3 servers, that's a total of 192GB of ram for the one index for search system alone. This already cost more than a kidney on today's ram price.

Make sense. What about offering something like "automatically search base64 variant"? It would be two search on the same index.

 

[Checkmate]

I don't want to bored you but there are several technical challenges in this design.

First, I need to determine who can search for what. For example, if you type in "alezonyth," the server processes your query and returns results that may include both desired and undesired outcomes. I also need a reliable method to decide who gets to see each result, which is complicated. How do I distinguish between good and bad results for a specific membership class?

Additionally, there are security implications to consider. There are also extra checks involved, and processing time significantly reduces capacity for everyone. Guest searches are subject to the same processing rules, meaning that I would need to allocate extra CPU time for every search. We process hundreds thousand of searches per second, generating about 120GB of keywords everyday.

For instance, if someone searches for "hentai game," that constitutes one keyword, approximately 0.01KB. Therefore, 120GB of keywords every day translates to millions of individual searches.