(Ep 44) Securing User Data With Firestore Security Rules

Hi, by any chance do you have a video which you can link me to, that tackles the function of reading out-loud data fetched from Firestore as audio to user? Thanks

Really appreciate this, man. So hard to find explanations of how to write these. Agree with the cross-user data question from 'twitter at r..." Seems like the queries could get super complicated, but I need to figure this out for what I'm building. I checked your channel but didn't see an update.

Meanwhile, tactical question: I would have expected something like {documentID} or {document.id} as opposed to {userID}. It's not obvious to me how Firebase would understand that the documents names in the userData collection are themselves userIDs, even though I've seen this pattern and used it myself (albeit in Firestore). Thanks again!

does it matter if you use /userData/{userId} or /userData/{uid}? I use uid in my code and was wondering if it made a difference

phenomenal stuff - thank you Dave!

great

This video saved my life!

Great tutorial, such a great job, I have a question I have a collection, in which latitude and longitude of the user is stored as geopoint in an array.
What want to do is I want to show these geopoint in a separate application which will be used by admins/moderators. These points will be shown on the map. How do I achieve this, in terms of rules. I used the above one, because it threw me a caution that the server will start declining client accesses.

Could someone please help me with rules, I want to have an admin account that can see all users by their emails and names but nothing more, then be able to delete them so admin would need read and Wright rules and I don't know how to get this in my app

Thanks for the video

Thanks for the straightforward explanation

Awesome job. Any chance to teach how to create a group where you can add users and interact internally with them? Thanks!

Thanks for the info, Is there a way to have some kind of backup for the database just in case of any unexpected error, deletion or so?

I'm beg iOS dev, so I'm not following your courses. But this was really helpful.. Thank you for great explanations!

thanks

nice video...but its worth mentioning that your app is specifically designed to be used on a per user basis. Meaning, no user looks at anyone else's data..i.e, traveling expenses, current budget, etc...if you're building an app that engages all users within the app, your rules will be more involved....great video by the way nice explanation

Great stuff, such a great job you're doing with this series. Thanks again Dave.

You're getting good at this man!

Thanks again💯

I have an app which requires all firebase data to be encrypted, so no-one can see the original plaintext data. In your opinion what would be the best approach to take to achieve this? Great content btw man!

Thank you. 🙂🙂