This blog is now federated natively to lemmy

db0

@[email protected] @[email protected] I love to see the native interaction between lemmy, mastodon and wordpress from any of those platforms!

Draconic NEO

Greetings from Lemmy, great to hear that this is now working. This is only a suggestion but maybe you might consider changing the icon of the blog to something a bit more personal than the wordpress icon.

Draconic NEO

@[email protected] Is this federating to your blog?

Edit: Seems like it is now.

Db0

Yep, I can see it fine.

Draconic NEO

@[email protected] Awesome, it didn’t federate at first until I mentioned you, then both the comment and the reply I mentioned you in federated just fine.

poVoq

So, which setting was it that made this work?

[email protected]

IDK why but I can’t see other comments from my instance.

Db0

Check the github issue I linked. I’ve posted a screenshot there

Db0

I need to approve new commenters on the blog which is an anti spam measure, so that might be why. I think I’ll disable that setting and see if it’s still an issue

Db0

If it’d not using lemmy 0.19.6 then WordPress federation is not working well yet

shnizmuffin

This is super cool.

Unfortunately the previous posts on this blog are not retrieved automatically, so you won’t be able to see them or their comments in the community, but one can search for a blog url in lemmy and it will discover it and open it for comments.

I don’t think previous comments are retrieved automatically either. From my instance, comments are empty.

Db0

Yes the comments are the same. Unless you were subscribed to the blog via lemmy when the comment was left, you wouldn’t receive it and fetching it later doesn’t retrieve earlier comments.

[email protected]

Just because I’m curious, which one was the setting in the plugin that made it work natively with lemmy?

Db0

[Bug]: dbzer0.com wordpress blog not being fetched · Issue #5147 · LemmyNet/lemmy

Requirements Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support Did you check to see if this issue already exists? Is this only a single bug? Do not put multiple bugs in one issue. Do you agree to fol...

GitHub (github.com)