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

Reply to https://twitter.com/LauraKalbag/status/1209843483542007808

Out of interest where are you moving to?

Because GitHub is willing to work with ICE https://techcrunch.com/2019/11/13/github-faces-more-resignations-in-light-of-ice-contract/ but at least GitLab are being up front about their politics?

Although yes I agree they're not amazing

 Reply

Reply to https://twitter.com/heydonworks/status/1209769610502905856

All my code hosting is on https://gitlab.com/jamietanna

Static site hosting is on https://netlify.com and VPS hosting is on https://hetzner.cloud

Although some things that I contribute back to are on https://github.com

 Bookmark

Dear Americans: Be Very, Very Afraid Of The EU's New Copyright Rules

Those of us in the EU are pretty worried about it, so I can imagine it's not going to be fun for folks whose countries haven't even had a say in it!

Recommended read: Dear Americans: Be Very, Very Afraid Of The EU's New Copyright Rules https://www.techdirt.com/articles/20191220/16454343611/dear-americans-be-very-very-afraid-eus-new-copyright-rules.shtml

 Bookmark

Working for Microsoft cost me $200 million

An interesting look at why you'd want to work for a startup, not a tech giant - although not everyone will have the same experience.

Recommended read: Working for Microsoft cost me $200 million https://blog.garrytan.com/working-for-microsoft-cost-me-200-dollars-million

 Reply

Reply to https://lobste.rs/s/4qf4tj/future_web_isn_t_web#c_932z7f

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/

 Bookmark

SemVer is an intent - not a promise

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.

Recommended read: SemVer is an intent - not a promise https://damieng.com/blog/2019/12/19/semver-is-an-intent-not-a-promise