@miaq@flipboard.social @jerry@infosec.exchange for sure, just look at the number of instances spanning multiple software!

@steve@social.technoetic.com is vibe coding ActivityPub in C++ and this is making me feel unsettled When will Claude join the Forum and Threaded Discussions Task force? Eagerly awaiting...

@bentigorlich@gehirneimer.de okay Apologies for not mentioning you up top. I did not know you were the maintainer for mbin, but now I do!

@liaizon@social.wake.st fosstodon seems to be down at the moment, but I don't believe Flarum has started their ActivityPub work, or if they have, it is not at a level for demo yet. I can't say whether the NLNet project was ever completed.

@silverpill@mitra.social it sounds like @fedify@hollo.social was generating one activity for each recipient, which if combined with relatively heavy database calls, would scale quite poorly, even when processed asynchronously. Batching those db calls is always a low hanging fruit in terms of code optimization.

@julian@fietkau.social sunk cost fallacy is a very real thing. In my case I like having more fine-grained control over my own ActivityPub implementation, but that's just an excuse. Truth be told, if Fedify were around when I looked into starting AP integration in NodeBB, I might've gone that direction.

@shoppingtonz@mastodon.social if edits from PieFed aren't reflected here that may be a bug.