1,882 karma · joined August 3, 2015
Also, look for indicators of active moderation and participation in the Mastodon Server Covenant if you want to avoid toxicity.
Some popular instances have been highlighted here.
Finally, dont be afraid to use a throwaway email and hide behind vpn to create a temporary account on a server or two, just to check it out.
Be kind to the server owners by deleting your temporary accounts, though.
Apple has gotten three states on-board with digital driver’s licenses in the Apple Wallet.
Login.gov supports a variety of identity providers and OAuth.
That was probably one of the advantages of shoe-horning authentication (OpenID) with the existing authorization standard (OAuth).
> Why is everyone linking this draft? It's got very little to do with what we're discussing.
> … Github ALSO uses OAuth2 to delegate permissions to the user's stuff on their own site
> … But even that should only have access to the user’s own repositories.
Seems like Rich Authorization Requests are exactly what we are discussing.
Give it a skim (or a read).
See the latest draft for OAuth Rich Authorization Requests (“work in progress”): https://www.ietf.org/archive/id/draft-ietf-oauth-rar-18.html
edit: you might be mixing up / conflating Open Authorization (an authorization standard - authorization scopes are in scope) with Open Identity (an authentication standard - authorization scopes are out of scope)
edit 2: It probably doesn’t help disambiguate which auth is which when the same company is providing both the authentication service and the authorization service.
Nothing but agreement there.
Can you identify a specific recommendation by the IETF or W3C that was ignored, in this case?
> And saying "caveat emptor" will be about as effective at preventing that as saying "wingardium leviosa".
I had to look up that apparent reference to Harry Potter, but I disagree.
Educating your users about phishing risks, aka “caveat emptor” in this context, is explicitly a best practice for mitigating these kinds of security risks on the open web.
Caveat emptor is not a threat model, it is a risk mitigation.
It is arguably the only mitigation directly in the hands of the consumer.
And that the modern phrase is from a 2000+ year old “dead language” should certainly speak to the longevity, utility, and effectiveness of that mitigation.
> it would be great for me as a dev if I could just disavow responsibility for cross site scripting attacks and other attempts to misuse the user's credentials
thankfully there are standards and RFC’s that indicate best practices that recommend that these security risks be considered and mitigated
edit: see Rich Authorization Requests <https://www.ietf.org/archive/id/draft-ietf-oauth-rar-18.html> for the “work in progress”
Your GitHub user account was compromised by a bad actor, so it shouldn’t be surprising nor considered victim blaming.
Of course, GitHub might cross the line to being unreasonable if they become aware of this as a potential security issue and fail to mitigate the phishing risks that they are exposing their customers to.
edit: restoring your user account to good standing, if absolutely necessary, is certainly something to strive for, but be aware that it can take years or never, from anecdotes that I’ve heard about Google, Apple, Twitter, etc. Microsoft/GitHub/LinkedIn won’t likely be any different, in that regard
I automatically decline the moment I see any app trying to authorize with that scope.
Nonetheless, perhaps this is pointing to Microsoft’s Window’s UAC moment for GitHub.
Bright yellow or red UX with warnings that if you click “agree” then you might as well have given away your computer to a malicious actor.
No one should be surprised that allowing an untrusted program to write files and permissions through an operating system could lead to a security exploit.
Many would likely be cognizant of the risk of becoming a member of a botnet.
Allowing untrusted programs to control your digital services is not fundamentally different, in my current perspective.
GitHub isn’t doing the handing out, it is the user doing the handing out.
I don’t blame the user, as a rule, but in this type of scenario, the user (a consumer of development tools) shouldn’t be excused, in my opinion.
This would be like a doctor complaining for getting sued for malpractice by a patient of a nurse under the doctor, while the doctor neglected to review the patient chart and neglected to take the time to speak with the nurse.
caveat emptor
All that said, I would hope that bad actors that get caught, effectively phishing for GitHub credentials, using a technique like this end up being banned from GitHub.
One neuron might seem insignificantly miniscule, but just one neuron may encapsulate you recognizing a specific face of someone important to you.
[1] https://bionumbers.hms.harvard.edu/bionumber.aspx?id=106322
[1] https://en.m.wikipedia.org/wiki/Prices_of_chemical_elements
I agree that human accountability is something not likely to ever disappear.
“Whether or not it is ethical to use an AI to assist with your communications depends on several factors, including the specific context in which you are using the AI and the potential consequences of using it. In general, it is important to be transparent about the fact that you are using an AI to assist with your communications, and to make sure that the AI is not being used to deceive or harm others. It is also important to consider the potential impact on the people you are communicating with, and to ensure that the AI is not being used in a way that infringes on their rights or autonomy. Ultimately, the ethics of using an AI to assist with your communications will depend on the specific circumstances and how you use the technology.”
Also, why not go further and include a disclosure label for human-generated content?
But further yet, why only disclose that content is AI generated, but not also disclose the manner in which the content was generated and what human-in-the-loop verification and validation took place before posting?
Unless we are talking about an AI-agent posting to social media, in which case, the disclosure could be implicit in all posts made by the AI-agent.
Disclaimer: This was written by a human. All claims made above should be presumed to be falsehoods, unless otherwise indicated.