As mentioned in the issue, we could extend the API but then each client would have to specifically implement the additions. There's a risk of duplicating types added by other apps in incompatible ways unless there's something like FEPs or RFCs for the API schema?
Bonfire
Public Interest Social Networks
Bonfire is built by communities, for communities. Rooted in autonomy, mutual care, and collective power. Co-create your tools, reclaim your data, and resist manipulation by shaping your own federated digital spaces.
Previously at @bonfire@indieweb.social
> you mention this would be a limited window onto Bonfire, is that just because you only implemented a proof-of-concept so far, or is it because Bonfire would have features that the existing clients wouldn't support (yet)?
It's because of features not available in the Masto API schema (like boundaries/circles) but also since Bonfire is extensible and some extensions implement new object/activity types beyond the note/post...
Here's an issue going into more details about the different options: https://github.com/bonfire-networks/bonfire-app/issues/1260
Feedback welcome!
We did implement a partial Mastodon REST API as a proof-of-concept (attached are some screenshots of a Bonfire feed displayed in different clients). Of course that would come with several limitations, like when displaying activity/objects/metadata not supported by the API and client, or with features not available such as the option to select custom boundaries/circles when posting...
📣 We're looking for communities and individuals interested in setting up their own Bonfire instances over the next weeks.
We need your help to:
- Use Bonfire in real-world scenarios
- Federate with each other and the wider fediverse to test interoperability
- Monitor performance under active use
Your feedback will help us get Bonfire Social across the finish line to a stable 1.0 release!
We’ll be happy to provide guidance throughout the whole process ✊
Please boost or reach out if interested!
@nicd@masto.ahlcode.fi @bonfire@indieweb.social oh thanks for reporting! that's new, will fix it!
Wait does @Bonfire have the potential to grow into the open source, non-evil Facebook alternative I've been dreaming about? 🤔
@3TomatoesShort@disabled.social that's what we're betting on
📣 Kicking off a week of exciting news from Bonfire by bridging online and offline worlds:
✊️ Join us May 9th at Làbas - a self-managed social municipality in Bologna, Italy where we're facilitating a collaborative Bonfire workshop with #municipiozero and scift.
Together, we'll install a Bonfire instance and collectively configure extensions, community guidelines, and settings tailored to their specific needs 💅
municipiozero.it/events/bonf...
Stay tuned for more announcements 🔥
🎉🔬 More news this weekend.
@sciety (eLife's preprint evaluation platform) has secured funding from @nlnet to build a Bonfire flavour for federating preprint reviews and discussions.
This means federated, community-governed spaces for open discourse around scientific preprints outside traditional publishing gatekeepers.
Read the full announcement: https://blog.sciety.org/sciety-secures-funding-from-nlnet-foundation-to-help-build-discourse-around-preprints/
Such a nice conversation! great to have touched base with bida collective @thunderpussycat@d0c and @scosso and eager to see how municipiozero will experiment with using bonfire to empower grassroots and self managed activities in their communities!
Bonfire is a federated social network built by communities, for communities—rooted in autonomy, mutual care, and collective power. Co-create your tools, reclaim your data, and resist manipulation by shaping your own federated digital spaces.