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)
@bonfire Are these apps specific to the Bonfire ecosystem? i.e. do they need to be written in Elixir?
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).
Also note that this would mean missing out on all the libraries (be they a generic AP implementation, circles functionality, a search index, a collection of UI components, etc, etc) that we are developing to make it easy to build something bespoke without having to rewrite all the common functionality from scratch...
@bonfire would the device be required for 2 & 3, or an optional enhancement? Will there be public instances of the service and apps?
The device is not required (though would be the easiest to get set up). You could run the apps on another device at home, like a Raspberry Pi, regular server, or even on your personal computer (though they'd of course only be usable when it is online). You could also host them in the cloud, though we want to discourage that.
The Bonfire team will operate an instance of the AP server in the cloud for users of the device (and potentially others).
Whether and how anyone will set up open instances of the apps is TBD.
INDIEWEB.SOCIAL is an instance focused on the #Openeb, #Indieweb, #Fediverse, #Mastodon #Selfsovereign #identity (#SSI), #Humanetech and #Calm technologies evolution.