Koype's At 0.0.5!

At the time of writing; Koype is currently at version 0.0.5. This release allows it to do quite a bit. It supports most of Micropub (only fetching a list of existing posts is needed), externalizes endpoints on requests (handy since there's no Microsub server in Koype) and has a pretty lax method for obtaining the representative h-card (person info) of a page. All of this makes it easier to not only post onto the Web but retrieve interactions from it. There's a bunch of things I'd like to hack on for it but I have to consider some other projects I want to work on.

Lighthouse

Aaron provides a hosted Webmention service so one wouldn't have to handle said processing in their own sites. Something like this is super handy if your site's statically generated like mine over at https://jacky.wtf or if you want to isolate what your site does from other places. However, there's some stuff that I'd want in a hosted Webmention server and with Lighthouse, I'll aim to produce them! The biggest one is analytics about the kind of Webmentions my site's received - it's a cleaner way to do tracking on one's site with consent!

Fortress

This project is meant to help me push deeper into the world of authentication and authorization with IndieAuth. My ideal world is to get a light notification on authorized devices about requests to my site and accept them from there. Despite it being the IndieWeb, there's some things that are seamless about tapping a notification on my device and keeping it moving. I can see it being used for a lot of different things. It'll be an excellent playground of sorts to see what we can do with IndieAuth (most of which is already done with the boundary pushing of OAuth2).

Version 1.0.0?

I'm personally looking for 1.0.0. to be released when I manage to port my personal site over to it. The idea of doing a manual backfill of over 100 blog posts is a bit arduous to me. And it's something I can imagine other people would want to do as well. This is one of those "what to do" scenarios because I can either:

  • Import each post by hand: This'll take the most time and is super prone to input errors.
  • Build a Jekyll to Micropub import tool: This'll take each of my Jekyll entries, render the core of it as HTML and send them to my endpoint.
  • Build a JSON-Feed to Micropub import tool: This feels like the most likely route since I prefer to work with JSON over things like XML (that'll date me!).

We'll see where this route ends up going. So far, I'm really enjoying what I have!

Permalink • Published about then updated by Jacky Alciné.

Syndicated To IndieWeb News Twitter Bridgy Publish to GitHub