It seems like thre are really only a couple of options, and I haven’t found many review or examples that show enough detail to compare them.
Jellyfin has a bookshelf plugin that seems to be able to handle it. Audiobooks look to be accessed through the main client app, and ebooks through a companion app like JellyBook, which also claims to handle audiobooks.
On the other hand, there is Audiobookshelf, which specializes in audiobooks, but also claims to host ebooks. It has a number of client apps, but none that I found mention eBook reading.
I’ve found a couple of other solutions that seem more specialized. Maybe one of those?
I want to be able to read and listen on an Android device, preferably with a native app. I have a few comics, but mostly interested in books and audiobooks. I already have a Jellyfin server setup.
I think specific solutions for each type of content would be better in the long term if you have a lot of stuff to host, and management/organization will be better since they are catered to whatever the content type is.
Others have already said it, Audiobookshelf is a good one. For EBooks though, I would highly recommend Calibre Content server. Calibre is pretty much the defacto open source EBook manager out there, a lot of features and abilities specific to ereaders and ebooks of all formats.
There is little better for ebooks than Calibre, and Calibre Web if you’re into web apps.
For the audio book discussion, OP should use the “search” function, because there was a robust discussion about this in @selfhosted@lemmy.world within the past two months.
I think youre linking to a user instead of a channel but could be wrong. When i tried to access in Voyager it told me the user didnt exist.
Oh. Yeah, probably. I can never remember how Lemmy does communities; with a bang, maybe?
!selfhosted@lemmy.world
I wish the OSS communities would get together and pick a lane. Matrix uses #room:server, Lemmy does !community@server; does Mastodon use the same as Lemmy?
Standards, people. Let’s have some standards. Shame on whoever designed their protocol second.