The core plugin is now compatible with Statamic versions 5 & 6!
Plus a new queue manager utility under tools to help see if anything is a bottleneck for any inbox or outbox sending.
The core plugin is now compatible with Statamic versions 5 & 6!
Plus a new queue manager utility under tools to help see if anything is a bottleneck for any inbox or outbox sending.
Repo's are set up and in the public eye to watch. And sure, everything broke the moment I spun up a fresh Statamic site and tried to install the add-on with composer, but that's learning for you.
Feel free to follow along:
Turns out how I was build this as an add-on was kinda off a bit. So I've spend the last bit refactoring, making things even more modular.
Then of course I broke a bunch, test broke, my confidences was squashed to almost 0. But now I'm back. And boy could this end up being fun.
Now you can install only the add-ons for your needs & flavours.
The core will be required for all
But then, I started building a couple add-ons to extend the core and make sure the fundamentals are working
Then here's some future add-on's I can immediately think of that I want to tackle
How do you want to extend AP?
Server resources maxed, accounts flagged several time 😬🤦, server admins mildly disgruntled as I whimper up and ask... please can I be unsuspended again?
Outcome is, I've refactored a bunch of processes to allow for more granular control. I can now choose how often and how many items to process from the inbox & outbox queue's, choose when to run maintenance and data integrity scripts (which are now separated from ongoing cron job needs), plus view a very loggy log of the processed queue ( UI tweaks coming around that for sure. )
I also implemented a light migration, so that if I make some sort of data changes ( which is very often as I uncover more and more with ActivityPub ), it will only run once, and only once, during a deployment.
Deploy often; break things as I go. That's what personal experiments are all about.
After a bit of learning yesterday and today, we've got some federation happening.
I'll share code after I've had a bit more time to work out some of the kinks.
Happy ActivityPubbing!
I believe in ActivityPub and the fediverse. But sometimes, the platforms built to federate feel to me they are hyper focused on a fraction of the capability, or way to complicated in scope and tech, or crammed on some core foundation with duct tape or crazy glue.
So, welcome to my quirky little experiment. I'll build it in the wee hours when the kids have woken me up and I can't get back to sleep; when the rest of the family is having screen time; When I need a quick mental distraction. So know this... the bar is low, I may fall off.
So the first step was figuring out how to get started. There are loads of options. After some testing, hair pulling, keyboard smashing, regrouping, coding myself, then back to more testing, I chose Statamic to be the core of my little pet project.
Here they are some of the reasons in no particular order:
For now it's simple. A list that looks like the many other ActivityPub project lists.
Groan all you want... puns are fun! What I'm actually interesting in are Intransitive Activities. I don't think we give them much value or exposure today.
Old school web was full of this: Scrobbling music, checking into FourSquare, or even the original Facebook, where everything was prefixed with "Nick is..." Remember when the classic Web 2.0 joke was, "I don't care that you ate a sandwich!"? Yet, we all still shared those simple acts. In our new ways, we still do.
I don't want to "bring it back" so-to-speak. With concerns of big brother watching, public logging like this may be passe, but I still think there's something simple and interesting for me to it: a way to "check-in" and support local businesses and places or a way to "scrobble" songs to support musicians, maybe other ways too.
Long story short, this is a beginning. Stay tuned here, and hopefully soon on the fediverse for updates.