Lidarr VS Huginn

I highly recommend Lidarr for organization/naming of your library. It's usually associated with piracy, but I just use it to maintain my self-ripped library and ensure that Plex has no issues discovering all my media.

Lidarr: Manages music libraries.

Lidarr + Jellyfin?

Lidarr handles your music downloads, sorts them and adds the correct metadata for your library to be picked up by Jellyfin. It will also upgrade your media if a better version is found. https://lidarr.audio/ there is also lidarr extended, which has extra features https://github.com/RandomNinjaAtk/docker-lidarr-extended

This method doesn't help at all, or I am doing something entirely wrong.

Lidarr (Music): https://github.com/Lidarr/Lidarr Lidarr can also pull down new album releases for artists, but that's something I usually have turned off (the artists I love I buy the CD for anyway).

Try https://lidarr.audio/

Lidarr: Music

Just a side note there is lidarr that has webui that handles music, not tried soulseek looking at it now, so don't know if it's the same..

I skipped to chapter 9 in the article ("Clogged"), and it looked like Pipes failed because it didn't have a large enough team or a well-defined mission. As a result they couldn't offer a super robust product that would lure in enterprise users. "You could not purchase some number of guaranteed-to-work Pipes calls per month" is the quote from the article.

The reason I think that interesting is because that's the model these days for everything from AI tokens to Monday.com seats. It makes me feel like Pipes was before its time.

That said I've been collecting different "business glue" products that are similar to Pipes. To me, like you say, they aren't as interesting, exciting and intuitive as Pipes was, but maybe it just takes a little more digging. I tried to focus on open source tools but some aren't.

- n8n io: https://n8n.io/integrations/mondaycom/

- Node-RED: https://nodered.org/ (just read about this one in this thread)

- trigger dev: trigger.dev

- automatisch.io: https://automatisch.io/docs/

- Activepieces: https://www.activepieces.com/docs/getting-started/introducti...

- Huginn: https://github.com/huginn/huginn

- budibase: https://budibase.com/

- windmill: https://www.windmill.dev/

- tooljet: https://www.tooljet.com/workflows

- Bracket: https://www.usebracket.com/pricing (just SalesForce <-> PostgreSQL)

- Zapier: zapier.com/

Anyway I hope some of these are fun!

"correct" is a value judgement that depends on lots of different things. Only you can decide which tool is correct. Here are some ideas:

- https://camel.apache.org/

- https://www.windmill.dev/

- https://github.com/huginn/huginn

Your idea about a queue (in redis, or postgres, or sqlite, etc) is also totally valid. These off-the-shelf tools I listed probably wouldn't give you a huge advantage IMO.

Huginn (https://github.com/huginn/huginn) has like some 39K stars on Github and the use cases it covered looks good.

Huginn is an another useful tool that allows you to wrangle CSS selectors and XPath nodes to create RSS feeds.

I use it quite successfully to get data out of undocumented APIs and out into RSS.

https://github.com/huginn/huginn

I know of Huginn that could be usefull depending on what you want to do.

https://github.com/huginn/huginn ??

Huginn

"not a single word about the safety implications of such a system"

Oh please. Not everything has to be regulated-to-hells before a use case is even found on this. Autonomous agents have existed for decades.

If it can automate agents like huginn[0] with natural language, I'd be very happy. Autonomous agents doesn't mean it's going to take over the world autonomously. Let's lower the fearmongering a bit.

[0]: https://github.com/huginn/huginn