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. 🙂

You’re welcome :)

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 :).

I am sorry for being late to reply, I think I would suggest opening an issue on this topic here:

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

Because I feel it would be better to have a discussion there. Also, I will be able to explain in more depth :).

Sorry for the delay in reply.

Great project, thanks for sharing.

You’re welcome :).

Quick question: will this be self-hosted only or will there be a public instance or something the like?

Yes, actually we are working on providing a page dedicated to allow everyone in the community to contribute their Websurfx instance which will allow others to use them and try them out. Something similar to what Searx does (searx.space). So right now it is still a work in process.

Sorry for the delay in reply.

Thanks for checking out my project :). Though right now we do not provide a public instance right now, but we are already working on this. Like we are working to provide a page dedicated to show all the instances hosted by the community members which will allow others to use them and try them out as well :).

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.