vasanthk1125

We'll have subscriptions for extra features like Letterboxd does. All basic features though is free forever.

Phoenix doesn’t have built-in auth, and setting it up with Guardian (the JWT library for Elixir) took too much time. Since we were already using Supabase for Postgres, we decided to go with its auth to move faster. Supabase provides a UUID after authentication, which we then use throughout the rest of the database.

1. No, it just means completely free. And the website’s not going anywhere unless I die or something. I'll look into making this clearer.

2. Noted. We'll put up a proper email address. I just figured Discord would be faster.

They switched because it took more effort from users to rate on a 5 vs just saying good or bad. Because Netflix is a streaming service, casual users don't want to put in that much effort when they're chilling. Tracking is fundamentally different, where you go in with the expectation of organizing your library.

Thanks for the detailed comment!

1. Friends reviews on book is actually not that hard at all. We will implement it right after we get the friends and follow system working.

2. This one will take a decent number of users and ratings. We need a lot of data before we can make recommendations using ML.

3. Noted.

4. We will add that in the next few weeks. Filtering TBR seems to be a common request.

Thanks!

We'll definitely implement automatic review bombing protection. I'm thinking something like Steam does.

Do users create and moderate the group themselves? It seems like a subreddit, but for book related topics?

When I first started working on the website nine months ago, I didn’t even know what Postgres was, so going with an easier option made sense. Right now, we also use Supabase for auth and emails.

For queries, we don’t use Supabase’s API interface—we interact with Postgres directly through our backend

We’ll definitely have this at some point. A good recommendation system needs a solid base of user data, so it’s only possible once we have a larger user base. I really wanted to have this for the launch since it seemed so important for a book tracking platform but we didn't have the data to train models to make recommendations.

Not yet, but we’re rolling out a way to add missing books later this week!

LiveView just has fewer libraries. For example, we use a rich-text editor called TipTap, and I’m not sure there’s anything similar for LV.

Yeah, search is currently by book title and series name. It should handle typos pretty well—Meilisearch allows for up to two—but I still need to tweak it further

I'm curious—what would you like to do with the API?