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.36 major release version of the websurfx project which was released on the 26th of January.

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, MickLesk and SchweGELBin 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.24.36 updates the hybrid caching api to 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

I just ran into the wonderful error message

the trait is not dyn compatible because method publish_video is async

and boy, what a rabbit hole. I found out about async_trait which resolves this by turning async methods into fn method() -> Pin<Box<dyn Future + Send + 'async_trait>>, but I thought that's what the async fn was syntax sugar for??? Then I ran into this member-only medium post claiming

Rust Async Traits: What Finally Works Now

Async functions in traits shipped. Here’s what that means for your service interfaces.

But I clicked through every rust release since 1.75.0 where impl AsyncTrait was shipped and couldn't find a mention of async. Now I'm just confused (and still using async_trait). Hence the question above...

Managarr v0.7.0 has been released with Lidarr support!

What is Managarr?

Managarr is a terminal-based application for managing all your Servarr instances from one place. It provides a user-friendly interface to interact with your media libraries, making it easier to manage your downloads, monitor your artists and albums, and perform various actions directly from the terminal.

It sports two modes: a TUI mode (Text-based User Interface) and a CLI mode (Command Line Interface).

TUI mode gives you an interactive User Interface right inside your terminal window, allowing you to navigate through your Sonarr and Radarr libraries, view details about your series and movies, and perform actions like adding or removing items, all through keyboard shortcuts.

CLI mode lets you execute commands directly from the terminal to manage your Servarr instances without needing to open the TUI. This is great for quick tasks or for integrating with scripts and automation tools.

Screenshots

Try it out for yourself using the in-browser demo!

If you want to try it out for yourself without installing it first, you can use the Managarr demo-site: https://managarr-demo.alexjclarke.com/

What Lidarr operations are supported?

📚 Library Management

• Artist Library - Browse, search, filter, and sort your music collection
• Add Artists ➕ - Search for new artists and add them with full config options (quality profile, metadata profile, root folder, monitoring options)
• Edit Artists ✏️ - Tweak artist settings including quality profiles, metadata profiles, tags, and monitoring status
• Delete Artists 🗑️ - Remove artists from your library with optional file deletion
• Artist Details 🔍 - Get the full picture on any artist:
  • Overview, disambiguation, type, status, genres, and ratings
  • Album list with release dates, track counts, and download status
  • Artist history with detailed event info
  • Manual discography search with release selection and download

💿 Album & Track Management

• Album Details - Drill into individual albums to see:
  • Track listing with audio info (codec, channels, bitrate, sample rate, bit depth)
  • Album history
  • Manual album search for grabbing specific releases
• Track Details 🎼 - View individual track info and history
• Delete Albums - Remove individual albums from your library

⬇️ Downloads & Queue

• Downloads Tab - Keep an eye on active downloads and manage your queue
• Blocklist 🚫 - View and manage blocked releases

📜 History

• Full History Support - Browse, search, filter, and sort Lidarr event history
• History Details - Dig into the details of any history event
• Mark as Failed ❌ - Mark history items as failed

🔎 Indexers

• Indexer Management - View, add, edit, and delete indexers
• Indexer Settings ⚙️ - Configure global indexer settings
• Test Indexers 🧪 - Test individual or all indexers at once

📁 Root Folders

• Root Folder Management - Add and manage root folders for your music library

🖥️ System

• System Status - View Lidarr system info and health checks
• Tasks - View and trigger system tasks
• Queued Events - Monitor queued system events
• Logs 📋 - Browse system logs
• Updates 🆙 - Check for and view available updates

⌨️ CLI Commands

Full Lidarr CLI support for all the things!

managarr lidarr list artists|albums|tracks|indexers|root-folders|tags|quality-profiles|...
managarr lidarr get artist|album|track|...
managarr lidarr add artist|root-folder|tag|...
managarr lidarr edit artist|indexer|indexer-settings|...
managarr lidarr delete artist|album|root-folder|tag|blocklist-item|...
managarr lidarr search artist|album|...
managarr lidarr refresh artist|downloads|...
managarr lidarr trigger-automatic-search artist|album
managarr lidarr manual-search artist|album

Managarr also supports Radarr and Sonarr!

If you're running the full *arr stack, Managarr has you covered - It supports Radar and Sonarr too, all from the same interface!

This is a passion project so I'd love to hear your feedback, feature requests, or any bug reports you find.

A short blog post that reviews the development of kellnr, the Rust crate registry, in 2025.

Is it just me, or does Rust feel much more bare-bones than other languages? I just started learning it recently and this is the one thing that stood out to me, much more so than the memory management business. A lot of things that would normally be part of the language has to be achieved through meta-programming in Rust.

Is this a deliberate design choice? What do we gain from this setup?

Edits:

1. Somehow, this question is being interpreted as a complaint. It's not a complaint. As a user, I don't care how the language is designed as long as it has a good user experience, but the curious part of my mind always wants to know why things are the way they are. Maybe another way to phrase my question: Is this decision to rely more on meta-programming responsible for some of the good UX we get in Rust? And if so, how?
2. I'm using meta-programming to mean code that generates code in the original language. So if I'm programming in Rust, that would be code that generate more Rust code. This excludes compilation where Rust gets converted into assembly or any other intermediate representation.

cross-posted from: https://lemmy.bestiver.se/post/854816

Comments

cross-posted from: https://lemmy.bestiver.se/post/851393

Comments

I've been building a bytecode VM in Rust and recently implemented NaN boxing for value representation. Sharing here for anyone interested.

I needed all VM values (booleans, integers, string pool indices, bytecode references) to fit in 64 bits (stack is Vec).

My implementation encodes 5 distinct types using a 3-bit tag and 32-bit payload, all within a single u64. It also has 15 unused bits, they may be used later for types expansion.

I'm using a 64-bit layout:

• Bits 63-51: Quiet NaN signature (0x7FFC...)
• Bits 50-18: 32-bit payload (integers, string pool indices, etc.)
• Bits 17-3: Unused/ (15 bits)
• Bits 2-0: 3-bit type tag

So it allows me to have 5 tagged types: TRUE_VAL, FALSE_VAL, STRING_VAL, CALLDATA_VAL, U32_VAL

Developer @tracyspcy@lemmy.ml

Link to original post by madmo@programming.dev

Developer @tracyspcy@lemmy.ml

cross-posted from: https://lemmy.bestiver.se/post/834991

Comments