@lemmy_support Why do only SOME updates reach Lemmy from Mastodon?
I posted to Lemmy from Mastodon: https://lemmy.ml/post/49566110
A Lemmy user’s comment on that post reached me on Mastodon. I replied from Mastodon & my reply showed up on Lemmy, as hoped.
https://lemmy.ml/post/49566110/26507040
Later, I tried to reply from Mastodon to other Lemmy comments on the same post. Why didn’t these replies reach Lemmy? https://mastodon.social/@modem/_down/116907072443986550
If the update showed after you pinged/mentioned the .ml community, I would suspect that it’s the mention that reinforced the missing federation.
@db0 You mean that pinging a user from the target Lemmy instance might force that instance to pull in intermediate messages from the same thread? Yes, that could be a factor.
Still doesn’t explain why my reply to Grendel didn’t reach Lemmy.ml, though.
I’m not pinging anyone from Lemmy.ml this time, so see what happens.
Also, you didn’t just ping just any user. You pinged the community handle.
@db0 but the following replies that I sent from Mastodon did NOT ping the community handle, yet still reached Lemmy.ml:
- My first reply to you in this thread.
- My reply to @gary_host_laptop on my original “can you see this message?” thread.
There’s some apub unseen metadata which is not visible to us which might cause any of these. I can’t investigate it though, I just know that while federation is working, it’s notoriously flakey between the two apub services.
@db0 do you have a GitHub account?
If so, would you mind opening an issue there, asking the Lemmy devs to take a look at this thread so investigate why my reply to Grendel didn’t reach lemmy.ml even though it should have done. Thank you again.
It does seem like there must have been some kind of federation bug involved.
I’m afraid that’s entirely more effort than I’m willing to do atm.