-
-
Notifications
You must be signed in to change notification settings - Fork 918
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Federate content of a searched post or comment #5554
Comments
lemmy-ui changed comment links to include the post id. The old links ( Edit: The fedilink (next to comment direct link) still has the old format. |
I'm not sure I know what you mean by "next to comment direct link" as I only see the one link, but searching for Edit: I have updated the report yo include that format as well. Edit2: Found what you meant by Fedilink, but it too fails (same format as updated report). |
@matc-pub Actually, that part may be a bug.
For instance, if I search a post that was made on I wonder if the local server doesn't think a parent exists because of the mismatch in host, even though that's valid. |
Annnnd that may have been a one-off federation issue. Using the fedilink works every other time. Ugh, inconsistencies will be the death of me. I am updating the above feature request to focus only on federating the content once a user has interacted. |
Requirements
Is your proposal related to a problem?
Assumptions:
Action: Search post
https://other.instance/post/1234
Describe the solution you'd like.
When searching for a post on another instance, that post should begin federating and backfill content. Preferably new content specific to that post would also federate if a user on the local instance interacts with it (comment/vote/save).
Describe alternatives you've considered.
Searching every individual comment fedilink, which is not really feasible.
Additional context
Apologies if this has come up before, I swear I saw something similar but less detailed a loooong time ago, but could not find it anywhere. I also don't think it was exactly this.
The text was updated successfully, but these errors were encountered: