With the exodus from big tech social media, people often wonder where they find events for their city or community. The need for community driven/owned event calendars rises and with it people starting one themselves. Nowadays there are a couple of viable technical solutions, but the real question is: How do you get people to use them. In this blog post we reflect on nearly 5 years of building and operating @eintopf@sueden.social We hope this will help others to make their calendar a success. Comments and additions highly welcome.
Front page
@Wtebbens@social.coop im referring mostly to Jacobin (bonfire for publishing), Totnes Pulse (bonfire for neighborhoods) and boven-jan (bofnire for mental health communities)... happy to share the gist of those on a call if you want, and open to get help on writing more about those!
Dear @ivan @mayel, we're collecting stories about inspiring "Connected Community Spaces" and would like to get a few @bonfire stories.
Could you give us more info on the jacobin.de case? You presented at the https://fediforum.org/2026-04/session/7-b/ is their more details available?
Other stories about communities adopting Bonfire as their toolbox to shape their community space might be of interest.
I'm asking for the FKI, DTF and others around us who'd love to learn more, document it for our communities and help telling your stories 🙂
@Wtebbens@social.coop hi! We will publish a couple of case studies during the summer going through all the codesign and development we did with 2 projects we are involved with👍️ @bonfire@indieweb.social @mayel
@lauti@bonfire.cafe is LAUTI working with Mobilizon and Bonfire for events? Would love to do some kind of integration via AP 
@julian@activitypub.space @liaizon@social.wake.st
We laid out the details of our fediverse strategy and cooperation with bonfire in this blog post: lauti.org/blog/lauti-updates...
And overall we collaborate with Mobilizon and Gancio @lesion@mastodon.cisti.org via @linos@graz.social @blog@event-federation.eu and the FEP-8a8e. All plan to implement that to have a common base for federating events. Not sure how far the implementation on their side is. @linos@graz.social do you know more?
Would be awesome if NodeBB also supports the FEP in the future.
The next step in our #activitypub implementation is ready! This brings a simple instance actor object along with #webfinger support for it and a #nodeinfo endpoint.
We highly appreciate reviews from any #fedidev 🙏
codeberg.org/Klasse-Methode/...
We are really greatfull for @nlnet@social.nlnet.nl to fund this work and for @linos@graz.social for being such a great mentor!
Feature Highlight for v4.12.0 — Activity Intents
@mayel@bonfire.cafe summary is only sent with as:Article, so your Article carve-out should have worked (but didn't, maybe btfree.org is running an older version).
But your fix combined with mine should solve the problem twice over.
@julian@activitypub.space awesome 😊
@julian@activitypub.space we added an exception for Article but will switch to instead only do that for Note.
@thisismissem@activitypub.space @evan@cosocial.ca @ivan @smallcircles@social.coop @liaizon@social.wake.st
@julian@activitypub.space will that work for you or are you sending Note with summary but no sensitive tag?
@ivan @liaizon@social.wake.st @smallcircles@social.coop @evan@cosocial.ca @thisismissem@activitypub.space
Feature Highlight for v4.12.0 — Activity Intents
@thisismissem okay, but it seems as though Bonfire now treats summary with missing sensitive as a CW.
@julian@activitypub.space we added an exception for Article but will switch to instead only do that for Note.
@thisismissem@activitypub.space @evan@cosocial.ca @ivan @smallcircles@social.coop @liaizon@social.wake.st
Do we need to have a CEO of Wikipedia? Can we maybe just not?
@smallcircles@social.coop @mayel @liaizon@social.wake.st @ozoned@btfree.social
Its because we currently use the summary field as cw text when present...
@lauti@bonfire.cafe Yes, but.
I did this and I found that some remote servers don't set the Accept header correctly when fetching the server actor. They get tangled up in the content negotiation.
I eventually made the server actor use the same routes as the other actors on the server, except with the domain name as its preferredUsername. This seems to work really well, especially with default Webfinger lookup.
@evan@activitypub.space Interesting! Do you rememeber with which software had troubles?
Regarding preferredUsername did you configure it so that you could search for @instance?
@lauti It's okay, Lemmy and Friendica put a server actor there.
>activity delivery issues
My server drops your Accept activity because you don't sign the Digest header.
@silverpill@mitra.social yes, that was it! We succesfully federated the first event from lauti to mastodon (and maybe other fediverse software too) 🎉
If you want to receive random test events follow @events@lauti.sankara.klasse-methode.it 😆
Is it okay if the instance actor id is equivalent to the instance url? Does anyone know if most other implementaions support this?
Also if anyone can help with debugging some activity delivery issues that would be awesome 🙏 #activitypub #fedidev
@events@lauti.sankara.klasse-methode.it is our test server. But if you try to follow it the Accept is not being delivered properly
Is it okay if the instance actor id is equivalent to the instance url? Does anyone know if most other implementaions support this?
Also if anyone can help with debugging some activity delivery issues that would be awesome 🙏 #activitypub #fedidev
Cose difficili
Test from icecube 🥸
@Bonfire@bonfire.cafe Running it already!
Hmm. I seem to be having some issues with search. Do I need to change anything on the config side for 1.0.4? (Trying to tag somebody in the composer is showing me ActivityPub IDs, not tags, and trying to use the search box just starts a UI reload loop)
@mavnn@bonfire.mavnn.eu thanks for reporting! We can reproduce the autocomplete issue but not the search, could you please send us app logs of when it refreshes?
Checked if there was a @Bonfire@bonfire.cafe release for the first time in a few days and noticed there was, and then was puzzled when I couldn't download the container image.
On double checking the time stamps, turns out I had tried to pull the image less than 2 minutes after Mayel pushed the commit.
@mavnn@bonfire.mavnn.eu it's out now 😊
Thanks @erictapen@chaos.social for creating this need FEP-8a8e compliance checker. We already integrated it into our CI to support the development of #activitypub into #LAUTI.
