A bonfire builder. They/them.
I wrote a thing as, having being confused about 'granular boundaries' I'm now rather excited!
https://dougbelshaw.com/blog/2022/07/30/bonfire-granular-boundaries/
@BonfireBuilders
👋 Hello, @ivan and I would like to share with you our application for the next round of the nlnet user operated fund: https://nlnet.nl/useroperated/
tl;dr we want to implement groups on bonfire, based on the work we did with boundaries and circles: hackmd.io/BlYSKmlcSk2yn_iAxS...
Any feedback is more than welcome 🔥 (deadline is tomorrow, so we are quite tight with timing unfortunately)
I have a suggestion for Bonfire:
@BonfireBuilders #bonfire_feedback
The current playground instance is so slow that sometimes I don't understand if there is an actual bug or if a request just timed out due to lack of capacity. Would it be possible to give it more juice?
This article (which you may have encountered before), first published in 1969 and added to in 2000, should be of interest to anyone who wants to think about non-capitalist perspectives on community, hierarchy, egalitarianism, and the commons.
This article (which you may have encountered before), first published in 1969 and added to in 2000, should be of interest to anyone who wants to think about non-capitalist perspectives on community, hierarchy, egalitarianism, and the commons.
Ok, so do we have to accept federation requests in the federated TL? 🤔
also, i'm curious about how lightweight Bonfire is. Like can it run on a very low config ? Does it uses a lot of resources both on back and front end ? #sustainabledesign
i'll go and search the website but still asking here just in case 😬
Indeed, you can run on Rasperry Pi for example 😊 Of course it depends how many simultaneously-active users will be using the instance, but for small instances it is perfect.
am i the only one having desktop Bonfire using open dyslexic font regardless of font chosen in settings ? ^^
You probably have it installed on your system? We need to find a better way to set the preferred font so that locally-installed fonts don't override the setting.
Every definition of "entrepreneur" I can find involves an (heroic) individual... but I don't want the future of co-operativism to depend in any way on that sort of romantic individualism.
I want co-operatives to, instead, develop collective modes of deliberation and consensus building, with as little institutionalization of power structures and as little reliance on charismatic personalities as possible.
As someone who used to identify as a "social entrepreneur" in a past life, I really don't understand people who seem to share similar values/goals but still feel the need to hold on to the loaded language of the hegemony.
Yet another social network that doesn't support tag following :(
Why is every iteration is so derirative lacking of any basic innovation like discovery, or markdown formatting. Diaspora was way ahead of it's time.
Interesting. I found my profile and the post from elsewhere in the Fediverse though.
yes you can do manual lookups, but not follow
My #firstpost from #bonfire.
Now let's see if this federates...
Yep, and to grant them the same permissions within that boundary.
I have a suggestion for Bonfire:
@BonfireBuilders #bonfire_feedback
What is an example circle name with associated boundary name? I'm trying to figure out the best way to structure in my head. I have a circle for "devs" but I'm not sure the best boundary to make or if I can reuse an existing one
Transcribing them here:
Example circles
- Besties
- In-laws
- Trip mates
Example boundaries
- Memes & lols
- Summer '22 trip
- It takes a village
One way to think about it is circle names are simply about what the people in them have in common, whilst boundary names should probably be more about what kind of content you'll share and what permissions you'll grant over it to whom (note that a boundary can contain multiple circles and individual users, granting different permissions to each).
So extending your example, I could imagine having:
Circles
- Devs
- Bonfire devs
- Techies
Boundaries
- Tech stuff (granting see/read/interact permissions to those 3 circles)
- Coding resources (granting the same to the first 2 circles)
- Bonfire collab (granting additional permissions to Bonfire devs circle, like the ability to edit and delete)
I have a suggestion for Bonfire: it seems multi-level bullet lists aren't supported
Let's see if that works now: flic.kr/p/2nyyAFq
A quick update: we're just about ready to release the first iteration of circles and boundaries, which you can read about here: bonfirenetworks.org/posts/in...
We deployed the update to the playground earlier but ran into a mysterious issue that didn't appear until now, so have rolled back to the previous version until we figure that one out. Wish us luck! 🤞
There's a list of changes here: playground.bonfire.cafe/term...