📣 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!

@bonfire looking for existing communities or are new communities / ideas welcome as well?

@digigeek new communities very welcome as well!

@pescetarian we have a progressive web app that works pretty good already - but we plan to release native apps as well in the future.

@bonfire It would be great to have ARM64 Docker images available as well

@histrio ah yes thanks for the reminder! we need to configure our CI to generate those again

@bonfire

This sounds very exciting! We'll be in touch 👀

@newsmast so glad to hear this 😀

@bonfire I’ve been reflecting for some time on building a local social network prototype for my city, aimed at connecting people who are dissatisfied and seeking solutions to their everyday problems, starting from their own neighborhoods. At the same time, I’d like this medium to give rise to a local journalism collective made up of these people and focused on these issues.

@bonfire @pescetarian what is the compatibility with mastodon clients? That could solve this!

@bonfire @akshay @3wordchant @dphiffer @edsu @edumerco ^ 🥳

@sounddrill @bonfire @pescetarian
I do completely back up this proposal: at a minimum, Bf should work with any standard ActivityPub client.

Then, if certain features specific to Bf are not implemented on them, it makes total sense to add them to a specific client.

Also, a progressive web app seems a very solid starting point bcs sustaining a native app takes a huge effort along time, and it is debatable if this is the best use of the limited efforts available as of now. :)

@edumerco @sounddrill @pescetarian

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...

@edumerco @sounddrill @pescetarian

So it's possible but would offer quite a limited window into Bonfire while being quite an extensive API to maintain. We'd welcome contributors/PRs who want to make that happen though!

Not a programmer here, but if UX/interaction is useful, we already collaborated a bit before and can happily engage again. :)

I heard and understand the point, but still think that interoperability with the rest of the Fediverse (as possible) is crucial.

Also, having seen people maintaining native apps for IOS and Android (ind it's various parallel working versions), just wanted to warn about the (potentially) upcoming ragnarok that could ensue... ^_^"

@bonfire @sounddrill @pescetarian

@bonfire @pescetarian @sounddrill @edumerco i would also think having a masto compatible REST API would be a huge boon for your project. there's a very strong and high-quality app ecosystem. 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)?

(i maintain a client for mastodon API servers, and i explicitly aim to ensure support for software beyond mastodon itself. i suspect other client devs would behave similarly, but this only happens on the basis of supporting the masto api.)

best of luck in either case...

@mousebot @pescetarian @sounddrill @edumerco

Here's an issue going into more details about the different options: https://github.com/bonfire-networks/bonfire-app/issues/1260

Feedback welcome!

@mousebot @pescetarian @sounddrill @edumerco

> 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...

@mousebot

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?

@pescetarian @sounddrill @edumerco

@bonfire@indieweb.social For those interested in setting up Bonfire with a declarative approach on #Guix systems let me know if I can help. Currently my personal instance is running on the latest Guix at bonfire.fishinthecalculator.me .

@histrio have now added arm64 and arm32v7 (for Raspberry Pi) to our CI builds: https://hub.docker.com/repository/docker/bonfirenetworks/bonfire/tags

@bonfire if all goes well will likely setup an instance under the umbrella of nmmdc.org assuming the docker deployment goes easily. 🤞 🔧 #nmmdc #nm

@Mumonkan great! Let us know if you need any help!

@bonfire does this include an ability to create private online spaces?

@patamystic yes you can switch from having a local-only or public instance from the admin settings (plus a third-option to manually fetch remote activities :))