update on #fossil: last night i pushed changes to make algorithms pluggable. it uses #python entry points for discovery, so you can develop your own plugin without cloning fossil. it gives you a few hooks:
train: e.g. if you need to train an ML model, or just calculate aggregate statistics
render: format toots into an object that’s passed to a jinja template. you can make the jinja template or just use one that already exists
i made the existing TopicCluster algorithm into a plugin that happens to be shipped by default, so that should provide a guide. i also want to write more documentation, but it takes time. #fossil
i’m noticing that using #htmx is leading to a surprisingly pluggable design. tbh i haven’t wrapped my head around why, it still seems counterintuitive that true APIs would be harder to compose than HTML endpoints. maybe it’s just the dramatic simplicity is inherently easier to grapple with, idk #fossil
@mnl btw i didn't forget about this. i wrote a blog post, but the AI overlords inform me that i didn't actually describe the plugin system, which is a valid criticism regardless if it's real intelligence. Also, the code didn't exist (it was just a design in my head), so i'm also producing that too. you see, tooting is such a malleable medium :)
fwiw the code and post are almost there, just need to brush both up
@kellogh I ... Know exactly where you're at :) being able to so quickly get stuff implemented means your mind gets so much further ahead of itself "it's just a generation away". But still generating something takes an hour or two and not just the 2 minutes one thinks it does 😭
the contributor base is growing. still not many pull requests, but it’s ramping up.
i got this comment on a public issue, and i feel like i could’ve posted the same thing at several points in my career. i’m so glad that i can help people find meaning in life & work
@kellogh I’m going to guess that #htmx is more pluggable than you’d expect because the API is so simple. REST is amazingly straightforward (real REST, anyway) and I think this carries over.
There’s no dependencies between components or worrying if a JS widget has already been loaded or not — just little self-contained bits of code that go right here on the page.
Add comment