Okay my actual like system is kinda energy-intensive regarding api requests. So im going for a fresh start. Ive got a collection movie_liked who gonna store all movie likes. Each document gonna as :
- userID
- movieID My first problem, is how prevent when liking, not have duplicate like for the same user with the same movie ? There no solution without making a check before (listDocument,....) ?
Ideally, I would like to have a single request to like or dislike a movie (like on Youtube, etc...) but I guess for that we need to have a custom backend with custom api request
You can add 1 unique index on userId and movieId
Yeah my bad. But right now I try to create an api route in my NextJS app like this :
/api/user/${userId}/movie/${movieId}/like for the like, but Ive got an error about user_unauthorized. That weird because its working with function, but not with api routes. I guess its because when using api routes, we dont have the user token to authorize the request
You're right. The session is client side and there is no session server side
Recommended threads
- Issue with OAuth 2.0 authentication
Good evening, I’m reaching out because I’m having a small issue with Appwrite. I’m trying to set up OAuth2 with Twitch, and even though I’m entering the correc...
- Domain Help
My domain estimately.me is verified in Appwrite DNS but SSL certificate keeps failing with: DNS problem: server failure at resolver looking up A for estimately....
- What's the proper way to delete user acc...
I would like to provide an option for the users of my app, to completely remove theirs account if they want to. I don't want to 'deactivate' the account, but to...