The hope of Sele is to make it "easy" to deploy. This version is focused on the "community" edition that'll be hosted for general use. I'm already looking to what parts can be shaved down for its underlying libraries that separate attestation and the general IndieAuth endpoints (so any Axum-powered Rust project can drop in IndieAuth support with WebAuthn support by only providing a means of data persistence). This is important for the rewrite of this site (Shock, namely, this is stored into something else) because I'd want to bake in the IndieAuth provider logic from a battle tested implementation.

I'm not sure how to get this into more hands outside of solving some usecases for it. The most immediate would be looking to coax folks using webmention.io to opt for this service but that could be a lot. I think, instead, I'll keep it quietly humming along and then flip my personal site to use it. And once that's cool for about a few days, I'll start working on Lighthouse to flesh out the social reader system. My site's truly going to be the last thing rebuilt, ha.

I'm making some huge changes in my site in prep of using it for more of my comms and devs, a bit similar to how https://simonwillison.net/ does it. Right now, I'm going to experiment with implementing local sign-in to my site. It'll probably be incomplete as Sele doesn't support RelMeAuth and I'm very torn on implementing it as an explicit feature (more on that later).

For now, if I can get it to show that I'm signed in, that'll be a great first step. I've added logic to https://indieweb.org/Shock to allow for the redemption of a token for it to use for fetching Micropub information, as well as granting me access to the dashboard. This is exciting as I can also use this to require authorization for posts and feeds soon, and even considering allowing an on-site form for replying if you sign in. All things to consider.

Made lots of changes to my site's parts this evening. Most of it is to lean more on protocols to get me what I need. Eventually, this site would essentially become a feed renderer of the content I store in my Micropub server (and other places). Very exciting.

byhttps://jacky.wtf • posted archived copycurrent

Definitely need to figure out this bug that's happening when I try to hit some parts of the p3k suite of tools. That's no good. But also subtle incentive for me to work on my own implementations!

A next step is to have my theme 'auto-deploy' to my site. I think I'll have to write a custom script for this and have a token that has the ability to push it for now. Adding that functionality to Shock directly would require a bit too much work right now.

Might need another channel called "pages" so I don't have things just float up there whenever I make a standalone page on my site.

I updated both Shock and Koype so now categories can be paginated, which makes them into feeds! Now to actually generate feeds (like RSS and the like) instead of using Granary