Has Jeffrey ever mentioned the reason why he isn't offering the social login via Github or Google?
This is one of the very few things I think should be improved here.
With something like Socialite it is dead simple to implement. I am putting it on all my projects, especially the Facebook and Google logins are quite popular. I would imagine that Github would be a very popular choice on Laracasts.
Personally I find it so tedious to use passwords like that on every page. Especially if you are on the phone having just a button to click on is super nice.
Perhaps he mentioned it somewhere, why he stays away from it?
Out of curiosity I watched the Socialite video tutorial by Jeffrey and he did a sloppy job with it to be honest. Out of the gate, his code will throw an error if the user tries to register manually with the same email he is using with Github. Another shortcoming of his code is that he uses auth/redirect and callback urls specifically just for github. He should use a {service} parameter in the route so you can use if condition (facebook, google, ...) and perhaps set it to github as default to make it future proof.
@BigFur If you are referring to the Larabit on github socialite, it wasn't meant to dive into further & more improved functionality, it was just supposed to be a quick video explaining how to use the socialite package to do handshake authorisation via the github oauth api, which he fully covered in the video.
If you want a starter package that has a lot of features pre bundled into it, I suggest you try Joel Butcher's SocialStream - which as the name suggests, combines socialite with jetstream plus a lot of advanced features that are highly configurable. It can be found here & has a really good docs written for it (link in github discription). I would suggest checking it out, it may have the features that you were hoping for in the Video (such as not throwing error when a user tries to register with an already attached account)
