Hey hey! We've talked with a bunch of people using notes and sheets to manage their libraries. Seems to be a common trend from people who want a little more control than Goodreads offers. Here's my take on each of these:
> 1. Is there a way to bulk edit a list?
Not today, but I love the idea. What were you hoping to do in bulk? Change a status? Add to list? etc?
> 2. Related to the first one, when I click the "Want to Read" big yellow button, it takes about 100-200ms for something to show or be clickable.
Yeah, good point. We do like 4 queries there to get all the data for the button, but we could do that in one query and get everything. That would speed it up. We've also talked about splitting the button into a "mark as want to read" button and a "dropdown" button. That way if you just want to mark as a book as "want to read" it's only 1 click.
> 3. When in Airlist when I click manage, nothing appears
Hmm, I see what you mean. That's supposed to be a dropdown with options for edit list, reorder list, save list ordering (in localstorage). But we're in the process of rebuilding that feature, which means sometimes there are no options there. Adding this to our issue tracker.
> 4. This is a suggestion, make it possible in the settings to configure what the home page
That's an interesting one! We've talked about two things that could help there. One is making the feed filterable. If we added feed items for blog post and you could set your filter to only show those that would work. The other thing was creating widgets to show in the left/right columns on the feed page. Do you feel like either/both of those would work?
> 5. Do you think it will ever be open source?
Yes! We have a path to open sourcing that we're starting down this year. It's a difficult one to run locally due to the 8 docker containers needed as well as a lot of local data for books. Right now a big advantage of the team is our agility, and at the moment open sourcing (and getting to the point people can actually run the app) would take some time.
We are thinking about open sourcing the front-end first though. In that case people would work on the Next.js app but use a staging API/database. Any thoughts on that kind of approach to start? Or are you much more curious about the Rails side?