[feat] Announcing replies to have more complete threads #461
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#461
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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?
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.