My Micropub endpoint has a fair bit of unit testing inside the Java project ( https://gitlab.com/jamietanna/www-api/tree/develop/www-api-web/micropub ) for common flows, but I've also found a tonne of implementation issues by integrating with real Micropub clients.

Some of it is an issue on a Micropub client, but most of it is something I've missed or assumed incorrectly.

I'm thinking to create a stubbed version ( https://gitlab.com/jamietanna/www-api/issues/26 ) that I can then use with https://micropub.rocks to ensure compliance.

Some of it is also a case of reading through the Micropub spec!

Definitely yes to this! I've also proposed how we can do this using Microformats2 in https://www.jvt.me/posts/2019/04/10/pronouns-microformats/

This is my go-to for tidying up disk space issues when working with Docker

Ah nice! Thanks I'll have a play with it at some point then. Although I'm not sure I've got the time currently to write a spec compliant IndieAuth server too 😥

Interesting. I guess my main thought was whether it was something you could get Okta to only require MFA via Verify, or if you needed to do some hacking around it to make the flow work so you can just log in via Verify?

This is a really nice recap of https://dddeastmidlands.com and gives you a nice feel of the day!

I'm quite up for coming to IndieWeb Summit, but I'd need it to either map to some work while I'm out there, or some holiday, as it's a long way to come. But would be very cool!

Did you ever write up how this works / could work? If so, I can't seem to see the post by searching passwordless

An interesting read, but I would personally say to stick to the language-specific process. Ie Rakefiles for Ruby, a task in your build.gradle or npm run deps as it'll handle things nicer in a language / stack you're more familiar in, although I totally see why you'd want a language-agnostic interace

There may still be some dupes for now, looks like my async work has meant there are clashes with trying to write to the DB https://gitlab.com/jamietanna/www-api/issues/75

Looks like I've done it now - https://gitlab.com/jamietanna/www-api/issues/74 is the root cause, which I'll fix this evening properly.

For now, I've put a hacky hotfix in to get it working

But this unfortunately has not worked - I'll have a look at debugging this in the morning!