{"action":"created","issue":{"url":"https://api.github.com/repos/firebase/emberfire/issues/239","labels_url":"https://api.github.com/repos/firebase/emberfire/issues/239/labels{/name}","comments_url":"https://api.github.com/repos/firebase/emberfire/issues/239/comments","events_url":"https://api.github.com/repos/firebase/emberfire/issues/239/events","html_url":"https://github.com/firebase/emberfire/issues/239","id":67973061,"number":239,"title":"Feature Comparison to AngularFire... what is missing from EmberFire","user":{"login":"brendanoh","id":3473461,"avatar_url":"https://avatars.githubusercontent.com/u/3473461?v=3","gravatar_id":"","url":"https://api.github.com/users/brendanoh","html_url":"https://github.com/brendanoh","followers_url":"https://api.github.com/users/brendanoh/followers","following_url":"https://api.github.com/users/brendanoh/following{/other_user}","gists_url":"https://api.github.com/users/brendanoh/gists{/gist_id}","starred_url":"https://api.github.com/users/brendanoh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brendanoh/subscriptions","organizations_url":"https://api.github.com/users/brendanoh/orgs","repos_url":"https://api.github.com/users/brendanoh/repos","events_url":"https://api.github.com/users/brendanoh/events{/privacy}","received_events_url":"https://api.github.com/users/brendanoh/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/firebase/emberfire/labels/discussion","name":"discussion","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-04-12T23:28:20Z","updated_at":"2015-04-15T22:53:22Z","closed_at":null,"body":"I am under the impression that AngularFire includes AUTH and Presence (and Idle) features that I personally feel are vital in getting the most out of Firebase.\r\n\r\n@tstirrat @sararob are either of these in your plans for EmberFire?\r\n\r\nCurrently I am using ToriiFire for managing social logins but it actually has some issues. Since login and presence are so tightly bound I really feel like either within EmberFire ala AngularFire or a separate Firebase supported Add on would be the way to go here.\r\n\r\nThoughts? Comments?"},"comment":{"url":"https://api.github.com/repos/firebase/emberfire/issues/comments/93591111","html_url":"https://github.com/firebase/emberfire/issues/239#issuecomment-93591111","issue_url":"https://api.github.com/repos/firebase/emberfire/issues/239","id":93591111,"user":{"login":"brendanoh","id":3473461,"avatar_url":"https://avatars.githubusercontent.com/u/3473461?v=3","gravatar_id":"","url":"https://api.github.com/users/brendanoh","html_url":"https://github.com/brendanoh","followers_url":"https://api.github.com/users/brendanoh/followers","following_url":"https://api.github.com/users/brendanoh/following{/other_user}","gists_url":"https://api.github.com/users/brendanoh/gists{/gist_id}","starred_url":"https://api.github.com/users/brendanoh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brendanoh/subscriptions","organizations_url":"https://api.github.com/users/brendanoh/orgs","repos_url":"https://api.github.com/users/brendanoh/repos","events_url":"https://api.github.com/users/brendanoh/events{/privacy}","received_events_url":"https://api.github.com/users/brendanoh/received_events","type":"User","site_admin":false},"created_at":"2015-04-15T22:53:22Z","updated_at":"2015-04-15T22:53:22Z","body":"> Instead, you want to manage presence from the single user model that represents your currently logged in user. \r\n\r\nI would suggest this to be a mixin to the **controller** or **service** that manages session state and not a model at all.\r\n\r\n> This is difficult to make both generic and useful. It's why I think exposing the record.ref() is a good start.\r\n\r\nBased on having a mixin in the user model to access this data then I would think only things required in the mixin would be `lastActivity` and `lastOnline` (really last disconnect). Everything else seems calculable from that I think. See comment below.\r\n\r\n> In regards to your mixin, it's a nice idea. However, I think this kind of thing is very app specific. e.g. If I was creating a chat app I would likely use a single field of status that has the possible values: online, idle, away, dnd, offline. All of which are managed by some custom app logic, incl. some use of idle.js, and use of record.ref().onDisconnect(). In another app I might only care about online, another I might care about lastActivity.\r\n\r\nI wasn't suggesting a finished implementation. The only things required in the mixin would be `lastActivity` and `lastOnline` (really last disconnect). The online was a simple sample of how to do your own implementation."}}