Mastodon not federating to Lemmy?

I’m not sure if this is the wrong place to post this; my apologies if it’s not.

Anyway, I have an inquiry about Mastodon replies seeming to not post to show up on Lemmy.

Earlier today I made a post on Mastodon and made it post to Lemmy as well, by @ing the community I wanted it to appear in. Here’s a link to the post on Mastodon, and here’s how it showed up on Lemmy. At first, everything seemed to work fine.

But something I noticed is that, though the Lemmy comments were visible to me on Mastodon, the reverse was not true: most of the Mastodon replies were not visible on Lemmy. So there seems to have been some federation issues there.

So my question is, does anyone know what caused this and if so how I can fix it?

It's pretty inconsistent, depends on what the people running the site are doing. Seems like the Palestine comm and other stuff that is really consistently popular on both sides for years is what works reliably. Plus it depends on Mastodon fork. Misskey would have no problem federating with Lemmy if not for one tiny bug, but the forks like Sharkey and Iceshrimp already solved that. It's just that nobody except for me and like 37 other people know they exist.

You mentioned K/Mbin and I honestly find it a bit distasteful, as representing what should really be the same kind of post-reply format (the retweet accounts represent comms or rss feeds etc perfectly, I even use them for scraping imageboards and Telegram, these sites may have different UI but they're almost the same format) in a whole separate thing just feels really clunky and the magazines are weird—sorry if that makes you mad because it really fits your workflow. Wish there was just more basic consistency between the platforms since users could share information regardless of whether they have Twitter or Reddit brain

Mainly I wish stuff like a.gup .pe worked better *lmao this already shut down nevermind RIP it was basically a platform-agnostic way to create groups similar to lemmy's communities, and they appeared on here that way

If you use Misskey or whatever it calls itself now, it works well with Mastodon and okay with Lemmy.

> @a_gee_dizzle@lemmy.ca said in Mastodon not federating to Lemmy?:
>
> So my question is, does anyone know what caused this and if so how I can fix it?

Mastodon doesn't know to send replies to the community for distribution to the rest of the threadiverse.

Long story short if you're not on the same instance as the community, Mastodon replies to you won't make it to the rest of the threadiverse.

I experimented with a hack to see if I could fix this. NodeBB works around this by including a hidden mention to the community that Mastodon will then pre-fill in the text box, and then the reply will make it in successfully. If you have a Mastodon account try to reply to this comment, the community will be pre-filled as a mention.

Piefed, Lemmy, and Mbin will need to do this.

Does it work? Yes

Are we supposed do it? Technically no, it's easier to blame Mastodon for not doing it right.

Should we do it? Probably, yes.

@rimu@piefed.social @nutomic@lemmy.ml @bentigorlich@gehirneimer.de @melroy@mastodon.melroy.org I tested this. It works perfectly fine. We can implement this today and remove it when Mastodon supports threadiverse conversations better (I'll try to make that happen.)

Sounds good to me!

Unless the person replying on Mastodon removes it of course (to save themselves some characters and because they don't recognise it).

There doesn't seem any functional difference between your comment (which implicitly Mentions the community), and the original post on thecanadian.social (which explicitly Mentions it). Screenies from activitypub.academy show that replies to both include both Mentions pre-filled.

https://thecanadian.social/@mike/116234121499688717 didn't remove the Mention, and so the comment made it to Lemmy. https://mstdn.ca/@cass_m/116234270845317774 did remove the Mention, and so it didn't.

Specifically for Lemmy btw, the reply at https://mstdn.ca/@cass_m/116234270845317774 demonstrates another problem - that instance requires a signed GET request for its actors, which hasn't been fully implemented AFAIK.

Afaik it's fixed now

The federating issues were solved iirc

@julian @a_gee_dizzle @rimu @nutomic @BentiGorlich @melroy I’m replying from mastodon, don’t you see it ?

Good idea, adding this to Lemmy.

Add hack to improve Mastodon federation by Nutomic · Pull Request #6409 · LemmyNet/lemmy

🐀 A decentralised discussion platform for communities. - Add hack to improve Mastodon federation by Nutomic · Pull Request #6409 · LemmyNet/lemmy

GitHub (github.com)

@nutomic @julian oh wow thats great to hear. Gotta love a hack

though the Lemmy comments were visible to me on Mastodon, the reverse was not true: most of the Mastodon replies were not visible on Lemmy.

Yeah... That's a common federation issue. I haven't properly investigated but a hypothesis might be that the account that commented are on instances not federating with the Lemmy instance.

Here a community for you to do more test : !testfediverse@jlai.lu

Long story short if you’re not on the same instance as the community, Mastodon replies to you won’t make it to the rest of the threadiverse.

Oh... That explains a lot of. Thank you for sharing the cause and the solution (^_^)

Did you receive my email from last Thursday? Seems there might be some delivery problem.

Here a community for you to do more test : !testfediverse@jlai.lu

This is a useful too, thank you

I see it

I tested this. It works perfectly fine. We can implement this today and remove it when Mastodon supports threadiverse conversations better (I’ll try to make that happen.)

Wow that’s a really proactive response, thank you! Please keep me posted on how it goes

About batched votes? Yeah I did, just haven't responded yet