[feat] Announcing replies to have more complete threads #461

New Issue

Open

opened 2023-02-05 16:08:32 +00:00 by ilja · 1 comment

ilja commented

2023-02-05 16:08:32 +00:00

Contributor

The idea

The idea is to make sure instances have (more) complete threads. One way it can be done is to announce replies to other instances we previously send things to in the thread.

Akkoma has a build-in relay. The way it works is that each instance has a relay-actor who announces to it's followers all public posts made on the instance. A similar mechanism can be done here as well.

When a new post comes in, see if it's part of a thread with posts from your own instance, then announce this new post with the same addressing as the other posts in the thread.

It requires some overhead because now every time a reply comes in, you need to check the whole thread, but it's one idea and could be a start.

Maybe the announce doesn't need to come from the relay-actor, but can be done with the actor from whose post you copy the addressing, idk.

The reasoning

Every now and then I see people struggling with the fact that they don't see all posts in a thread because their instance doesn't know about all posts (e.g. https://social.hoga.fr/@manu/109812548712576779).

The work-around for that is to open the thread on a remote instance (e.g. of the OP). But that's an extra step, even more if you also want to interact with one of these posts, and may not always provide a good experience since you never know how the remote instance will act or look like.

Have you searched for this feature request?

I have double-checked and have not found this feature request mentioned anywhere.
This feature is related to the Akkoma backend specifically, and not pleroma-fe.

### The idea The idea is to make sure instances have (more) complete threads. One way it can be done is to announce replies to other instances we previously send things to in the thread. Akkoma has a build-in relay. The way it works is that each instance has a relay-actor who announces to it's followers all public posts made on the instance. A similar mechanism can be done here as well. When a new post comes in, see if it's part of a thread with posts from your own instance, then announce this new post with the same addressing as the other posts in the thread. It requires some overhead because now every time a reply comes in, you need to check the whole thread, but it's one idea and could be a start. Maybe the announce doesn't need to come from the relay-actor, but can be done with the actor from whose post you copy the addressing, idk. ### The reasoning Every now and then I see people struggling with the fact that they don't see all posts in a thread because their instance doesn't know about all posts (e.g. <https://social.hoga.fr/@manu/109812548712576779>). The work-around for that is to open the thread on a remote instance (e.g. of the OP). But that's an extra step, even more if you also want to interact with one of these posts, and may not always provide a good experience since you never know how the remote instance will act or look like. ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [x] This feature is related to the Akkoma backend specifically, and not pleroma-fe.

ilja added the

feature request

label 2023-02-05 16:08:32 +00:00

ilja commented

2023-02-21 19:49:47 +00:00

Author

Contributor

A discussion in chat reminded me of https://www.w3.org/TR/activitypub/#inbox-forwarding

So basically, we don't need to announce, we need to forward it. I'm not aware if any one is currently doing this (are we?), so I'm unsure how to best implement this. Some talk has been done on https://git.pleroma.social/pleroma/pleroma/-/issues/2882, it may be that LD signatures will be needed to do it for non-public scope.

A discussion in chat reminded me of https://www.w3.org/TR/activitypub/#inbox-forwarding So basically, we don't need to announce, we need to forward it. I'm not aware if any one is currently doing this (are we?), so I'm unsure how to best implement this. Some talk has been done on <https://git.pleroma.social/pleroma/pleroma/-/issues/2882>, it may be that LD signatures will be needed to do it for non-public scope.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#461

No description provided.