Tag www.jvt.me

 Note

Welp it turns out that the slow builds on my site (> 25 minutes, mostly due to the size of it) that have been causing GitLab to time out can be resolved by upgrading the size of CI runner that was launched several months ago!

 Reply

I've also implemented this in my Micropub server:

  • when creating a post, and the draft scope is present, the post-status is forced to draft (even if it's set otherwise in the post)
  • when updating a post, and the draft scope is present, the update is only allowed when updating a draft post, otherwise returns insufficient_scope
  • delete/undelete returns insufficient_scope when the draft scope is present

 Note

It feels odd to suddenly have i.e. replies to tweets be sent ~90 seconds after I post the comment, instead of ~8 minutes later. Turns out that some tweaking of #Netlify settings, reducing some of the size of files on my site, and migrating from Netlify to #Cloudfront with a self-hosted shell #gitlab CI runner makes a big difference!

 Note

Managed to track down what the ~5 minutes of post processing was on my #Netlify site (thanks to the wonderful support from https://community.netlify.com/t/slow-deploy-times/30857/4) - now I wonder how else I can trim the deploy speed to something more reasonable

 Note

Folks who follow my blog's #Microformats feed will now see the context (as an h-cite) that is visible on my site, allowing you to have some context for at least interactions with Twitter, but hopefully other stuff in the future!

 Note

Woo! Got #Micropub edit functionality working 🙌 https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b is my first update through the API. Next will be getting my syndication links auto updated once syndication is reported as successful, but not one to do tonight

 Note

So I sorted my Webmention sending issue after an incredibly frustrating day of fighting with Jackson parsing my XML sitemap. I'm still not sure what the issue was, as I've ended up replacing my POJO with another one, but 🤷🏽‍♂️ at least Webmentions are sending again

 Note

Woops, looks like I broke my Webmention sending yesterday when I upgraded all my versions of Spring / Spring Boot. That'd explain why things haven't syndicated to Twitter today. Film time now, so will fix tomorrow!

 Note

I interact a lot with Twitter from my website, and as such the interactions you see are i.e. "Like of @indiewebcamp's tweet" which isn't super helpful. So I've just added the ability to mark up my interactions with some context of what the post was so it's eaiser to see without navigating there.

This is using the awesome https://granary.io/ and will hopefully make reading Twitter interactions through my site much nicer!

You can see https://www.jvt.me/mf2/2020/02/ihnc5/ for an example of what it'll look like (including photos!), and https://indieweb.org/reply-context for more info from around the #indieweb

 Note

Very much looking forward to tonight's #TechNott, not least because it'll be the first meetup I'm owning every interaction first from my website in #IndieWeb fashion, as well as converting hashtags to tags on the posts themselves!

 Reply

I mean, I said that an hour or so ago, but that was before the site had deployed... Turns out https://www.jvt.me/posts/2019/11/11/gotcha-netlify-lowercase/ caught me out again and isn't fixed until https://gitlab.com/jamietanna/jvt.me/merge_requests/638 is in (although I've done a temporary deploy from my local machine to get the site up).

Very annoying!

 Note

My site is now running Hugo v0.62! Not too painful an upgrade from 0.58.3, given changes in the Markdown parser - https://gitlab.com/jamietanna/jvt.me/merge_requests/637 - largely Table of Contents related, and one place where I'd not got enough spacing in around fenced codeblocks

 Note

This post has been published by my Micropub endpoint (code in https://gitlab.com/jamietanna/www-api ) and syndicated to Twitter via https://brid.gy 🙌 #IndieWeb - I'm able to own my tweets from my personal website at https://www.jvt.me and you can too by joining the folks at https://indieweb.org/discuss

 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.