@Aljoscha I'm a bit hesitant to put a version on go-ssb butt I regularly cross compile go-sbot to two deployments, you might have used them already.. :)

They don't crash or leak all over the place but since it's all concurrent and not at all optimized for memory allocations yet, it will eat upto one maybe two gb of ram, depending on the size of the network you throw at it. Some numbers for the xxZeu-pub: I have it at hops:2 and it tracks 10k feeds with 1.4mio messages using about 1gb of ram after loading the repo with its index k:v's and stays under 1.5gigs for about 18hrs while it is getting 0.1 new connections per second avg over that timeframe.

I try to squash them but hanging bugs can accumulate and I hate to say it but it's still a back and forth of fixing and introducing new bugs around muxrpc and session handling. Complicated way of saying: It might need a little supervision but a daily cronjob to restart it is enough, at least for the current master and I intend to for less not more of course.

With that disclaimer out: I'd love to hear from your experience with it would help where I can to get it useable. The building instructions on the readme should help you get the bot and cli binaries built, if you choose to shine light down this rabbit hole.. :)