Reply

Would that be needed? Generally with OAuth2 a 401 would indicate there is some issue with the token and to either refresh a refresh token (if one was issued) or to request the user re-authorise the application.

Unless we're recommending the use of a refresh token, I'm not sure if we'd need clients to keep an eye on the expires_in from the initial issue, or calls to introspect on the token endpoint

 Reply

We've done that too (but don't have kids) so Anna Dodson and I each have profiles and then there's a shared one which doesn't skew our history. But the family mix includes music from all and is quite nice!

 Like

Liked a post on Twitter
Post details

 Reply

Hey! Do you mean instead of having my base image downloading each of the gems and the Netlify CLI? Yes I did, but I was a bit lazy so didn't get round to it. I've since moved to Netlify's build https://www.jvt.me/posts/2020/05/27/migrate-netlify-deploy-gitlab/, although I'm wondering about going back to GitLab again to cut costs, and hopefully speed it up a little

 Reply

A fair few of us using static sites use https://webmention.io as our webmention server, and then you have the choice of how you want to display them. I used to do it on site builds, but moved to dynamically doing it with client-side JavaScript for a more up-to-date feel as mentioned in https://www.jvt.me/posts/2019/06/30/client-side-webmentions/