Welcome to the enchanting realm of 3D Printing
Our bot, the guardian of this realm
Just follow and mention me in your post, it's that simple! I will #boost
Ready? Set. Print!
Admin and moderator extraordinaire
Check the replies to this post for rules and special features such as reporting posts.
Please contact @Stark9837 for any reports or inquiries.
Happy printing!
@3dprinting @Stark9837 I'm curious. Have you ever posted under either account about the software and configuration you are using for the bot?
I wrote it myself. The #Github links were posted a week or so ago but is currently set to private as I changed the name from Mastodon-group-bot to #MastoBot as it now has more generic functionality and is also a Python package.
It is written in #Python, #Docker, and also uses #Sqlite, but this is currently being changed to possibly use #Redis, but I am still experimenting.
I'll let you know once the repo is public again, and you can check out the source code.
The source code for this bot's config and the package will be back online in a day or two.
We also use #Jinja2 for the custom messages the bot sends to new followers.
@Stark9837 @3dprinting Thanks! I was asking because I have been thinking about a different kind of group aggregator bot and I was curious what was already written that might accomplish that purpose.
What functionality are you looking for specifically?
@Stark9837 @3dprinting Being an Actor that auto-boosts all posts from a configurable set of other Actors.
I plan to expose every public category on a Discourse I run as an Actor but I'd also like to follow groups of categories easily. I could do that by having various Actors boost a configurable set of Discourse Actors — including one that boosts all of them.
Currently, I am working on it as a package that can be used by other developers or just simply be confugrable with #YAML files.
Also, I am investigating having multiple bots in 1. Thus, only a single instance or #Docker container is required to allow bots to work together. You can create an issue on #Github once the new package is made public, and then we can have a closer look at your desired functionality.
@Stark9837 Cool! I'm still thinking this through but this sounds interesting. Thanks!