I'm not familiar with this. At first look it seems like an alternative to Abs then something we would integrate.
Can you be more specific on what you would like to see with this integration?

It could be neat since Lissen refues to support SD cards, so smaller devices with those cards have to resort to other software. AntennaPod for example can pull books via the podcast API but you lose sync. (Antenna can sync via a local gpodder server, though this requires you do all the listening via podcast clients, so you can't switch between streaming on the desktop and caching chapters on a mobile when going outside.)

Gpodder support would be great as an option.

I really like the audiobookshelf android app but I don't like how complicated it makes it to manage podcasts. I have to always be connected to the server to still be able to listen to podcasts that I have not downloaded.

AntennaPod is dedicated to podcasts and supports the gpodder api. It handles podcasts and playback really well. I love being able to also just have all my audiobooks, ebooks, and podcasts managed by audiobookshelf but then when out and about, right now, the app is less convenient for me.

Gpodder api would be great to have the option to use other apps. But I also like the app and can see the benefits to managing all three types of media from the singular app if it fit better with my use case.

P. S. Thank you for all the work you guys put into this project:)

Would also love to see support for syncing with Gpodder. It would make ABS a significantly better podcast platform; currently the ABS Android app is not particularly good for listening to podcasts imo. With the Gpodder sync support, I could start a podcast on any app and pick it up, progress synced, on any other app or on the ABS web UI.

Any movement on this? I am also in the same boat where I would love to use different clients. For example the terminal client podliner also now supports this API and I'd love to be able to sync it with Audiobookshelf.

This seems like something that would be ideal as a plugin, rather than having ABS intrinsically add code for an unrelated service that in some ways overlaps with ABS itself.

Once plugins are supported, of course. :)