RT @AndyVesey_AGL .@TonyAbbottMHR We're getting out of coal. We committed to the closure of the Liddell power station in 2022, the end of its operating life.
Facebook now shows that I used Bridgy to create this post:
Clicking the word Bridgy above takes me to this page:
I can keep clicking links in this iframe, for instance there's a link to indieweb.org, so:
.... looks like the indieweb has been consumed by facebook.
I tried clicking through to my own site, but I have a header set to X-Frame-Options: DENY, so I get a blank iframe. Probably not a bad idea to set it if you want to avoid this sort of thing.
I mentioned at the end of my last post that I wanted to add a new link header to my home page to make web actions easier. I've done that now, and so have a webaction endpoint that can be discovered (along with all the others).
Since web actions can now be discovered from my home page, I can use my Universal Sign-In Button to find the config for me:
When it finds the config, it automatically applies it to the page the same way indie-config works after receiving a message from a hidden iframe. The dialog shown above then closes automatically.
This solves the problem of "over sharing" my config via the browser's protocol handler, and still allows me to share the information with other sites as simply as possible, which is with one click. Another advantage of this method is that I don't have to "prep" the browser by logging into my site and activating the protocol handler. It is also easier to see what my web action page is set to when I am logged in as it's now just a field in my profile information.
The Universal Sign-In Button is a customisable bookmarklet that will auto-fill a sign-in form on the page you are currently visiting and submit it for you. It's a one-click way to tell the current page who you are.
Ok, so why do I want to tell the page I'm visiting who I am?
One of the advantages the big data silos have over the IndieWeb is that everyone has an account on them. That means small sites can create sharing links that link back to Facebook, Twitter, (or maybe even Google+) and the visitor will be able to interact with the link in a meaningful way. A site could even embed a comment form provided by one of these sites, knowing their visitors will most likely be logged in. This creates a social layer between small sites and the big silos that reinforces their position as the place where it's easiest to share links and comment on what you read.
On the IndieWeb, there is no comparable singular point of focus. That makes it just a little bit harder to re-create that social layer. Indie-config is a really nice way to solve this problem, it registers a protocol handler in the browser that contains your custom url. Unfortunately this technique suffers from a privacy problem. The process that allows you to automatically tell a site who you are can be implemented by anyone. That means you really need to check who is requesting your config from your site, and give them permission before you visit their site.
The way to fix that is for browsers themselves to implement indie-config, and to require your permission before giving your details to a new site. Since that's not going to happen any time soon, we need another way to easily tell a website who we are, without giving this information automatically to every site we visit.
I've written a bookmarklet that can do just that. A bookmarklet is a standalone piece of javascript that can be saved as a bookmark, and when opened will run on the current page. I've called it the Universal Sign-In Button because it lets anyone sign into any website with one click. The nice thing about this solution is that some browsers (ie Firefox) will let you customise the location of the bookmarklet, so I can have my Sign-In button right next to the address bar:
You can use this button to sign in to any site that supports IndieAuth. I've used it to sign in to the IndieWeb wiki, Quill and my own site. It doesn't have to just be used with IndieAuth however. I mentioned indie-config above, well instead of using the browser's protocol handler to find my config, I can create a second bookmarklet containing the url that returns the config.
To make this button more 'universal' however, my next project will be to add a new rel value, rel="webaction", to my home page. That way, if a form supports webaction discovery, only one button will be required.
facebook iframing
Clicking the word Bridgy above takes me to this page:
I can keep clicking links in this iframe, for instance there's a link to indieweb.org, so:
.... looks like the indieweb has been consumed by facebook.
I tried clicking through to my own site, but I have a header set to X-Frame-Options: DENY, so I get a blank iframe. Probably not a bad idea to set it if you want to avoid this sort of thing.
Indie-config using the Universal Sign-In Button
Since web actions can now be discovered from my home page, I can use my Universal Sign-In Button to find the config for me:
When it finds the config, it automatically applies it to the page the same way indie-config works after receiving a message from a hidden iframe. The dialog shown above then closes automatically.
This solves the problem of "over sharing" my config via the browser's protocol handler, and still allows me to share the information with other sites as simply as possible, which is with one click. Another advantage of this method is that I don't have to "prep" the browser by logging into my site and activating the protocol handler. It is also easier to see what my web action page is set to when I am logged in as it's now just a field in my profile information.
Universal Sign-In Button
The rest of this post explains why such a button is necessary. If you would like to create your own button, you can head straight over to this page.
Ok, so why do I want to tell the page I'm visiting who I am?
One of the advantages the big data silos have over the IndieWeb is that everyone has an account on them. That means small sites can create sharing links that link back to Facebook, Twitter, (or maybe even Google+) and the visitor will be able to interact with the link in a meaningful way. A site could even embed a comment form provided by one of these sites, knowing their visitors will most likely be logged in. This creates a social layer between small sites and the big silos that reinforces their position as the place where it's easiest to share links and comment on what you read.
On the IndieWeb, there is no comparable singular point of focus. That makes it just a little bit harder to re-create that social layer. Indie-config is a really nice way to solve this problem, it registers a protocol handler in the browser that contains your custom url. Unfortunately this technique suffers from a privacy problem. The process that allows you to automatically tell a site who you are can be implemented by anyone. That means you really need to check who is requesting your config from your site, and give them permission before you visit their site.
The way to fix that is for browsers themselves to implement indie-config, and to require your permission before giving your details to a new site. Since that's not going to happen any time soon, we need another way to easily tell a website who we are, without giving this information automatically to every site we visit.
I've written a bookmarklet that can do just that. A bookmarklet is a standalone piece of javascript that can be saved as a bookmark, and when opened will run on the current page. I've called it the Universal Sign-In Button because it lets anyone sign into any website with one click. The nice thing about this solution is that some browsers (ie Firefox) will let you customise the location of the bookmarklet, so I can have my Sign-In button right next to the address bar:
You can use this button to sign in to any site that supports IndieAuth. I've used it to sign in to the IndieWeb wiki, Quill and my own site. It doesn't have to just be used with IndieAuth however. I mentioned indie-config above, well instead of using the browser's protocol handler to find my config, I can create a second bookmarklet containing the url that returns the config.
To make this button more 'universal' however, my next project will be to add a new rel value, rel="webaction", to my home page. That way, if a form supports webaction discovery, only one button will be required.
If you would like to create your own button, please visit this page.