Podgrab VS flood

I use Podgrab[0].

Light footprint, easy to use -- and no reliance on Google or anyone else.

[0] https://github.com/akhilrex/podgrab

I found a great tool for myself as a programmer here but not everybody knows how to set that up https://github.com/akhilrex/podgrab. So I build a simple little website here for anybody who has the same problem.

Something podgrab could fix? https://github.com/akhilrex/podgrab

How does it compare to podgrab?

I created an alternative for [Podgrab](https://github.com/akhilrex/podgrab) named [PodFetch](https://github.com/SamTV12345/PodFetch) it contains more features than Podgrab and also includes many bug fixes like a local RSS feed. (Bonus: The backend is written in Rust :D ). You can search podcasts via iTunes or via PodcastIndex.org, download, find local podcasts or subscribe to the local rss feeds.

Podgrab to download my podcasts

I am thinking that if users are willing to automate a workflow to download new episodes to their Plex Library ( just came across podgrab (https://github.com/akhilrex/podgrab) which makes me think automating episode download to Plex library should be easy. And then your podcast app can do the magic you have done with Prologue.

It looks like there's an option to export an OPML file containing Podgrab feed links, which could then be imported into any application (I like AntennaPod)

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Only one that I'm aware of is Flood: https://github.com/jesec/flood

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile

https://flood.js.org/ ?

If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)

qbitorrent-nox with flood-ui

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood