hello, I am doing some tests with the Wordpress federation with ActivityPub. It works very well even with Lemmy:
- articles are automatically posted to the Lemmy community if mentioned
- if I reply to a Lemmy account directly on the post, everything works well and my comment is also visible on the blog (example reply from Martufello: https://feddit.it/post/14612919 is also visible on the site: https://www.lealternative.net/2025/02/05/fridgey-unapplicazione-per-la-gestione-degli-ingredienti-in-cucina/)
but
- however, if the user receives a reply, in this case, the reply is given by “testuser,” the latter is not visible in the Wordpress article (in the article, in fact, only Martufello’s first response is present.).
Is it a Lemmy bug?
Thanks.
You must log in or # to comment.
You and db0 are doing different things - he has blog that Lemmy users can interact with as if it was another Lemmy community, whereas you have a blog that you want to use to post articles into a different Lemmy community.
A reply is sent from Lemmy twice - once to the community to Announce out to its followers, and once to the person being replied to. A top-level reply will appear on the WordPress blog because it is a reply to the author. A reply to a reply won’t, because the blog is not following the Lemmy community (so won’t get the Announce), and the author isn’t the person being replied to.
If you want a reply to a reply to also appear on WordPress, you need to treat it like Mastodon, and also Mention the original author. Here is an example that also appeared on the blog: https://lemmy.world/comment/14897939 (the reply from ‘freamon’)
Ok, thanks, the reason is now definitely clear to me.
I was wondering, however, if it might somehow be possible to “bypass” this issue. I have no idea how to do it technically, but I mean something like automatically inserting the author’s tag in certain cases as you did, to make it more practical in terms of usability.
But perhaps, precisely because of the way it is shared, it is not possible to imagine something like that.
I’m not sure, either.
I can imagine, though, that if Lemmy automatically inserted the original post author in replies as a Mention, it would be indistinguishable from when it’s done manually to page another user. So if you made a post as a Lemmy user, every reply in the comment chain would show up in your Notifications.
That looks like a bug on your end. It works for me https://dbzer0.com/blog/this-blog-is-now-federated-natively-to-lemmy/
Thank you very much, this is very interesting. Being both the admin of the WordPress blog and the Lemmy instance, I now need to understand which of the two is having issues.
The ActivityPub plugin seems to work well; I also recently resolved some problems that were solely due to a third-party caching plugin.
I read your article; is it possible to know, if publicly discussable, what changes were made to the plugin that allowed you to resolve the issues? This way, I can compare them with mine and understand what the problem might be.
Thanks!
This bit
Ok perfect, now everything is clear to me then :)
What you did is the actual federation of the site, so every time you create a post you don’t mention a community where it should appear, but it gets federated automatically and displayed within dbzer0 not as a real community but must necessarily be searched for.
What I’m trying to do is slightly different.
Currently, I have the first setting active, that is, only federated authors. An author when posting content can mention a community, in this case
@lealternative@feddit.it, and the post will automatically be posted in that community (which is a real community of feddit.it, in the sense that it is actually present in the list of communities and anyone can write there).For this reason, the bug “persists,” meaning that only the first responses are displayed on the site while the responses to the responses are not.
If instead I change the type of federation and use yours, I can also see the responses.
Ah, this is probably due to you posting as a note, and not as an article. You might need to open a bug report.
