cross-posted from: https://programming.dev/post/45042331
Hello again!!
Sorry for the big delay in the announcements. I know it has been a long time I have not made any announcements but I will try my best next time this doesn't happen again.
So, through the medium of this post I would like to share with you all the
v1.24.36major release version of thewebsurfxproject which was released on the 26th of January.If you are new, and you don't know what is
websurfxthen I would suggest taking a look at my previous post here:https://programming.dev/post/2678496
Which covers in depth about what the project is and why it exists.
Credits
Before I share with you the
changelog, what this release version means and a preview on what we are planning to work on for the next major releasev2.0.0. I would first like to thank all our contributors and maintainers because of whom this was all possible. Specially I would like to thank spencerjibz, MickLesk and SchweGELBin who have been invaluable to the project. Also,Websurfxwould not have been possible without alamin655 and xffxff early involvement.
Thanks π to all the people involved in the project
Now, let's dive straight into what this release version actually means.
What does this release version means
This new release version
v1.24.36updates the hybrid cachingapito take advantage of the two layer caching solution which eliminates the round trip time delay of fetching the same results from the cache.Changelog
The changelog of all the changes can be found here:
https://github.com/neon-mmd/websurfx/releases/tag/v1.24.36
Preview of the goals for the next major release
- Different levels of privacy to choose from with the help of rust's conditional compiling features (In progress).
- Even more engines will be supported.
- Categories would be added to search results like images, news, etc.
- More themes will be provided by default
- More animations for the websurfx frontend will be supported.
- Multi language support would be added.
- I2p and tor support will be provided.
- Reduce animations would be added for those who don't want animations and effects on the frontend.
- And lots more β¨.
Call To Action
If you love our project and want to see it move ahead and progress in the direction you want, then we would suggest contributing at our project
Thanks π to all the people involved in the project
Thanks π to all the people involved in the project



Sorry for the delay in the response.
Your welcome π
The design vision for the
websurfxengine is to protect user's privacy, and to have a really secure and fast search engine along with that also provide a really customizable, safe (like the level of protection you want for the safe search to go even allowing you to use filter lists to filter out specific websites from the search results), highly theme-able, and with organic and ad-free search results. So that the user can get a search engine which is entirely their own.And for the case whether you should self-host it or use an instance of it depends on your threat level. Like many people because of your threat model may prefer self-hosting as they may not want to have their data served from a computer that is not their own.