Original title: Separate Notices Made in Reply from General Notices
Like what Twitter and Mastodon do--- it separates conversation from the actual microblogs. That way when interacting with people it doesn't bury or "push down" statuses.
I notice Pleroma doesn't do this either, so I wonder what the mindset is behind having everything under one timeline.
Original title: Separate Notices Made in Reply from General Notices
Like what Twitter and Mastodon do--- it separates conversation from the actual microblogs. That way when interacting with people it doesn't bury or "push down" statuses.
I notice Pleroma doesn't do this either, so I wonder what the mindset is behind having everything under one timeline.
I've talked with @tenma who knows both twitter and mastodon better than I do.
I'll try to expose our understanding of your request and the changes we are considering to improve this.
By default (no JS):
In the timeline, only show notes that aren't replies and their direct replies of actors the logged person has subscribed to.
For full conversation, require explicit click in the Coversation link and redirect to the conversation's page.
If no person is logged, in instance's public timelines, show every direct reply of local actors to non-reply notes.
With JS:
Same behaviour but, clicking the Conversation link would trigger a JS modal in the same page instead (twitter like).
Let me know what you think.
Hi @licho, thanks for bringing this up.
I've talked with @tenma who knows both twitter and mastodon better than I do.
I'll try to expose our understanding of your request and the changes we are considering to improve this.
**By default (no JS):**
>In the timeline, only show notes that aren't replies and their **direct** replies of actors the logged person has subscribed to.
>For full conversation, require explicit click in the `Coversation` link and redirect to the conversation's page.
If no person is logged, in instance's public timelines, show every direct reply of local actors to non-reply notes.
**With JS:**
>Same behaviour but, clicking the `Conversation` link would trigger a JS modal in the same page instead (twitter like).
Let me know what you think.
<lnxw37d4> I’m not a fan of that way, Diogo. I want to see both original posts and replies without additional effort. We aren’t Twitter, where everyone is shouting at once. Conversations are fundamental.
<lnxw37d4> Twitter lost most of its usefulness to me when they switched to hiding replies.
<rozzin> OMG.
<rozzin> That's why I quit twitter.
<rozzin> That's *the* reason: the presentation of conversations was unusable.
<rozzin> People actually *like* that?
<rozzin> We also *already have* timelines dedicated to "only things I wrote" (/profile) and "only replies" (/replies).....
<rozzin> diogo: does ConversationTree work in your branch? That's one of the things that I'd *really* like to get back....
<rozzin> lnxw37d4: I didn't know that twitter even *ever had* a unified timeline, though--I guess that must have been either a *very* long time ago, or only appeared briefly after I gave up on it?
<rozzin> lnxw37d4: actually, I had figured early on that they just didn't even have the datastructures to support it--they didn't seem to be actually tracking what was a reply to what; and even if they were tracking it internally, when I got there the UI discouraged people from generating those datastructures.
<rozzin> lnxw37d4: now I'm actually sort-of wondering if the reason twitter went with the "decontextualize everything!" approach might have actually been to help drive all of those massive shitstorms that twitter is know for....
<rozzin> lnxw37d4: because "it's the quantity of people talking that matters, not the quality"
I believe the raised points are very valid.
Feedback from IRC:
<lnxw37d4> I’m not a fan of that way, Diogo. I want to see both original posts and replies without additional effort. We aren’t Twitter, where everyone is shouting at once. Conversations are fundamental.
<lnxw37d4> Twitter lost most of its usefulness to me when they switched to hiding replies.
<rozzin> OMG.
<rozzin> That's why I quit twitter.
<rozzin> That's *the* reason: the presentation of conversations was unusable.
<rozzin> People actually *like* that?
<rozzin> We also *already have* timelines dedicated to "only things I wrote" (/profile) and "only replies" (/replies).....
<rozzin> diogo: does ConversationTree work in your branch? That's one of the things that I'd *really* like to get back....
<rozzin> lnxw37d4: I didn't know that twitter even *ever had* a unified timeline, though--I guess that must have been either a *very* long time ago, or only appeared briefly after I gave up on it?
<rozzin> lnxw37d4: actually, I had figured early on that they just didn't even have the datastructures to support it--they didn't seem to be actually tracking what was a reply to what; and even if they were tracking it internally, when I got there the UI discouraged people from generating those datastructures.
<rozzin> lnxw37d4: now I'm actually sort-of wondering if the reason twitter went with the "decontextualize everything!" approach might have actually been to help drive all of those massive shitstorms that twitter is know for....
<rozzin> lnxw37d4: because "it's the quantity of people talking that matters, not the quality"
I believe the raised points are very valid.
Hi, if it could work without JS that would be nice.
I don't sympathize with the 'conversation mindset'.
A large majority of cases re: conversation, I'd have to go off-instance and read the thread on another because a partial amount of conversation is available locally.
[this also means I can not respond or interact with certain replies]
This idea is for profile only. Very easily conversation can fill the entire page for heated discussions.
Meaning if soemone goes to my profile to see what kind of person I am, they'd be seeing a lot of specific context required conversation that may or may not be available locally.
Hi, if it could work without JS that would be nice.
I don't sympathize with the 'conversation mindset'.
1. A large majority of cases re: conversation, I'd have to go off-instance and read the thread on another because a partial amount of conversation is available locally.
[this also means I can not respond or interact with certain replies]
For example, this thread:
https://gnusocial.no/conversation/4689800#notice-5385119
vs
https://qoto.org/@freemo/102361717923471724
2. This idea is for profile only. Very easily conversation can fill the entire page for heated discussions.
Meaning if soemone goes to my profile to see what kind of person I am, they'd be seeing a lot of specific context required conversation that may or may not be available locally.
Also I tried /profile
and it doesn't work.
https://gnusocial.no/licho/profile
=> page not found
Original title: Separate Notices Made in Reply from General Notices
Like what Twitter and Mastodon do--- it separates conversation from the actual microblogs. That way when interacting with people it doesn't bury or "push down" statuses.
I notice Pleroma doesn't do this either, so I wonder what the mindset is behind having everything under one timeline.
Hi @licho, thanks for bringing this up.
I've talked with @tenma who knows both twitter and mastodon better than I do.
I'll try to expose our understanding of your request and the changes we are considering to improve this.
By default (no JS):
If no person is logged, in instance's public timelines, show every direct reply of local actors to non-reply notes.
With JS:
Let me know what you think.
Feedback from IRC:
I believe the raised points are very valid.
Hi, if it could work without JS that would be nice.
I don't sympathize with the 'conversation mindset'.
[this also means I can not respond or interact with certain replies]
For example, this thread: https://gnusocial.no/conversation/4689800#notice-5385119 vs https://qoto.org/@freemo/102361717923471724
Meaning if soemone goes to my profile to see what kind of person I am, they'd be seeing a lot of specific context required conversation that may or may not be available locally.
Also I tried /profile
and it doesn't work. https://gnusocial.no/licho/profile => page not found