#bonfire_feedback rendering issues with long posts. Firefox.
#bonfire_feedback retrying sending a pic. If it does not show, pics are broken. (it seems to upload fine, but showing is not there?)
Discussion
#bonfire_feedback rendering issues with long posts. Firefox.
#bonfire_feedback retrying sending a pic. If it does not show, pics are broken. (it seems to upload fine, but showing is not there?)
#bonfire_feedback rendering issues with long posts. Firefox.
Can anyone point me to any manual or examples of the economic aspects of Bonfire?
https://bonfirenetworks.org/ scroll down to the "Powerful Building Blocks" section, maybe select ValueFlows
Or pick the "Blog" link at the top to see what's been done
Can anyone point me to any manual or examples of the economic aspects of Bonfire?
Ok, so what's this about?
Normally I'm on dcht00@social.coop .
Hello folks. 😊
I have a shared server at Mayfirst.coop.
Is that enough to try a Bf installation or does it needs a virtual private server?
Thanks a lot...
Back to this information about upcoming Bonfire capability: https://bonfirenetworks.org/docs/boundaries/ In the "circles" diagram, there is a circle of relationship "exchange" where we have a paid relationship. An example IRL exchange could be someone with which I have a handy-person relationship. I want someone who is IRL near me. With this particular iteration of Bonfire, I would have to identify all the handy-people who meet my requirement of "near" IRL and place them in my exchange circle.
Here are the two use cases I know of:
on NextDoor (ND) app, I have a neighborhood, so I know (sort of) that putting out a "need IRL help" to my neighborhood is supposed to result in "near" IRL people seeing my help request. This assumes ND is properly not over-distributing my posts beyond my declared neighborhood.
a Unitarian church near me offers a service to connect less-abled members of that particular church to more-abled members for getting needs met. Again, the church "instance" provides the IRL "near enough" element for connecting those with needs to those with offers.
Both of these use cases are examples where ValueFlows (VF) are intended to service (AFAICT). Seems that the Circles function in the Boundaries description are trying to set up, maybe, a future entry of ValueFlows enablement-- maybe? Or maybe, the Circles function is supposed to help set the IRL parts of VF implementation? Here's the example I'm thinking of wrt VF: https://www.valueflo.ws/assets/ValueFlows-Story.pdf In this story, since apples, pies, and truck sharing are physcially exchanged, they need to be IRL near.
Protecting oneself online is an important aspect of the boundaries (and circles) function described. IMO, it needs to go the other way, too.
For thoroughness (and to allow me to find this again later...) here is some additional connection:
The boundaries feature is explored more here: https://bonfirenetworks.org/posts/how_to_boundaries/
My take on the boundaries section of this page is boundaries are how the Fediverse environment affects the user who sets the boundaries. Another take on boundaries would include how I, as a user posting, affects the ecological environment in the sense of computational heat generation in the service of transporting posts beyond my screen and cost of services to do so. This is along the lines of https://www.theguardian.com/environment/series/the-carbon-footprint-of-everything. Me as a user might want to trade my use of email's eco-environmental cost vs using the Fediverse. I want to limit the potential reach, so I know I'm trading to my eco-environmental goals.
It looks like I can use Circles as a way to limit the eco-environmental cost of communicating (nts: see the How-to boundaries link above)
https://nlnet.nl/project/Bonfire/ Some thoughts after reading this:
Noodling on use cases for a person like me wrt Bonfire. Guess that starts with trying to figure out the bits and how they might fit together. I'll toss some ideas here to try out what's there and how it feels.
There's this, of course, very oriented to dev rather than user: https://bonfirenetworks.org/
Also, there's this: https://nlnet.nl/project/Bonfire/ which feels a bit more oriented to informing users of Bonfire. Still thinking about that.
btw... couldn't find the nlnet.nl link through g**gle search but could on Duckduckgo. Interesting.
This “call to action” for Universities to join the fediverse is a fair summary of the benefits and costs, but moderation is a huge liability. So I wonder if academically focussed apps like OKLi might tip the balance and make it more obviously worth their while… https://netzpolitik.org/2023/a-call-to-action-universities-of-the-world-into-the-fediverse/
OLKi: research papers, datasets and peer reviews on the #Fediverse https://olki.loria.fr/platform/?utm_source=thenewstack&utm_medium=website&utm_content=inline-mention&utm_campaign=platform#
Should I start a wiki?
I wonder when I will reach the point in which my homelab goes full BSD. If only there were Plex builds for NetBSD.
I believe I promised a (third) blog article under that premise years ago. The custom TLD and custom root servers are on my blog. The certs are in my TODO list. Somewhere.
am I the only one seeing this list and thinking “huh, would be neat to know everything from that list without needing to check on it again”?
for those curious, if I were to ask my browser to print it, it would turn this list into 54 A4 pages.
am I the only one seeing this list and thinking “huh, would be neat to know everything from that list without needing to check on it again”?
Either I was lucky with my timing, or .photography NS changes propagate really quickly
Guess what just popped up on my timeline. https://hackers.town/@thraeryn/110684203105257506