It's very early days, and I have a lot of design work to do, but #Readlebee is on its way to becoming a reality!
If you have questions or want to discuss the project or contribute, check out the Gitter link, which lets you log in with a GitHub, GitLab, or Twitter account:
@Alamantus what book database are you using? Was wondering if BookBrainz could be useful to you. (Not much data in there just yet, but very open)
@Alamantus I am a nearly daily Goodreads user. I would LOVE to move to something open source, preferably self-hosted & federated. I don't have dev time right now, but I'll go open some feature requests for my favorite use cases. For extra fun, several are things Goodreads makes difficult to impossible.
@asparagi It's still so early that code help isn't what I need at the moment, so this is perfect! Be sure to check what's already planned in the wiki, but other than that, ideas (both design and functionality) are very helpful right now!
If you want to keep up with development, I just made a new account for posting Readlebee stuff over at @Readlebee.
Another way to help is by bolstering @inventaire's database, and there's a link pinned to the Readlebee account for how to do that!
@Alamantus I just looked at Inventaire's wiko and it confused the heck out of me. Then I looked at the website and well...
It seems to be aimed soley at physical books with isbns... Lots of books especally indie books no longer have a paper edition at all. There's a lot more cost to the author to produce a paperbook.
@Shutsumon It does enable the addition of digital editions, but the website itself is definitely more target toward something I don't find useful. It's the collection of book data specifically that is useful in my opinion. You can create and edit content freely, which is super handy for things like @Readlebee, which is currently set up to pull book data from their database!