-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatability with AP-enabled Wordpress blogs #567
Comments
I'm looking into it. It seems the webfinger entry for the user |
This issue, related to Plume's URL schema retrieval by webfinger may be of some help in sheding light on the issue in general, even if it's not specifically Wordpress related: |
The two issues are different and unrelated, but I'll try to push fixes for both by the end of the day |
Oh... good to know, sorry :-) |
Hey I am the developer of the ActivityPub plugin (https://wordpress.org/plugins/activitypub/) for WordPress. I just tested my implementation with plume and it seems to detect the profile, but my blog does not receive a follow request. |
Hey there, Plume team!
I'm currently trying out your software on a public instance (fediverse.blog), and was interested in the possibility of subscribing to my ActivityPub-enabled Wordpress blog, which is made possible by Pterotype. For context, I run a site called WeDistribute.org, which talks about fediverse projects. Currently, a few types of platforms are capable of subscribing to it:
I think, in the long term, it could be very crucial for ActivityPub-enabled blogging platforms to be capable of federating with one another. Currently, I am unable to follow my Wordpress blog from Plume. Attempting to navigate to ether
https://fediverse.blog/@/blog@wedistribute.org
orhttps://fediverse.blog/~/blog@wedistribute.org
does not appear to bear fruit yet.My question to you is, what would it take to make cross-federation with Plume possible? How might separate ActivityPub-enabled article platforms work to ensure compatability with each other?
The text was updated successfully, but these errors were encountered: