Discussion

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

3/3

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.

2/3

At present, #bonfire 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 ....

Full discussion on the campground ▶️
https://campground.bonfire.cafe/post/01H39EJQ8B0SC7BQHDP40TJ0C3#activity-01H39H0KM6JGNTM4ZHJ9714E6P

1/3

@BB oh thanks for the report! it seems we have an issue with pagination when you're not logged in, will look into it. Can you please try creating an account in meantime?

2/2

Here's how to get involved:

1️⃣ Navigate to https://campground.bonfire.cafe and 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: https://github.com/bonfire-networks/bonfire-app/milestone/41

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.

1/2

@strypey @bhaugen indeed we are working on groups functionality, you can read more here - http://bonfirenetworks.org/posts/dev_diary_groups_1/
- http://bonfirenetworks.org/posts/custom_roles/

We will deploy groups on a ad-hoc instance for people to play with and test, likely in the coming weeks.

hey @brianb thanks for the feedback! It is true that in most of the case the subject of our communications are communities, rather than individuals - so we totally understand the confusion. Addressing this challenge is high on our agenda, and we're glad to have @dajb on board to help us navigate this 😀
ps. and you're more than welcome to participate as well 😃

A great article delving into the power of fractal software to empower organizations in post-capitalist worlds and imagining how Bonfire can benefit from adopting the fractal knowledge model itself.

https://fossil-milk-962.notion.site/Fractal-Software-for-Fractal-Futures-71e515597d6b424c994cae74f3341521

#FractalSoftware #Bonfire #PostCapitalism #FutureOrganizations

@kainoa may be worth looking at https://ffdweb.org/ - they seem to fund a wide range of projects (not only Blockchain things)
Good luck!

@box464

🔥 📣🔥 Dive into our latest #Bonfire blog post where we explore the development of federated #Groups
http://bonfirenetworks.org/posts/dev_diary_groups_1/

🔥🔥 Managing your circles on #bonfire is now a breeze. 🌟 Create new #circles effortlessly and organize your users directly from any feed or user profile. Check out the video or experience it firsthand on our campground! 🏕️
https://campground.bonfire.cafe

https://www.loom.com/share/2ed8e21cd8bd47c69b00642878d31573

New Blog Post 📣

Want to take control of your online presence? Check out our latest blog post on using Circles, Boundaries, and Roles in Bonfire! Learn how to create custom #circles, grant specific #roles, and share content with the right people. 🎯

Turn your online interactions into meaningful connections.

🔗 http://bonfirenetworks.org/posts/how_to_boundaries/

For those familiar with SQL, this looks something like (though the real query is much more complex):

```
SELECT * from activities
INNER JOIN (SELECT id from activities WHERE [...] LIMIT 40)
LEFT OUTER JOIN [...]
WHERE EXISTS (SELECT [...] WHERE boundaries.id = activities.id)
LIMIT 20
```

6/end

By deferring the retrieval of complete details and boundary computation until after pagination, the database minimizes the amount of data it needs to process. This significantly improves performance, even when the instance contains a large number of activities. It reduces the time and resources required to handle pagination, resulting in a much faster and more responsive user experience.

5/...

Next, the database takes the results of the optimized query and fetches the complete details of those activities. At this stage, it also computes the boundaries for each of those 40 activities, checking permissions to determine if the user has access to view them. The database filters out any activities that the user is not allowed to see. Finally, another round of pagination is applied to the filtered activities, ensuring that 1 to 20 activities are returned as the final result.

4/...

Here's how it works: First, the app creates an optimized query that loads only the necessary information needed for pagination. This includes filtering activities based on a specific feed, ensuring that only relevant activities are considered. This optimized query is designed to load less data from disk and thus is faster. It returns just the IDs of one or two pages, which could be up to 40 activities.

3/...

To address this challenge, we implemented deferred joins and boundary checking. Instead of fetching all the data and performing boundary checks for every activity before selecting the ones for a specific page, we defer these operations until after an initial pagination has been applied.

2/...

Here are the details copied from that post:

Why the campground had become so slow, and how we fixed that (browsing feeds is now up to 95% faster!):

When you're browsing your feed on Bonfire, each page on the app displays 20 activities, but there are tens of thousands of activities in total. Fetching all the activities at once, including related data like their authors and threads, and checking permissions for each activity can be slow and inefficient.

1/...