You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug with a clear and concise description of what the bug is.
GoToSocial is able to see Lemmy posts, boost them and reply to them, and the replies and boosts will federate to Mastodon followers, but the replies don't seem to federate back to Lemmy.
What's your GoToSocial Version?
0.7.0rc1
GoToSocial Arch
amd64 docker
Browser version
No response
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered:
tsmethurst
changed the title
Replies to Lemmy posts don't show up on Lemmy instance
[bug/federation] Replies to Lemmy posts don't show up on Lemmy instance
Feb 10, 2023
That would explain it. It also means Lemmy would already have issue federating with people on certain Mastodon instances if those run in "secure mode", i.e have https://docs.joinmastodon.org/admin/config/#authorized_fetch enabled. Pleroma has a similar setting as do most other implementations, though it's not enabled by default.
I suspect that's likely to change over time though so the longer it goes unimplemented in Lemmy the more federation issues users will experience. There are a couple of Rust crates available that implement HTTP signatures so hopefully the Lemmy devs wouldn't have to do this from scratch.
Describe the bug with a clear and concise description of what the bug is.
GoToSocial is able to see Lemmy posts, boost them and reply to them, and the replies and boosts will federate to Mastodon followers, but the replies don't seem to federate back to Lemmy.
What's your GoToSocial Version?
0.7.0rc1
GoToSocial Arch
amd64 docker
Browser version
No response
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: