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/

Very interesting to see that there's even more to the command than expected - and some great new features coming soon.

Some interesting points in here that reinforce my thoughts about the difficulties of knowing what the right version number should be - although I hugely push for and use SemVer.

Have you by any chance heard of the #IndieWeb movement? We've got a great group of folks who are looking at what it means to #OwnYourData and #BeYourOwnSocialNetwork

I've written about it https://www.jvt.me/posts/2019/10/20/indieweb-talk/ and we've got a large wiki too https://indieweb.org/why

Thanks for sharing - I've been wondering about getting it since getting a Switch and may reconsider

Arthur Christmas is such a great Christmas movie - we discovered it maybe four years ago, but it's part of our yearly routine now!

An interesting approach - but I wonder why you'd implement like so (requiring SSH usage) instead of the Systems Manager's run-command https://docs.aws.amazon.com/systems-manager/latest/userguide/walkthrough-cli.html ?

A safer way to parse YAML by removing some of the more dangerous parts of YAML parsing - an interesting approach that means you don't need everyone well-versed in the minutiae of the YAML spec!

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.

A good read by Terence about how the Semantic Web and using metadata (be it Schema.org, microdata or Microformats) will build a more usable and interconnected life

I like that idea - automagically parsing the data from a URL is reasonable, and is mostly automatic but a little manual so there's the ability to correct issues (as mentioned in https://aaronparecki.com/2019/12/21/12/ )

Would we also be interested in iCal feed parsing, or just stick with MF2 for now?

This is really amazing - great work on this!

Out of interest, would there be any interest in the ability to syndicate events from our own websites to https://events.indieweb.org so there's a bit less manual process for adding them to the official list?

Aw thank you! It's my last day in Notts today tho so unfortunately won't be able to make it. Hope its good though - did you go see it with work on Thurs or is today your first one?

A subtle and not so fun source of bugs if you're affected - worth investigating!

Also looks like this post doesn't have a valid in-reply-to url!

Could be that your reply is an h-cite maybe? So parsing it isn't happy? Odd as there's definitely a url in the body that references my post so it should be ok

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!