#Fediverse does this happen often to you too?
You found a great post, commented to it, only to find out later that a broad discussion was triggered ... but not on the thread branch you commented on.
So if you didn't bump into it coincidentally you'd be totally unaware of that.
I'd like a Watch Post feature that sends me notification of all activity on the thread.
Would you like to have a Watch feature?
@tinyrabbit I can see why you would want that, & I'm sure I'm not going to say anything you haven't thought of already, but my thinking is this.
Suppose there's already a single thread, not too long, easy to read perhaps 10 or 20 toots. But one of the toots in the middle is something to which I'd like to reply. The existing system allows me to do that, whereas having a single thread would force me to tag my comment on the end, even though I'm replying to something further up.
@tinyrabbit My wish is to be able to reply to multiple toots, thus drawing a sprawling conversation back together. Then, additionally, have the ability to render the discussions as graphs, like this:
I've written a discussion system that lets you do that. It's currently find for small numbers of users, and extremely helpful, but pig-ugly, and very parochial.
@ColinTheMathmo @humanetech To me this sort of discussion tree looks quite horrible 😆 I can't imagine the effort it takes to follow that discussion in all its branches, or how frustrated I would be to see virtually the same discussion taking place along a number of different paths. To me it looks like a great way to *socialize*, but a horribly inefficient way to *discuss*.
> To me it looks like a great way to *socialize*, but a horribly inefficient way to *discuss*.
If you refer to #fediverse ( #pleroma, #mastodon et al) then I fully agree with you here. And it is very frustrating to see how much good information is lost in unobserved branches that immediately sink into history to be forgotten about.
@humanetech @ColinTheMathmo It's in the nature of social media to have low information density and short cycles, though. It's an ephemeral medium (and I don't really think we should hold on to posts forever).
I've never understood why people try to use facebook (even facebook groups) or twitter for serious discussions. Each to their own, I guess, but it doesn't work well for me.
If it's for long-term policy discussions I definitely want that in a discussion forum, mailing list or issue tracker where it should exist for a decade or more. Mastodon I haven't decided about. It's in our power to retain discussions forever but it's not a norm and it's much harder to resolve retention policy on any piece of content than when dealing even with a corporation.
The poll however is about knowing where the action is so valuation comes down to how efficient the fedi should be about drawing attention to the best content (however each user defines best). I'd like it to be efficient without being game-able.
It is a bit of an issue with microblogging. I've sent numerous "Attention [this and that], contribute to the discussion [here]" with a link to a forum, or lemmy. But hardly anyone does that really. You get good discussion.. as toots, not where you want to have them.
Ppl have an interest to participate, but the external location just adds too much friction. So I end up putting a link to the toot in the forum post. But then people on the forum don't read that.
@humanetech What I've done in the past is to have the discussion spread over several platforms, but then aggregate it "by hand" into DiscDAG. Sometimes people have migrated and had the discussion there directly, others have continued tooting, tweeting, and posting elsewhere, and I've continued to add those under their name to the DiscDAG discussion.That has resulted in a really useful resource.
It's been work for me, but I've been slowly automating it to reduce the work.
@humanetech Different people want different things and think in different ways. For example, @tinyrabbit thinks the "One True Way" for discussions is the purely linear forum (PLF), but I think the "One True Way" for discussions is the "Branch and Converge" DiGraph.
I can't cope with the PLF, but I appreciate that others will prefer that.
I have ideas, but not the skillz.
@humanetech I appreciate that you have reasons for suggesting that, but it's yet another platform (YAP), and the mere idea of trying to become familiar on YAP just makes me feel tired all over.
I'm backing off and asking: What are you/we trying to achieve?
There's already large amounts of discussion out there, spread over multiple platforms with varying levels of visibility and accessibility. I can't help but feel that there's got to be a better way to make progress.
In this case Lemmy is also a (rather new) federated platform. They just released a new version and will be extending the federation support. Interoperability with Mastodon, Pleroma and other microblogging apps is something that is likely to be added in some way or other.
Lemmy is also an example where stuff comes together. The communities you see on the server, may exist in entirely different servers, yet still can you interact with them, be a member and chat
@weex I'm doing that by hand. When I hit "Reply" here, several IDs are inserted at the head of the toot, even though I'm actually replying to you. So I leave your name at the top, and move the others mentioned to the bottom, preceded by the CC to make it clear that I'm replying to you, although others have previously been involved.
Using CC is nice for clarification, but not needed. The implicit rules are:
- When the mentions are at the top I reply explicitly to the first one
- When there's one at the top and the others below, then these are CC'ed
I sometimes use CC myself, but then to 'drag' some new person into the discussion, i.e. to make them aware of interesting stuff.
@humanetech It might not be necessary, but I find the existing convention of having all the IDs at the top is something that's constantly nagging at me, sucking attention, and creating work. It's like a stone in my shoe ... I can walk with it, but it's a constant low-level annoyance.
But I can't make other people work in a way that's convenient for me, so I just have to put up with it.
Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.