Loading...
i'm excited 😍 we finally seems to have reached a new phase in bonfire development - where we're start working and discussing more subtle improvements or specific UX cases - while relying on a strong foundation. Lot of room for improvements, but we're getting there, thanks for partecipating in it 😍
Thanks, it's because of a wrong url generated when the task is created - fixing now
Which set is currently used in the UI?
for the extensions icon (the ones on the left sidebar) we're currently using the noto pack: icon-sets.iconify.design/noto/
"Reality is not a collection of things, it’s a network of processes."
https://www.theguardian.com/books/2022/sep/05/the-big-idea-why-relationships-are-the-key-to-existence
it resonates to me with the theory promoted among others by lynn margulis, about stop considering living beings as individual - but as symbionts hup.harvard.edu/catalog.php?...
done: notes.zo.team/DyZVcgBXS6ip_Q... 😘
The coordination app is the first of many that's based on the valueflo.ws vocabulary for economic cooperation. We're also planning to interoperate with the various forge federation projects for using it as an issue tracker for FOSS projects.
we also have a offers/needs extension in progress 😀
Dues It looks to you like Bonfire can present something for this grants? https://www.standict.eu/standicteu-2023-8th-open-call
A brief reading tells me yes, but I'm not an expert at all...
seems more focused on protocol development rather than platforms tough?
I have a suggestion for Bonfire: press CTRL-Enter to send post. This is usual behaviour on other social networks, etc.
@BonfireBuilders #bonfire_feedback
sure, it is already noted down here: github.com/bonfire-networks/...
ivan
boosted
Erving Goffman's "Asylum" is an excellent reading on how not to implement a social media : the capitalistic ones are designed to turn into total institutions for their socially isolated users. I won't mince words to please do-gooders, cutting millions of people's time schedules to the bone of meals and 5 hours of sleep per night, lifting social activities, studies, work, and family life, is a crime against humanity.
Oomph I can imagine how difficult that is in a federated setting.! Maybe a balance can be found that just gives a rough sense of the "context size" of a post instead of being very exact about the whole thread metadata?
or alternatively we can leave the feed as it is, but showing more context when the user click on the reply icon.
Rather than just showing the replied to post above the composer box, we can show a more contexted set of information related to the thread (We can merge the read discussion and the reply icon together, so that when you click on the reply icon it shows the thread and load the position where you want to reply to ?)
Exciting! That links 404s for me though....
New link: design.penpot.app/#/view/a90...
+User_Experience
We've started working on #coordination app - a simple task tracker extension.
Here some first mockups: design.penpot.app/#/view/a90...
I have a suggestion for Bonfire:
@BonfireBuilders #bonfire_feedback
Bonfire does a lot of great things with single posts:
- show them in a "timeline" view as they occur
- according to who I follow
- according to what topics I follow
- according to the instance I'm on
- personal messages
- show them in a threaded view highlighting semantic connections
- according to filters, such as searches for tags, or taking into account blocked users
It is everything that you'd want, but also a bit much. In particular, after seeing the threaded view once, I'm always having the impression that I am missing something when looking at a post. Bonfire allows for quite a rich context for every post, but most views present single posts. They might be parts of threads that I haven't visited before and therefore might misinterpret. I have to click on every post to see it in thread view to understand if I'm indeed missing something.
It would be great if each post would feature some information about its context. For instance, it could show a mini-map of the thread, or display metadata like "part of a conversation started 2022-09-19, 4 participaring users, 34 messages (3 unread)"
If threads were more of a basic unit users would interact with (rather than single posts), it could also be possible to mute a thread. For instance when all your friends start to talk about some sporting event that you're not interested in or whatever.
Things like that could encourage better discussions, as in slower, less repetitive, more interaction with other thread participants.
this makes a lot of sense, especially since our thread UX is not the flat standard one, when a user replies from the timeline, they don't know in which layer of the tree they're replying to.
There is always a balance to find between overwhelming the feed showing too much info per single post and not giving enough context to the user (as it is now in bonfire and most of the social networks i'm aware of)
