wordpress-activitypub

wordpress-activitypub copied to clipboard

Hey all,

I've been using Pterotype for one of my sites for some time. While it works pretty well, unfortunately the project has fallen into an unmaintained status, with no conceivable updates happening anytime soon.

Given that my blog (wedistribute.org) has a pretty sizable following across the fediverse, I was wondering whether there was anything that could be done to migrate the data being used by the Pterotype plugin to instead be used by wordpress-activitypub. Aside from the manual process of moving data from one place to another, what kind of considerations would need to be made? How different are the database schemas between Pterotype, and this one?

Please let me know!

Oh: https://github.com/pterotype-project/pterotype/issues/18#issuecomment-561010105

I will have a look how much work it is... But my plugin is very light weight and does work witch most of the WP Core data. I think the only thing that has to be migrated is the followers list.

@DeadSuperHero can you tell me how much followers you have?

Hey @pfefferle , thanks for getting back to me!

can you tell me how much followers you have?

If this endpoint is any accurate indication, it appears that there are approximately 569 followers as of right now.

Won't the most difficult thing be keeping the actor ID, which currently is https://wedistribute.org/wp-json/pterotype/v1/actor/-blog ? Because if that changes, all implementations will see it as a new actor anyway :thinking:

@jaywink good point... I think using an API endpoint as profile page is generally problematic... I will think about how to work around that "problem"... Perhaps providing the endpoint and redirect to the profile page if the accept header is something html.

Just wanted to ping on this, as we have a rising spam problem stemming from Pterotype. Are there any thoughts on how the data could actually be migrated from one plugin to the other?

I suspect I might have to manually pull MySQL tables/rows from the db and somehow move them over to the other respective plugin, but I'm not totally sure on what the process even is right now.

Would resolving issue #43 fix this? That should allow @DeadSuperHero to continue using @[email protected] scheme employed by pterotype, if I'm understanding this correctly.

Perhaps @jdormit can offer some guidance (If you read this: Thank You for Creating Pterotype)!

Theoretically, yes, but the existing articles would need to retain attribution to the original actor object, and said actor would also need to retain its follower collection from before the transition.

On Sun, Mar 15, 2020, 9:38 PM sunjam [email protected] wrote:

Would resolving issue #43 https://github.com/pfefferle/wordpress-activitypub/issues/43 fix this? That should allow @DeadSuperHero https://github.com/DeadSuperHero to continue using @[email protected] scheme employed by pterotype, if I'm understanding this correctly.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pfefferle/wordpress-activitypub/issues/75#issuecomment-599312001, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADCBGGDTJ5NVARWN673X2TRHWGI7ANCNFSM4JUDFGQQ .

To clarify, what I mean is: basically we would need to retain the followers collection of the original actor object, and then make sure that the attribution in federated posts correctly points back to it, so that further interactions with said posts receive updates.

On Sun, Mar 15, 2020, 10:57 PM Sean Tilley [email protected] wrote:

Theoretically, yes, but the existing articles would need to retain attribution to the original actor object, and said actor would also need to retain its follower collection from before the transition.

On Sun, Mar 15, 2020, 9:38 PM sunjam [email protected] wrote:

Would resolving issue #43 https://github.com/pfefferle/wordpress-activitypub/issues/43 fix this? That should allow @DeadSuperHero https://github.com/DeadSuperHero to continue using @[email protected] scheme employed by pterotype, if I'm understanding this correctly.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pfefferle/wordpress-activitypub/issues/75#issuecomment-599312001, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADCBGGDTJ5NVARWN673X2TRHWGI7ANCNFSM4JUDFGQQ .

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@DeadSuperHero pterotype was causing serious errors on my wordpress so I just had to uninstall it. Hope you are doing well!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

:shrug: Would love to have work on this, so suppose this will keep it open.

On Thu, Dec 8, 2022 at 7:15 PM stale[bot] @.***> wrote:

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

