- cross-posted to:
- webdev@programming.dev
- opensource@lemmy.ml
- selfhosted@lemmy.world
- cross-posted to:
- webdev@programming.dev
- opensource@lemmy.ml
- selfhosted@lemmy.world
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.15.0
major release version of the websurfx
project which was released on the 25th of March.
If you are new, and you don’t know what is websurfx
then 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 release v2.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, ddotthomas and evanyang1 who have been invaluable to the project. Also, Websurfx
would 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.15.0
introduces the new ranking algorithm for search results on the search page which ranks the results based on the relevancy to the user’s search query.
Changelog
The changelog of all the changes can be found here:
https://github.com/neon-mmd/websurfx/releases/tag/v1.15.0
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 ✨.
Thank you for your hard work. I had come across your pervious post a while back; good to see it’s going well. Will try it, also looking forward to ARM support
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. 🙂
Unfortunately, I’m not a programmer. If I had more free time I could possibly help with your hosting infrastructure, but that’s a no-go too at the moment. I’ll keep your requirements in mind though, if I do find someone
Ok, thanks ❤️. I really appreciate your help. 🙂 .
Cool project, congratulations! But got a question about privacy, to what extent is it private? As I see it still uses other search engines to search for things, is that we don’t share any other data except for the search query and IP addresses (if we aren’t using a proxy).
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. 🙂
That sounds great and I’m a user now, looking forward to the new features🖖
Thanks ❤️ for trying out. If you encounter any problems/issues. Then feel free to ask them here. 🙂
Pretty neat, though the first thing I noticed on a public instance was that it has no mobile formatting/layout, kinda a deal breaker for me at the moment. However I applaud the effort already done!
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. 🙂
As soon as you’ll get ARM support I’m definitely going to check this out!