Thanks ❤ for trying out our project. Yes, that is something that is being worked on currently. Though some pages do support mobile layout, but others are a work in progress. So they will be worked on soon, probably in the next few releases. 🙂

Thanks ❤️ for trying out. If you encounter any problems/issues. Then feel free to ask them here. 🙂

Thanks ❤️ for asking this question. Yes, exactly the search engine does not share any data except the search query and IP address and nothing else making it really private though we will be adding tor and I2P feature which will also remove the concern of sharing the IP address to the upstream search engine as well. 🙂

Ok, thanks ❤️. I really appreciate your help. 🙂 .

Ok sure, thanks for the suggestion, I would make the change as soon as possible. Also, next time, I would make sure to provide a brief description with the release announcement.

Thanks for taking a look at my project 🙂 .

We are already planning to have an initial support for this added soon in the coming releases. Right now, we are looking for someone who has more in depth knowledge on how to manage memory more efficiently like reduce heap usages, etc. So if you could help with this, I would suggest letting us know. 🙂

Yes, I have found the fix. I will publish it tomorrow morning as soon as possible, so no worries :).

Sorry for the delay in the reply.

Thanks for the feedback :).

Sorry for the delay in reply.

Thanks for the suggestion :). We are already having plans of supporting this in the near future.

Sorry for the delay in reply.

Thanks for checking out my project. We are already working on fixing this issue, and we will fix it soon as possible as :).

Also, I would suggest following this issue. Here I explain on how to fix this issue.

Here is the link:

https://github.com/neon-mmd/websurfx/issues/242

If you find any difficulties, just leave a reply on this issue. We would be glad to help :).

Sorry for the delay in reply.

Building on BastingChemina’s comment. Thanks for the help :).

Sorry for the delay in reply.

Thanks aksdb you are in ;).

Sorry for the delay in reply.

Thanks for the suggestion :). Even I myself hate ads and I avoid doing so, but I just did add that just to emphasize that my project is also open source and does not support ads. Because if I don’t add this then it can raise some doubts whether it is open source or not and whether it supports ads or not. So to make it clear, I added it :).

Sorry for the delay in reply.

Yes, it is, but I just wanted to emphasize that my project is also open source and does support privacy. If I don’t add this then it can raise some doubts whether it is open source or not and whether it is privacy respecting or not. So to make it clear, I added it :).

Ok no problem :). If you need any help regarding anything, just DM us/me here or at our Discord server. We would be glad to help :).

Ahh, I see, Why didn’t I remember this before that I can do something like this. Thanks for the help :). Actually the thing is I am not very good at docker, and I am in the process of finding someone who can actually work on in this area like for example reducing build times, caching, etc. One of the things we want to improve right now is reducing build time like I am using layered caching approach but still it takes about 800 seconds which is not very great. So if you are interested then I would suggest making a PR at our repository. We would be glad to have you as part of the project contributors. And Maybe in future as the maintainer too. Currently, the Dockerfile looks like this:

FROM rust:latest AS chef
# We only pay the installation cost once,
# it will be cached from the second build onwards
RUN cargo install cargo-chef

WORKDIR /app

FROM chef AS planner
COPY . . 
RUN cargo chef prepare --recipe-path recipe.json

FROM chef AS builder
COPY --from=planner /app/recipe.json recipe.json
# Build dependencies - this is the caching Docker layer!
RUN cargo chef cook --release --recipe-path recipe.json

# Build application
COPY . .
RUN cargo install --path .

# We do not need the Rust toolchain to run the binary!
FROM gcr.io/distroless/cc-debian12
COPY --from=builder /app/public/ /opt/websurfx/public/
COPY --from=builder /app/websurfx/config.lua /etc/xdg/websurfx/config.lua # -- 1
COPY --from=builder /app/websurfx/config.lua /etc/xdg/websurfx/allowlist.txt # -- 2
COPY --from=builder /app/websurfx/config.lua /etc/xdg/websurfx/blocklist.txt # -- 3
COPY --from=builder /usr/local/cargo/bin/* /usr/local/bin/
CMD ["websurfx"]

Note: The 1,2 and 3 marked in the Dockerfile are the files which are the user editable files like config file and custom filter lists.

Sorry for the delay in the reply.

Ok, thanks for suggesting this out. I have not thought about particularly in this area, but I would be really interested to have the docker image uploaded to docker hub. The only issue is that the app requires that the config file and blocklist and allowlists should be included within the docker hub. So the issue is that if a prebuilt image is provided, then is it possible to edit it within the docker container ?? If so then it is ok, otherwise it would still be good, but it would limit the usage to users who are by default satisfied by the default config. While others would still need to build the image manually, which is not very great.

Also, As side comment in case you have missed this. Some updates on the project:

• We have just recently got the custom filter lists feature merged. If you wish to take a look at this PR, here.
• Also, recently there has been ongoing on getting new themes added, and an active discussion is going on that topic and some themes’ proposal have been placed. Here is a quick preview of one of the theme and what it might look like:

Home Page

Search Page

Hello again :)

Sorry for the delayed reply.

It is essentially, how we are achieving the Ad-free results is when we fetch the results from the upstream search engines. We then take the ad results from all of them, bring it to a form where it is aggregatable and then aggregate it. That’s how we achieve it.

Hello again :)

Sorry for the delayed reply.

Right now, we do not have ranking in place, but we are planning to have it soon. Our goal is to make it as organic as possible, so you don’t get unrelated results when you query something through our engine.

What the project does is it takes the user query and various search parameters if necessary and then passes it to the upstream search engines. It then gets its results with the help of a get request to the upstream engine. Once all the results are gathered, we bring it to a form where we can aggregate the results together and then remove duplicate results from the aggregated results. If two results are from the same engine, then we put both engine’s name against the search result. That’s what is all going, in simple terms :slight_smile: . If you have more doubts. Feel free to open an issue at our project, I would be glad to answer.

Yes, it is, but I just wanted to emphasize that my project is also open source because if I don’t add this then it can raise some doubts whether it is open source or not. So to make it clear, I added it.