Released version 0.7.1 of my micropub-express module and 0.4.4 of my micropub-to-github project. Major change: Now supports the "create" scope, so more Micropub clients should be supported by default. Also: Of course posting this using the new version.
Trying out https://micropublish.net/ – another online Micropub client besides the Quill one. Great to be able to pick between different ones and this one feels to be especially great for those who constructs their own Micropub endpoints as it very clearly shows what it is going to be posting to the Micropub endpoint.
Just launched a ServiceWorker here on my site, added a manifest.json that for now goes all in on setting it up for a PWA (it shouldn't really configure itself to launch as a standalone app, but I want to test the standalone mode out so for now it will) and modified the published time on all of these posts to by default be set as 15 seconds old and thus never be treated as a future post when the build server is triggered by a Micropub post – something both GitHub pages and Netlify has had a problem with.
There is a problem in journalism that we favour lots of diversities over economic diversity … We don’t have enough folks who grew up in working-class rural communities.
This is probably true for many places that want to be actively working towards gathering a more diverse crowd. When measuring the diversity one picks a few dimensions, but forgets that there are many others as well. The diverse crowd one then gathers might only be diverse in some very specific ways, but far from diverse in other ones. The diverse city crowd is eg. still a city crowd and might differ from the diverse non-city crowd.
Yarn certainly helps with some parts of this. Eg. parts of "installed-check" can be replaced with "yarn check", but the engine checks, "dependency-check" and "husky" certainly still provide value when using Yarn.
The ecosystem is to a large degree still the same, no matter if one uses the Yarn client or the npm client.