Obsidian looks interesting.

Thanks for the suggestion, but it seems like the challenges with Komga would be similar to those when using Mylar. I’ll probably just go for a spreadsheet.

That was my first idea too, but last I checked it didn’t scrape much other than English editions (using Comicvine AFAIR) and had no way of manually adding stuff it can’t scrape.

Scraping metadata. Wish/purchase/pull lists. Keeping track of multiple editions. Perhaps even scraping entire collections/storylines into manageable lists?

At the very least a quick way to use my phone to check if I already have a specific comic when I’m at the store.

Grist might be useful if I end up setting more than a spreadsheet up, thanks.

Thanks for the suggestion. I think that might be too much work for my needs though.

The container sees each volume as a seperate filesystem, regardless of your underlying disk setup and you cannot hardlink across filesystems.

This is not how you raise an issue on Github.

This has huge potential. What I personally look for in a podcast solution is:

• Web/desktop player
• Sync between players (down to seconds)
• Organize subscribed podcasts with folders/tags
• Per podcast/folder/tag settings for “automatically add to queue”
• Some way of dealing with older (backlog) episodes (built-in or via an API)

For now, I’m using Pocketcasts which pretty much does what I need, except for handling the backlog, which I do with a homemade python-script that adds backlog episodes to my playlist whenever it has less than 4 hours of playtime left, using Pocketcast’s web player REST API. The result is an endless playlist where newly released episodes are played within a few hours and older episodes are sprinkled on with no real need for micro-managing episodes in the playlist.

It looks like web/desktop players and sync is already in scope, but are there any “advanced” podcast organization features on your roadmap?

That is not correct. Prowlarr also searches Newznab-compatible providers (i.e. most nzb-indexers).