Kyle Paul

This is due to the cascading nature of [Firebase RTDB Rules](https://firebase.google.com/docs/database/security/securing-data#read_and_write_rules_cascade). Since the secured areas are nested within a parent that allows anyone to read, it would require some refactoring...

@MrCsabaToth I plan on testing your PR tonight and will merge asap.

Accepted PR #45 to move this project onto Angular 9. @MrCsabaToth do you mind updating PR #31 to sort out the merge conflicts? Thanks in advance!

In order to build this out using anonymous auth, there are a few sections that would need additional logic to determine if it's an "anon user" or a "fully authed"...

Correct and what I was implying with the list of areas that would need to have additional logic. With the "Attendee Schedule" feature, that should only show up if fully...

With the rules updated in [015c1e6](https://github.com/neojato/DeLorean-v2/commit/015c1e68226efa380a386f28fbff13dda26c23bf) I'm keen to close this one as I've not been able to reproduce the security issue mentioned.

Apologies for the delayed response, it seems the error message from the library we're using isn't fully exposing the issue. See here: https://github.com/airhadoken/twitter-lib/issues/37 tl;dr - You now need [Elevated access...