Tag www.jvt.me

 Reply

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!

 Note

Well, I think I've cracked it - after a few weeks of on-and-off work on making my webmention sending not spam everyone (see https://www.jvt.me/posts/2019/10/30/reader-mail-webmention-spam/ ) - it's now not re-sending them if they're successful. This is a good first step, but I'll be improving it to re-send if the post's data has changed since last time it tried (in the future).

Note that this isn't quite done yet, expect it to be live tomorrow perhaps.

 Note

Woo, thanks to https://realize.be/ for releasing an update of the wonderful Android app https://indigenous.realize.be/ which adds in a fix to not send multiple bearer tokens in Micropub requests ( https://github.com/swentel/indigenous-android/issues/241 )

This started breaking for me when I upgraded my Micropub endpoint to use the spring-oauth2-resource-server module ( https://gitlab.com/jamietanna/www-api/merge_requests/27 ) which is a well-formed OAuth2 server, whereas my previous implementation was not.

Super speedy fix, and glad to be back to using the app again!

 Note

I've just removed categories as a thing from my website. I'm still using tags on all the content, but categories no longer exist. This is for a few reasons:

  • categories are not Microformats2 markup-able (as we can't distinguish between tags and categories, it's just p-category which we use for tags)
  • categories in the site are not currently hierarchical - although they may be defined as such, they're not presented like it
  • categories are not any more meaningful than tags, as they're almost always the same, or a reduced set, compared to the tags

So we may as well just remove support for them, as they serve exactly zero purpose.

 Note

Extending www.jvt.me to allow for other post types

Announcing support for posting notes to my website.

Welcome to my first https://indieweb.org/note ! Notes are short-form content that will be purely plain text (for now!) and are similar to tweets on Twitter or toots on Mastodon, but won't be size limited.

I've been wanting to creating other post types since starting to use https://indieweb.org/Microsub and having a social feed. I've found that I want to interact with other posts, such as like or repost others' content, much as I would do with Twitter.

Discoverability of notes currently aren't super amazing, but I'm tackling it as part of https://gitlab.com/jamietanna/jvt.me/issues/457 because adding these post types was a large enough piece of work.

With this note, I'll now be able to https://indieweb.org/bookmark , https://indieweb.org/like , https://indieweb.org/reply , https://indieweb.org/repost , and https://indieweb.org/rsvp .

RSVPs are an interesting one, because the end goal I want is for my RSVPs to be syndicated from this site to i.e. Meetup.com.

I'm hoping to work on bringing https://indieweb.org/Micropub support to this site, too, but as it's a static site with https://gohugo.io and hosted on https://gitlab.com with a full build/test/deploy pipeline, it'll be a little less straightforward, and slower, than other solutions.

I've designed the content schema to be Micropub-first, as I want to be writing these posts using a Micropub client, rather than my usual workflow. I've made the source files JSON files (which Hugo natively supports) which makes them easily machine writeable - hopefully it'll teach me to prioritise my Micropub support so I don't have to manually write JSON!

In terms of licensing, I'm going to start by them in line with my posts, as http://creativecommons.org/licenses/by-nc-sa/4.0/legalcode , but down the line I may look at other licenses.