I’m happy to have Shinobu hosted at ani.social! I’ll do my best to maintain that uptime for the sake of the bot!

In retrospect I realize that maybe I should have gone and cleared this with you first. Thank you so much for being accommodating and giving your blessing nonetheless!

I too am a 🤮 Bakemonogatari 🤮 fan

… This may or may not have factored into the decision

I fear no loli, but that thing… it scares me.

What a terrible day to slay demons…

Roboragi’s kind of a doozy. It hooks itself up to the firehose and just runs forever consuming every single comment it can. I have to imagine that the hosting costs for Roboragi would be kind of high, not to mention the inherent unfairness of hammering one instance’s API to serve the whole Fediverse.

That’s not to say that Roboragi’s unsalvageable, per se… it’s just going to be a lot more invasive compared to the process of porting a passive bot like Holo. At the very least, we’d have to rip out the firehose stuff in favor of something like the mention-based system that bots like /u/RemindMe use.

Hi, thanks for reporting this issue! I was able to verify that shinobu’s posts aren’t populating on kbin, which is certainly not an ideal situation. After doing a little research, it appears that kbin.social currently completely refuses to federate content from any bot (see kbin-core#350 @ CodeBerg).

I couldn’t seem to find any official comment on this behavior, so I can’t comment on if this is by design or simply some oversight. I tried searching the kbin codebase for hints as to what might be going on, but nothing at all comes up in relation to the federated bot_account flag. I’m truly stumped 🤷

It is technically possible to bypass this through incorrectly marking shinobu as a human, but I won’t agree to do that as it sabotages the experience of users who specifically choose not to see bot content. At this point, I’m afraid that the only remaining course of action is for you to follow up on the aforementioned CodeBerg issue with your report and wait for an update from earnest.

I feel like you are still fracturing discussion by posting to both lemmy.ml and ani.social. Can you not crosspost in lemmy (ie make the lemmy.ml posts take you to ani.social)? So everyone is funneled to the same spot.

I, too, put a high value on helping discussions succeed and strongly want to avoid smothering discussion threads at such an early stage in this community’s growth. You should know that the possibility of using crossposts as you’ve suggested was explored, but unfortunately needed to be shelved.

You see, crossposts don’t actually share comment sections; users that click on the link will see the original’s comment section and users that click on the discussion button will see the crosspost’s comment section. I decided that this approach would cause confusion and only further worsen the problem and so gave up on it. What we’d need to make your crossposting suggestion work would be a special type of crosspost that has a shared comment section – this is something I’ve been actively advocating for to the developers as you can see here. If they ever agree to accept a PR, I plan to implement the code for it myself.

As for my little discussion community on ani.social: it primarily exists as a place to responsibly test and develop the bot without negatively impacting anyone else’s userbase. Yes, I’m also positioning it as a place where others can visit and discuss, but this is just my own personal hedge against the possibility of [email protected] becoming unviable for whichever reason. You’ll note that the subscriber count of my community is quite low and that I personally follow a strict policy of never actively mentioning/promoting it. If the situation changes so that the continued presence of my community substantially harms or otherwise steals growth from other Lemmy anime communities, you have my promise that I will shut it down – and no: simply existing as an alternative does not count as substantial in my book.