— Reply to this email directly, view it on GitHub https://github.com/pfefferle/wordpress-activitypub/issues/75#issuecomment-1343789458, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANUKZSBOSGAR5YYHPMJKILWMKP3JANCNFSM4JUDFGQQ . You are receiving this because you commented.Message ID: @.***>

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

:man_shrugging: open

Is this still a valid request?

@pfefferle absolutely my friend. :) It would be so wonderful to continue using @blog.* account instead of it being dead forever. Thanks for considering!

with 1.0.0 it is already possible to use @blog@... or whatever you call it. It is more about the rest of the data!?!

with 1.0.0 it is already possible to use @blog@... or whatever you call it. It is more about the rest of the data!?!

Excellent, do you need help with testing this?

@pfefferle Here are the options I can customize in the pterotype ui in case that helps.

Site Name
Site Description
Site Icon

does it make sense to have these settings? why not use the blogs settings? why should someone wants to have different informations on the blog as on the fediverse? this isn't even possible on Mastodon & Co.

Personally, I really enjoy being able to write my own description, user name and set an icon for how my site is perceived on the fediverse. :shrug:

Here is how it looks from Mastodon Social. https://mastodon.social/@[email protected]

Just to chime in here: being able to customize the field values on the blog Actor's profile would allow admins a greater level of customization, without too much disruption to the site itself.

The current blog Actor uses the site icon, name, and tagline for the description. The tagline field is not a great choice for a description field, because a tagline is generally intended to be short, whereas a description may need to be longer. It's also not possible to set a header image or custom field data for things like links.

Being able to update these properties as though they were any other kind of Fediverse profile would be extremely valuable.

I realize this all is a bit out of scope of the original issue. I'd you'd prefer for me to open up a new one for this concept, please let me know!

On Fri, Sep 29, 2023, 07:14 Matthias Pfefferle @.***> wrote:

does it make sense to have these settings? why not use the blogs settings? why should someone wants to have different informations on the blog as on the fediverse? this isn't even possible on Mastodon & Co.

— Reply to this email directly, view it on GitHub https://github.com/Automattic/wordpress-activitypub/issues/75#issuecomment-1740964488, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADCBGAJSR7VNRCV7T42YGDX43JVNANCNFSM4JUDFGQQ . You are receiving this because you were mentioned.Message ID: @.***>

@DeadSuperHero @sunjam Thanks for your feedback and @DeadSuperHero I would love to have that as an extra issue.

And the question is still: Should/can we close this one?

And the question is still: Should/can we close this one?

@pfefferle My question is: can I start using the same @blog@* account?

Thank you so much for caring about this. I love this.

you can rename the blog user (default is [email protected]) to [email protected], yes. This is already possible.

you can rename the blog user (default is [email protected]) to [email protected], yes. This is already possible.

Okay, did this by creating a blog user on my site. Seems the post is not showing on the federation side, nor is the gravator icon or profile description updated to replace those previously defined within pterotype.

@sunjam the content-negotiation does not seem to work on your blog.

curl "https://james.network/archives/author/blog/" \
     -H 'Accept: application/activity+json'

This returns HTML instead of JSON. Do you maybe use a Caching plugin?

My question is: can I start using the same @blog@* account?

This will not work for any instance that has previously interacted with the pterotype acct, since those instances have a cached copy of the pterotype public key, which will be different to the newly created one. Mastodon and most other software will ignore the new account.

Essentially the Pterotype actor would need to send aMove activity:

{
    "@context": "https://www.w3.org/ns/activitystreams",
    "id": "https://old.instance/users/someusername#moves/1",
    "type": "Move",
    "target": "https://new.instance/users/someothername",
    "actor": "https://old.instance/users/someusername",
    "object": "https://old.instance/users/someusername"
}

And our new Actor would need to have an alsoKnownAs property pointing to the pterotype actor.

This activity would trigger an all pterotype followers to unfollow, and follow our new actor.

Ref

This returns HTML instead of JSON. Do you maybe use a Caching plugin?

Yes, LiteSpeed cache app from hosting provider.