Conversation
Notices
-
!gnusocial shouldn't it be possible (with low overhead), to display all dents (even of ppl whom I don't follow), within the conversation view?
-
@marcus Been asked already many times: This requires #parent-retrival.
-
What exactly is that?
-
@marcus It is about fetching the parent dent (where you have replied to for example) which causes more load on servers.
-
You'll have to import those notices to your instance. The question is:
1. Do you really want to import all notices?
2. Do you want it to be done before reading the conversation - or on demand?
3. What if the conversation is horribly spammed by one or many individuals you actually want to ignore?
4. Etc. etc.
Bottom line: It requires a procedure for reliably, and trustworthily import remote notices. We don't have that now.
-
@marcus But: if the dents have been locally fetched already because someone else follows the rest of the people (you don't follow) then it might be possible. Or @mmn? What are your thoughts?
-
Oh and should the conversation continue filling up after you've read it once? If people continue posting to it. And in that case, assuming you've paid interest in it by posting to it, should it even - despite you're not subscribing - show up in your feed as a new post?
There are many questions and many possible implementation methods. It'd require a good standardisation committee to come up with a reasonable default behaviour without people becoming too angry ;)
-
Sounds like a good idea to me.
-
@mmn @marcus Possibly this format: /conversation/xxxxx/all for whole (even read) conversation and /conversation/xxxxx/latest for only latest dents? So people can choose whether they want to see dents from only followed, all or only latest.
-
@mmn Wow, importing a conversation on demand is a very intersting idea. I’ve never thought of that.
-
I would link '...xxx minutes ago...' to the latest dents and re-add a 'conversation' link which would display the whole story.