Discussion

@jvalleroy

We'd of course welcome others wanting to implement the sync protocol that Bonfire will use (for the apps to talk to the AP server) in other languages to enable non-Elixir apps to participate in the ecosystem, but the Bonfire team only has the bandwidth and interest to focus on and support Elixir apps (along with some Rust components).

@stevenroose @mayel @rysiek @tcit@social.tcit.fr @karen@kawen.space

It's basically the same project, in that Bonfire shares all the goals that CommonsPub had but adds things like the hardware device and the optional separation of the federation server (AP inbox/outbox and storage ActivityStreams data in the cloud) and the apps (UI, app logic, relational DB).

@Downes

And to address your concern, we're thinking to try a sustainably model where you can pay for convenience (in the form of optional cloud services and preconfigured hardware) but everything is FLOSS so you can self-host and DIY without loosing out on any functionality.

@dajbelshaw @ton

@Downes @dajbelshaw @ton check out Nextcloud which is a fork of OwnCloud (by many of the same people, who didn't agree with the direction)

@Argus@mastodon.technology They're also one of the few spaces we can still socialise in this age of social distancing (at least during the cold months). Let's light more bonfires!

@Argus@mastodon.technology bonfires often start among a small group of friends and then may attract neighbours and others who want hang out for a while. Also burning stuff is fun!

@humanetech@mastodon.social

Thanks 😊 still lots of work to do in this, but we think it's worth trying!

Just launched a first draft of our website with a little info about what we're cooking: https://bonfire.cafe

TL;DR: Bonfire will be:

1. a pre-configured device
2. a fediverse identity hosted service (which syncs between the fediverse and the device whenever it comes online)
3. apps (web apps but they run on the device instead of the cloud)

Hello, fediverse!