Specifically with the threadiverse as well, hopefully we'll start seeing Bonfire users popping up around here soon enough.

@evan > sorry to disappoint youNot at all. I'm no fan of friendly fire, and pleased to learn I was wrong on that score : )@mallory

Sadly no dice, but I will try again with some better logging in the morning. I'm curious to see what your Accept looks like <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f937.png?v=c7cc56fe415" title="" /> but I guess if it's failing signature validation then it's not even getting to that part.

@julian seems a lot of people followed it when developping I caught a couple of randoms (I totally forgot about Friendica) in the bot validator after deploying the new rules, looks like it's safe enough to push in that format to avoid filtering out the fediverse

@oliverandrich I'll ponder on this and see if I can come up with some starting points. The library does have a "reference server implementation"[1] but it's not entirely "minimal", because in it's smallest form an ActivityPub server needs to do quite a lot already: 1/ dispatch locally stored objects when requested2/ process remote activities targeted at local actors3/ process and dispatch client activities of local actorsOn top of these actions, a server might need to have additional behaviours attached to certain Activity+Object combinations.https://github.com/go-ap/fedbox