3 ms·
Thanks for that, I've read and re-read the security and the rules pages of your docs several times, but still have questions. Reading through the firefeed rule
by galenko 14y ago
Thanks for that, I've read and re-read the security and the rules pages of your docs several times, but still have questions.
Reading through the firefeed rules file answered a lot of questions for me, except for these two:
1. Editing an existing tweet isn't allowed (".write": "!data.exists()"). How can you make it not editable, but deletable by the author?
2. How would you securely handle liking/unliking or upvoting/downvoting? write if authenticated, validate for the increase/decrease by one, if the user hasn't modified this before? How would that work? Would there have to be a child list of people who edited this? I'm just really curious about this specific use case as it seems pretty common in many apps, yet seems to me, would be really complicated to implement in firebase?
- mayop100 14y agoThe details here are a little off-topic for this HN thread. Could you open a thread on Stack Overflow and tag it "Firebase", or shoot us an email (support@...)? We support all of these use cases.
- tehwebguy 14y agoBummer, I was hoping to see an answer to this right here since it's such an important core concept! It would be worth the time to answer it, for sure. I'll go hunt for said answer but I imagine some others will not.
- galenko 14y agoI posted this on StackOverflow, as advised, maybe they'll answer us there: http://stackoverflow.com/questions/15728319/implementing-remove-tweet-and-like-upvote-functinality-in-firebase http://stackoverflow.com/questions/15728319/implementing-rem...