A guide to Oauth2
milapneupane.com.np
A guide to Oauth2
1–10 of 55 posts
Re: A guide to Oauth2
#2> You want to add all your contacts in Gmail who are in skype
Never once in my lifetime I wanted to do that. For any two services.
Re: A guide to Oauth2
#3> You want to add all your contacts in Gmail who are in skype Never once in my lifetime I wanted to do that. For any two services.
True. These days we get all these kind of recommendations. We are not aware but we are granting access to our resources from one service to other services.
Re: A guide to Oauth2
#4> You want to add all your contacts in Gmail who are in skype Never once in my lifetime I wanted to do that. For any two services.
Not but I certainly wish for a way to merge all the contacts from thunderbird, my 3 web mail services, my phone et have them offline on my laptop.
Re: A guide to Oauth2
#5> You want to add all your contacts in Gmail who are in skype Never once in my lifetime I wanted to do that. For any two services.
Above that I think this is rude to my contacts: You can’t just go and upload random people’s data on plattforms of your choice.
I get it – people feel like it is their contacts because they collected them, but they are not. This should be illegal.
Re: A guide to Oauth2
#6I'm currently in the middle of implementing an OAuth 2.0 authorization server following the RFC draft of the best current practice [1].
It's been a huge pain navigating all the interlinked (and sometimes contradicting) RFCs around, especially with a distinct lack of resources for actually implementing an authorization server. RFC6749 does not suffice on its own since it says nothing about authentication or tokens payload (not that it should). I did discover the whole RFC universe which are mostly fascinating and very well written.
Most google searches end up to Auth0 (nice SEO!), which I'm sure is a fine product, but usually only gives a very high-level overview of the corresponding spec and ends up like "see how this is all complicated? there's a SAAS for that...".
I'm seriously considering implementing a fully spec-compliant OAuth 2.0 + OpenID Connect Core 1.0 reference server implementation in Typescript, with full documentation quoted straight from the RFCs. The HOW is actually pretty straight-forward once you've figured out the WHAT and WHY.
[1] https://tools.ietf.org/html/draft-ietf-oauth-security-topics
Re: A guide to Oauth2
#7I'm currently in the middle of implementing an OAuth 2.0 authorization server following the RFC draft of the best current practice [1]. It's been a huge pain navigating all the interlinked (and sometimes contradicting) RFCs around, especially with a distinct lack of resources for actually implementing an authorization server. RFC6749 does not suffice on its own since it says nothing about authentication or tokens pay…
I would love to see a reference server implementation for OAuth 2.0 & OpenID Connect Core 1.0, as it would be quite helpful when I go to add OAuth 2.0 to the libre software suite we use at work!
Re: A guide to Oauth2
#8> You want to add all your contacts in Gmail who are in skype Never once in my lifetime I wanted to do that. For any two services.
Above that I think this is rude to my contacts: You can’t just go and upload random people’s data on plattforms of your choice . I get it – people feel like it is their contacts because they collected them, but they are not. This should be illegal.
Is it even legal to upload contacts under GDPR?
Re: A guide to Oauth2
#9> You want to add all your contacts in Gmail who are in skype Never once in my lifetime I wanted to do that. For any two services.
Above that I think this is rude to my contacts: You can’t just go and upload random people’s data on plattforms of your choice . I get it – people feel like it is their contacts because they collected them, but they are not. This should be illegal.
That's why my dream contact platform would feature client side encryption. We should have a bitwarden/lastpass/1password for contacts, that synchronizes it across my services and devices, with a solid API + permission scheme to share with other apps.
I currently have at least 6 places where my contacts are stored (should I say scattered). I have no way to search them all, tag them all, archive the ones I seldom need, have versioning of the various data, etc.
Besides, contacts are a very broad topic.
I have contacts for friend and families, I have girls I'm flirting with, I have clients, I have administration offices, hair cutters, providers, restaurants... For some of them I want a way to contact them, some of them the location, some I don't want to appear in the main listing, some I want to explicitly hide from people peeking at my phones, some I want to easily share or even synchronize with others.
And then there is the way things are labelled. When going networking, I will collect many contacts I want to isolate. I want to be able to search them from a "known from" fields, or a "industry" tag. I want to make groups to mass communicate: I organize parties and sport events, and the best way to get people on board is still direct texting, and optional calling: fb events don't cut it.
It's one of those simple topics that aren't solve.
There is still no simple way to just send files from any computer to another. Try telling your mum to send you this videos from their iPhone to your laptop now that the wifi is down. Or share 3Go of photos with this group of 20 persons you just met on a trip.
There is still no simple way to make check lists (not to do list, mind you, there are plenty of those).
Having a personal archive of documents and notes sucks. Best effort used to be Evernote and MS one note. Proprietary plateform and standards, lock ins and of course they access your stuff.
Noting stuff on the way is hacking. I use telegram self-messaging for that because it let me quickly write, film, record stuff and queue them in a thread that sync accross my devices.
And contacts are still a mess. Once in a while, you receive the "I changed my phone/lost my contacts/new email/made a mistake" text asking "who is this ?". I still note metadata in the "name" field of contact to remember where I know the person from, or the name of their children to avoid being awkward when meeting them again.
Still we have an amazing free map of the entire world, more quality video content we can ever consume and encyclopedic knowledge of my entire field of expertise at my fingertip.
The way computer evolved is weird.
Re: A guide to Oauth2
#10I'm currently in the middle of implementing an OAuth 2.0 authorization server following the RFC draft of the best current practice [1]. It's been a huge pain navigating all the interlinked (and sometimes contradicting) RFCs around, especially with a distinct lack of resources for actually implementing an authorization server. RFC6749 does not suffice on its own since it says nothing about authentication or tokens pay…
I would love to see a reference server implementation for OAuth 2.0 & OpenID Connect Core 1.0, as it would be quite helpful when I go to add OAuth 2.0 to the libre software suite we use at work!
May be worth checking out https://github.com/ory/hydra and related projects by ory