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...
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)
Our initial design system is on penpot (anyone with a penpot account can comment on it 😊 )
It is not a fully fledged design system yet, we started from the main views and layouts, thinking in particular at how to handle multiple extensions together (eg. social and topics) and including a dashboard to summarize the user digital presence.
It's also a step toward co-designing bonfire in a more partecipatory way - as new features or UX/UI improvements will be first announced over our design system to gather feedbacks, before being implemented.
Thanks! Will surely do. :)
BTW, a #bonfire_feedback: the link to the video is not expanding in site, not even becoming a link... Shouldn't it be?
Thanks again... :D
yeah, a known issue with how content is formatted by the editor 👍
I have a suggestion for Bonfire: my opinion is that the top-left compose space is too busy and overwhelming.
Questions (rather than solutions) - especially for @ivan
- Does the 'Create' button (compose a post / create a topic) need to even exist? The reason I ask is that it might be conceptually easier to add topics after posts/threads exist rather than beforehand.
- Would it be better to move the circles/boundaries indicator (by default 'Public') below the post creation box? In terms of workflow, at least for me I want to know what it is I'm saying before deciding which audience it's for...
In general, and I'd love to talk with you more about this, I think people are going to get quite confused about the difference between (a) posts within topics, and (b) circles/boundaries.
@BonfireBuilders #bonfire_feedback
I'd love to talk with you about that too, we're now refactoring the topic UX and plan to work on boundaries UX as well shortly after, so it's a perfect timing to brainstorm together!
Still on holiday and taking a break from social media in general, but sharing this here as it's relevanito the kinds of conversations that (I believe) @BonfireBuilders are trying to create... dougbelshaw.com/blog/2022/08...
how long can posts on here be
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Etiam id nisl justo. Aenean eu dolor nunc. Donec malesuada quam nec ante pulvinar faucibus. Suspendisse et tortor nec ligula auctor imperdiet ac pretium quam. Maecenas sit amet diam turpis. Cras porta orci sit amet velit fringilla, quis lacinia mi rutrum. Fusce fringilla consectetur justo a vulputate. Etiam varius nibh non magna ultricies tempus. Fusce laoreet tempor augue ac pharetra. Ut et egestas tortor. Aliquam quis rutrum lectus, at mollis magna. Vestibulum elementum pharetra quam, quis venenatis nulla posuere ac. Suspendisse urna magna, ultricies dictum pellentesque sed, pharetra nec mi. Maecenas facilisis quis felis at consectetur. Proin pellentesque sem in nunc dignissim gravida.
Suspendisse porta fermentum tincidunt. Integer ac fermentum felis. Sed varius erat a malesuada lacinia. Donec blandit, elit vel suscipit semper, odio felis vulputate sapien, id blandit est sapien eu risus. Vestibulum et velit sollicitudin, euismod augue non, suscipit erat. Curabitur finibus porttitor pretium. Pellentesque luctus finibus eros quis vulputate. In lobortis, ante eget molestie varius, mi nisi porta enim, in egestas sem lorem in tortor.
Proin maximus neque lectus, ut malesuada magna convallis sed. Donec felis ligula, tincidunt eu auctor in, commodo in nisl. Sed semper neque quis ultrices suscipit. Phasellus scelerisque pretium augue quis tristique. Curabitur a nulla elit. Aenean eu maximus arcu. Integer lobortis suscipit lorem, eu cursus dolor lacinia in. Aenean at accumsan metus. Donec dapibus eleifend imperdiet.
Etiam fermentum, nunc non pulvinar bibendum, enim turpis fermentum libero, et tempus mi felis ac nisl. Sed et arcu sollicitudin nisl sagittis facilisis ac et purus. Fusce a metus a libero pellentesque iaculis quis sed nunc. Suspendisse potenti. Donec sollicitudin nec lorem ac pulvinar. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Nulla vitae eros et est facilisis consectetur.
In ut massa nec nibh gravida maximus. Cras mollis sapien nec ex tempus, non commodo erat blandit. Pellentesque non ex a leo tempus dictum. Nulla facilisi. Vestibulum ultrices metus nisl, id consequat leo feugiat vitae. Morbi semper egestas lorem, eget maximus augue blandit in. Sed mollis eros nibh, vitae consequat tortor suscipit ac. Cras porttitor lorem vitae elementum rhoncus.
atm there isn't a limit on the length of a post. This can very well be a configuration that we can add later, where each instance can set their own max length.
I've just ordered "novacene" by lovelock, I feel I really need a non dystopian narrative on how technology can help us navigate the climate change
I can see it...
But what if we include the possibility to add roles to users for threads? Eg. the thread moderator, the thread merger (which is responsible of cleaning the thread tree by merging together similar answers together), thread taxonomer (who is responsible of putting threads in their relevant topics), and so on
I guess somehow is about exploring the interconnections between social gardening , social networks and forums :)
uhm I feel i was more confused than before, let see if some more coffee helps 😅 😅 😅
Feature request: being able to redact, not delete, arbitrary posts (according to the post boundary) to preserve the tree structure @BonfireBuilders #bonfire_feedback +bonfire
Feature request: arbitrary, federated vote to allow complex, online decision making, and prevent topics takeovers by rogue admins @BonfireBuilders #bonfire_feedback
on this regard, we had some initial chats with @douginamug about porting #ukuvota ( ukuvota.world/#/ ) as a bonfire extension, as we used and liked it quite a lot...
more about systemic consensus: en.wikipedia.org/wiki/System...
Also more here: notes.zo.team/fediverse-soci...
TW self-harm, don't read this if you have mental health problems
@BonfireBuilders feature request, infinite scroll
we plan to add a configuration to switch between infinite scroll and load more button.
(Infinite scrolling is often considered a dark pattern, so it would be good to offer it as a conscious choice...)
it is a mockup we did for an alternative topic page in bonfire