why am i still up this late working on #rustodon
wrote a little debugging/ops tool for #rustodon, having fun with this
i see a lot of people on here wanting a plugin architecture for mastodon or mastodon-alikes. what do y'all _actually_ want out of that? like, which things do you want to be able to implement and how?
i'm interested because i've been thinking about how to do this in #rustodon, and that's highly dependent on what applications people care about
getting a lot of #rustodon work done recently! turns out that trying to implement new things is a great impetus to fix bad decisions i made in the past
hmmmmm finally removing the extra crate i had for #rustodon's database stuff back when Diesel and Rocket and Serde used to clash
what i have done this year. feat. shoutouts to a lot of awesome #rustodon contributors!
hmmmmm, #rustodon logo idea
i need to write a post about my goals for #rustodon
so i've been pretty silent on the #rustodon dev front for a bit! i'm working pretty hard on some behind-the-scenes stuff, laying the groundwork for sending posts around and stuff.
but, unexpectedly, @y6nH stepped in and completely redesigned the frontend! mad props to him. and it looks way, way, _way_ better than before! i'm extremely fucking excited about how this is shaping up. also, everything you're seeing here is js-less and screenreader accessible, and weighs only ~30kib (with compression and caching disabled!)
testing #rustodon federation stuff against pleroma. they do a few different things than mastodon and that broke our webfinger impl, which was actually really nice because it was a trivial fix for something that would cause 500s
very curious about pulling more IndieWeb stuff into #rustodon
h-hey it's a nodeinfo endpoint! #rustodon
we're getting really fucking close to having working pings in #rustodon!
#rustodon has pretty cute markup imo
i have more lines of test suite for this URL matcher than actual code #rustodon