IndieWeb post types

This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:

 Bookmark

This is a great article on why we can't just let Google Chrome / Chromium take over the Web, and need to fight for other alternatives.

But as well as looking at the browsers, we need to look to the platforms too. If everyone ie uses Twitter, then Twitter are less likely to make changes because no one has an alternative. Whereas when we have multiple viable options, folks can jump around and use better platforms if they exist.

The IndieWeb is looking to do this - check out https://indieweb.org/why for a bit more info

 Note

Day trip to London tomorrow, so 4+ hours on the train - hoping to finish my writeup of DevOpsDays London as it was a great conference and I'd love to share it with y'all!

 Note

So very close to having my IWC Amsterdam blog post finished before WIT Notts - may have to see if I can get the last bit sorted before the talks start!

 Bookmark

This is an interesting post, and is an important one to think about. We need to remember that although now we've got lax data privacy / retention laws, it's only going to get more user-focused and protect everyone more (which is universally a good thing!) but that we need to make sure we're architecting things in the right way to handle this.

Also, while you're thinking about this - have a read through some production logs and wonder "what could a bad actor do with these? Could they phish a customer? Could they steal their identity? Or are these so useless that we may as well not be logging anything at all?"

 Reply

Regarding our conversation yesterday for OAuth and API aggregation, I mentioned that while working on PSD2/Open Banking we've been doing similar, for instance with a third party who would register on behalf of a fourth party.

I've tracked down https://bitbucket.org/openid/obuk/src/6b4300bdc872dd55573f3ce9c65b66ada640efaf/uk-openbanking-registration-profile.md as the definition for the way this works with the use of new fields in the Signed Software Assertions (for use with https://openbanking.atlassian.net/wiki/spaces/DZ/pages/1078034771/Dynamic+Client+Registration+-+v3.1).

It may be worth reaching out to OpenID/Open Banking to see if they've got this officially specified about this, or whether this is the latest source of truth you can use

Hope this helps with your hope to standardise this into an OAuth spec!