Hello World 😉
@KazukyAkayashi welcome 🤗
@ivan@campground.bonfire.cafe
explore territories
- Joined
- Website
- Ivan.cafe
- ivan minutillo
- orcid.org/0009-0007-4869-4864
🔥 We've just rolled out a new feature: thread titles.
Add a title to your thread - either initially or add it later as discussions develop and edit it if the discussion takes another direction. We're exploring if this offers more context to discussions, driving better user participation and streamlining discussion management. Try it and let us know what you think!
With this entry, <1 day of engagement here. Enticed by some posts by https://xn--ocane-csa.fr/ on #Mastodon and their website. I've only just started to read https://bonfirenetworks.org/docs/ and https://www.w3.org/TR/social-web-protocols/
See document: https://www.platformaccountability.com/proposal, then scroll to the bottom. It shows some suggested measurements and some objectives for those measurements. Some for within a post/thread and some situated elsewhere TBD. The white paper contains more detail.
So sorry to be commenting without completely reading the specs first. Understood this particular comment period was for 2 weeks, and unsure I could finish and grok the specs in time to have a worthy basis for comment. I couldn't find a reference to the platform accountability document anywhere in the #Fediverse yet (but that be my weakness in search skills here). Wanted to be sure this work was known. Seemed like there were at least overlapping goals in the bonfire measurement goals noted here and the platform accountability goals.
@CynthesisToday @mayel the White paper looks extremely interesting...thanks for sharing, will read it over the weekend and get back to you 😊
@ivan Maybe show the number of flagged/reported posts?
Usually when I see many posts being flagged it's a sign of the thread going wildly off-topic or even attracting bad actors. I then stay away from that discussion. However, e.g. in Discourse I won't know until I have read through the posts. Having that metric on the top post would help me spend my time and engagement elsewhere.
Thinking of risks, maybe showing flag stats would attract more of the same? I would hope not in an otherwise functional community, but some people seem to gather around car crashes or houses on fire.
@lne super interesting, wondering if it is a valid metric though and in which ways it may have privacy implication ? A thread may have a lot of flagged activities because it talks about a complex topic (covid, politics, religion, gender ...) and users want to properly moderate it, on the contrary a thread without flagged activities may be just not moderated at all and being full of trolls ?
Maybe we can show a label only when the amount of flags exceed a certain amount (eg. after 30 flags on the whole thread) - as an indication 🤔
Hmm gotcha, I'm not sure if I did or not. They were green toggles. I see the new interface now for the custom roles and I no longer see the built-in roles.
fyi we're planning a round of user design session with @dajb to fine tune the current custom permissions and roles UX/UI - as they're still confusing ( and they're one of bonfire core features )
@mayel @ivan
Quantity of comments is good and necessary and has already been discussed.
WDYT about including the "position" in the discussion?
It helps to understand the present comment/post in context.
This indicator has a simple structure: P/T where:
- P is position and
- T is total number of comments.
I know it's not that easy to count (do we count bifurcations and/or other open lines of discussion?) buy it gives some idea.
It is not the same to see "23 comments" that "comment 21 of 23" or "comment 4 of 23".
Ideas, critiques, hurrahs, anguished screams or other reactions to this? 😉
now that i think of it, can bonfire not follow mastodon on the ''like'' = star thing?lol
everytime i click on it i have years of star= favorite bookmark taught by internet in the brain
a bonfire is a fire sooooooooooooooo, maybe a fire reaction? no likes, only hyped fires 😁
@lefterino done! great suggestion!
That highlights the need for open data and federation, because while it'd be quite simple to create a replacement for that app, the value is in the network effects (the more users the better) and the accumulated data. Time to federate our network effects!
@mayel composition not accumulation is a great mantra (from donna haraway)
ivan minutillo
boosted
now that i think of it, can bonfire not follow mastodon on the ''like'' = star thing?lol
everytime i click on it i have years of star= favorite bookmark taught by internet in the brain
a bonfire is a fire sooooooooooooooo, maybe a fire reaction? no likes, only hyped fires 😁
No doubt Discourse's stats are awesome!
I would say it would be nice to have those avatars at the bottom of people who have engaged in the conversation - showing first the people you follow or you mostly engage with and an option to expand to get the whole list of people who interacted with the post. Maybe -this could be controversial- an AI-derived icon next to people's avatars in the list indicating if they agree or disagree with the original post.
@jl I also agree that participant avatars are a relevant info to show 👍️ .
Re. AI: we actually did some very first experiments in the field of sentiment analysis , but to properly integrate AI in bonfire we need to do some work on the infrastructure side, to avoid putting any strain on the (typically small VPS) instance’s server
At present, our discussion page lacks any statistical data about the thread, a feature that is pretty common in most of social networks or forums. These platforms typically display a total count of replies, boosts, likes, and participants.
Take Discourse as an example, a platform with a great UX for productive conversations. Discourse displays the list of links shared in a post and provides a statistical box that details thread engagement. This includes also an approximation of the time required to read through the entire thread, if significant.
What are some meaningful statistics we must/should incorporate for the Bonfire 1.0 release? We are seeking to find statistics that can effectively foster engagement in discussions without solely promoting addictive behaviors. Any thoughts or suggestions ? #bonifre_feedback
#bonfire_feedback Only two things:
Passkey/2fa
Native app.
@LibertyBeta thanks
we've 2fa in beta, currently disabled because of UX issues
Native app is in the roadmap, it will likely come in 2024
Join us in testing comments and discussions in #bonfire!
For the next 2 weeks, we're honing our focus on fixing and improving any aspect of this core feature, and we would love to do it together with our community. Let's collaboratively craft a space that fosters both lightearted banter and profound discussions.
Here's how to get involved:
1️⃣ Join the conversation by creating a new post or responding to existing ones.
2️⃣ Spot a bug or see room for improvement? Let us know! Post your valuable feedback and don't forget to tag it with #bonfire_feedback.
3️⃣ Your feedback doesn't go unnoticed. We'll gather all the reported issues in our tracker, focusing on the most critical ones in our current milestone: github.com/bonfire-networks/...
I encountered this issue while using Bonfire:
Trying to follow a friend, the pop up "Could not follow "appeared.
@BonfireBuilders #bonfire_feedback
I also encountered another issues:
I liked a post, the pop up "Could not like this "appeared. After I log out and login again the 'like' star appeared.
@JohnTax94 yeah weird one, it is recently introduced will dig into it! thx
ivan minutillo
boosted
Fractal Software for Fractal Futures
Some updates about the development of federated #groups in bonfire:
indieweb.social/@bonfire/110...
Article: bonfirenetworks.org/posts/de...
(The federated group development has been made possible thanks to the #Nlnet Entrust grant)
oh wow, I didn't expect the "Compose" button to add that post as a reply to the one I was looking at. I figured "Compose" means compose a new post, not a reply #bonfire_feedback
@dragfyre weird., the compose button does create a whole new post even if you're in the thread page, maybe a socket bug?
