this post was submitted on 25 Apr 2022
1 points (100.0% liked)

Fediverse Futures

982 readers
1 users here now

Social Media Reimagined

This is a companion to Fediverse Futures on Social Coding to elaborate the Fediverse from high-level, non-technical perspectives, brainstorming our visions and dreams.

We need a more holistic approach to fedi development and evolution. We need product designers, graphics artists, UX / UI / Interaction designers, futurists and visionaries to join the dev folks. Everyone is encouraged to join here and enrich our views on what Fediverse can be with diverse and different viewpoints, and to stimulate brainstorming, creativity, thinking out-of-the-box and crazy, wild ideas.

Some guidelines

Please read the Social Coding Community Participation Guidelines for more information.

Our fedi hashtags

#Peopleverse #FediverseFutures #Web0 #SocialNetworkingReimagined #UnitedInDiversity #Fedivolution2022 #SocialCoding #ActivityPub

founded 3 years ago
MODERATORS
 

I recently started thinking again about the Social knowledge fabrics discussion, and it seems to me that one of the biggest obstacles for fedi to become one is the following. The things we refer to as "threads" are actually "branches of a tree". You have a trunk, basically the whole fedi, each post is a branch, each branch can itself ramify into branches, but all the branches stay independent.

It would be useful if a discussion branch was not only shaped like a thread, but also had the usefulness of one : sewing, or tying together different discussion topics. Sometimes I think again about an old discussion when participating in a new one, and so I cite it. But this message is still fundamentally part of the new discussion, while the newly established link should be of equal interest to participants of both threads.

What we miss is for that message to be part of both conversations, or a clear way to automatically signify to both threads that something new happens. Of course, this can be done by hand, writing a comment in each cited branch to point to the new one. But we won't remeber to do that everytime, or we will not want to "necrobump", or we just don't want to make the extra effort. So it would be interesting if the relations were established automatically. For example the way I proposed for Friendica's quote-shares in the linked URL, or the way GitHub handles issue that cite each other.

Maybe two old topics will come to know about each other that way, effectively being sewed by the new thread.

you are viewing a single comment's thread
view the rest of the comments
[–] GrassrootsReview@lemmy.ml 2 points 2 years ago* (last edited 2 years ago) (2 children)

Next to inviting citations, it would also be nice for everyone to be able to add citations. Make it more of a collaborative effort than someone's time line.

Would it need a way to make clear we are really interested in the citation? I feel that most cases people ask for citations, they mean to say diplomatically that the claim is nonsense.

[–] humanetech@lemmy.ml 1 points 2 years ago

Yes, you are right. My example served purely to present a use case where richer semantics might make sense in a microblogging context. In an actual app you'd model the domain first and drill down to concrete vocabulary formats from there.

[–] liwott@nerdica.net 1 points 2 years ago

Would it need a way to make clear we are really interested in the citation? I feel that most cases people ask for citations, they mean to say diplomatically that the claim is nonsense.

The problem is that if such tool comes to exisyence, the people who want to politely say bullshit will use that one out of politeness