Today, the Bonfire team is excited to announce our beta release 🔥🎉
We’re aware that Bonfire still needs a lot of work - like ensuring it federates as expected and improving configurability, accessibility and user experience - but that’s the point: we decided to launch at this stage with the intention of building the 1.0 release as a community.
🗞️ Blog post: https://bonfirenetworks.org/posts/meet_us_at_the_playground/
🌈 Signup on the playground instance:
https://playground.bonfire.cafe
@bonfire Congrats 🥳
@bonfire very exciting!
@bonfire I've read https://playground.bonfire.cafe/terms/code-of-conduct/and it's not for me.
@bonfire Looks neat.
@bonfire
> In general, we're getting into the habit where any hesitation or disagreement about a feature is used as an opportunity to add a user setting for it, meaning that the user is the one to decide how it should work. Developers and instance admins still hold power in setting the defaults, but ultimately it should be up to the people using Bonfire.
Oh gosh yes!
@bonfire Is it just me, or does the page at:
https://playground.bonfire.cafe/create-user
keep reloading?
@Relected bonfire tends to be an extensible and highly configurable platform (aka framework) to develop any kind of federated apps, that goes beyond microblogging (think at federated calendar / tasks coordinations / governance / and so on)
@bonfire congrats!!!
@bonfire Congrats. And excellent approach (in general, I mean, with the extensible core) :)