Bookmark

https://lukeb.co.uk/2019/05/15/your-event-probably-shouldn-t-be-in-a-pub/

Great post by Luke about how we should be more inclusive in events and whether alcohol-oriented is the nicest message for those wanting to get involved.

Recommended read: https://lukeb.co.uk/2019/05/15/your-event-probably-shouldn-t-be-in-a-pub/ https://lukeb.co.uk/2019/05/15/your-event-probably-shouldn-t-be-in-a-pub/

 Bookmark

Hardening SSH with 2fa

This is a great writeup about how to harden your SSH setup using 2-factor authentication. Would really recommend it!

Recommended read: Hardening SSH with 2fa https://gist.github.com/lizthegrey/9c21673f33186a9cc775464afbdce820

 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.