hi @db0@lemmy.dbzer0.com,

I don’t know if you ever noticed, but I also reported this strange behavior on GitHub.

If I activate Bot author and blog profiles, the posts are automatically and correctly visible here: https://feddit.it/c/lealternative.net@www.lealternative.net

However, if a person on Mastodon searches for the article’s URL and comments on it… their comment will be visible on WordPress but will not be visible on that page on Lemmy.

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.

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.

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!

Found out just now what the problem was.

I am writing this to help others: the federation was active in that instance but it was also marked as a private instance. This gave no problems in using it until the update (probably because it is restarted and re-run Docker).

I removed the federation from the config file leaving only the private instance and it restarted immediately.

yes, actually i tried ‘none’, ‘tls’ and ‘starttls’ but with no success. I tried with external SMTP because the default created by ansible does not work:

  email: {
    smtp_server: "postfix:25"
    smtp_from_address: "noreply@mydomain.it"
    tls_type: "none"
  }

It is the same thing that I thought. Unfortunately, if I try to manually force the port by writing smtps.aruba.it:465 as I said the server freezes for several minutes, goes to 504 and does not send any email.

So I can not understand if the port must be entered in another way (?) or if I have to install something on the server first to be able to send an email through an external SMTP as in this case?