Hey friends! Please join the new test instance at https://campground.bonfire.cafeWe also updated the website at bonfirenetworks.org which hopefully explains the project a bit better While the playground was about experimenting with the UX and all the different features and extensions in the works, the campground only has the core and social extensions enabled while we focus on stabilising them (incl. federation) before a v1.0 release.(We'll come back on the playground and the other features soon, don't worry!)indieweb.social/@bonfire/109...
Sorry Doug it took me some time (just needed focus on work deliverables and events). Yes, as benefits for the writer I can think at least 2: UI appropriate labels and translations where there is text (nothing terribly valuable, really, but smoothing), spell checking (although not so easy since today is common to have mixed languages in a toot, but anyway...). Eventually this could create a shared list of words in the instance or a group so as to make a better spellchecking for everyone. As benefits for everyone, as you said, there is filtering and also translations. If we know each person preferred language/s, we can offer translated versions by default for certain languages. This could be part of each User preferences. That is, each account can specify what language/s: the UI is preferred.the posts are filtered/allowedthe posts are translated or not by default. WDYT? :)
🎺 Just updated the playground. New goodies include:A basic coordination appAn updated layout and navigation incl. an app switcher Many fixes & tweaks (and a few remaining broken things on our to-do list)An [incomplete] changelog as always is available at playground.bonfire.cafe/term...
If it's not the time to ask this I'm sorry and please simply dismiss this post.
Imagine that you already have a community working on a CMS or LMS (like Moodle, Wordpress, Discourse, Drupal, etc.) with a bunch of users and a way to manage them (create, give roles/permissions, delete, etc.).
Is it, now or planned in a near future, a way to somehow connect that with a Bonfire instance so we don't need to have double users, one in each platform? Or -in the other way- can Bonfire provide this authentication? One platform to rule them all, one platform to find them, one platform to bring them all and in the Fediverse light bask them? 🤣
In brief: can Bonfire accept/provide identification by/to other sources?
Thanks a lot, and I hope this discussion opens some possibilities. :)
The +bonfire playground has been updated with a few fixes and improvements. My new favourite screen is this one which feels like a forum focused on your interests: playground.bonfire.cafe/topi...
Still on holiday and taking a break from social media in general, but sharing this here as it's relevanito the kinds of conversations that (I believe) @BonfireBuilders are trying to create... dougbelshaw.com/blog/2022/08...
The playground has been upgraded with a few fixes and improvements, some of which are listed on the changelog... Feedback welcome as always!
But what if we include the possibility to add roles to users for threads? Eg. the thread moderator, the thread merger (which is responsible of cleaning the thread tree by merging together similar answers together), thread taxonomer (who is responsible of putting threads in their relevant topics), and so on
I guess somehow is about exploring the interconnections between social gardening , social networks and forums :)
uhm I feel i was more confused than before, let see if some more coffee helps 😅 😅 😅
Feature request: being able to redact, not delete, arbitrary posts (according to the post boundary) to preserve the tree structure @BonfireBuilders #bonfire_feedback +bonfire
here an attempt of an improved UI for boundaries, the main outcomes are:
- Reduce the permissions list toshow only the relevant ones for each activity type (eg. see / read / like / boost / mention / reply / edit (future one) / delete (future one) ...)
- Default the permissions to be the same for all the users/circles involved
- Let the user expand each verb to customise the permissions for the users involved (fig.3)
- replace the 3 icons that shows the permission states (can / undefined / cannot) with a more standard 3-toggle state
I agree boundaries is not an ideal term, but not because it is abstract, it just doen't fit 100%. Bounded posts are not changing their shape, or growing or shrinking in size. They have certain rules about who can see and interact with them. It is like every post can be its own little forum. My suggestion would be rules or access.
Circle I think makes sense. But due to social network nomenclature, maybe group or camp members would work better? If you want individuals to understand what they are using, similar verbs may be necessary for similar concepts. Otherwise, it can produce confusion regardless of the intention for simplicity or clarity.