Authenticate your website and Twitter account with Bridgy and enable Bridgy publish on your account page:
https://brid.gy/twitter/username.
Tag: authorization
One of the themes that crops up again and again in the IndieWeb community is that your personal domain, with its attendant website, should form the nexus of your online existence. Of course, people can and do maintain separate profiles on a variety of social media platforms, but these should be subordinate to the identity represented by your personal website, which remains everyone's one-stop-shop for all things you and the central hub out of which your other identities radiate.
Part of what this means in practice is that your domain should function as a kind of universal online passport, allowing you to sign in to various services and applications simply by entering your personal URL.
A nice little primer on authorization and authentication.
👓 OAuth for the Open Web | Aaron Parecki
Aaron Parecki (Aaron Parecki)OAuth has become the de facto standard for authorization and authentication on the web. Nearly every company with an API used by third party developers has implemented OAuth to enable people to build apps on top of it. While OAuth is a great framework for this, the way it has ended up being used is ...
An Indieweb Podcast: Episode 7 The Reverse Salmention
Running time: 1h 35m 20s | Download (28.7 MB) | Subscribe by RSS
In this last episode before David Shanske and I head to the Indieweb Summit in Portland, Oregon, we discuss updates to people’s Indieweb experience, little things David has hidden in plugins, web-signin vs IndieAuth, etc.
We’re both looking forward to seeing those of you who can join us in Portland.
Huffduff this EpisodeToday I updated the IndieAuth plugin for WordPress, and I can now use my own website as an IndieAuth authorization endpoint (including provisioning and revoking tokens) for a multitude of things including a huge number of micropub clients.
Special thanks to David Shanske and Aaron Parecki for all their work in getting this to happen!
It never occurred to me that people would be blaming @oauth_2 for the Facebook mess. Friendly reminder that OAuth is what lets you control *which* parts of your Facebook data apps get access to, and what lets you revoke that access, which you can do here: https://www.facebook.com/settings?tab=applications