this post was submitted on 13 Mar 2026
8 points (100.0% liked)
Programming
26072 readers
65 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is fundamentally how Firebase etc. is meant to work: the client talks directly to the database, and security rules gate access. You don't need your own backend in between.
As for the spam issue, you're right that supabase can't do it (firebase can btw.)
https://github.com/orgs/supabase/discussions/36512
https://github.com/orgs/supabase/discussions/19493
Not sure what the best approach is, but for me it just sounds like supabase is not ready for real world production.
ps:
trailbase seems to do user rate limiting by ip through a reverse proxy. I'm sure the same can be done for supabase. https://trailbase.io/documentation/production/#reverse-proxy