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:

 Reply

I work on Open Banking APIs for a UK credit card provider.

A large reason I see that the data isn't made directly available to the customer is because if the customer were to accidentally leak / lose their own data, the provider (HSBC, Barclays etc) would be liable, not you. That means lots of hefty fines.

You'd also likely be touching some PCI data, so you'd need to be cleared / set up to handle that safely (or having some way to filter it before you received it).

Also, it requires a fair bit of extra setup and the use of certificate-based authentication (MTLS + signing request objects) means that as it currently sits you'd be need one of those, which aren't cheap as they're all EV certs.

Its a shame, because the customer should get their data. But you may be able to work with intermediaries that may provide an interface for that data, who can do the hard work for you, ie https://www.openwrks.com/

 Note

Since setting up the ability to syndicate posts from my website to other sites automagically the other day, I've been manually ticking the boxes in my posting UI, which isn't the best experience.

So I've now got it to automagically syndicate to Twitter any notes (like this one) or interactions such as likes/replies/reposts on Twitter, so folks still on Twitter are able to see the content I'm publishing to my site, too.

 Note

No spoilers:

Just seen Star Wars Episode 9 and damn JJ did it - what a great ending to the series. Expect more when the spoiler embargo lifts.

I'd seen some tweets similar to this and was a bit apprehensive but it was so good. Wanna go see it again!