it's often so complex to add #ActivityPub to an already existing platform (for example #WordPress ) and it gets even more complex if it is not built for social media

[pfefferle@mastodon.social]

it's often so complex to add #ActivityPub to an already existing platform (for example #WordPress ) and it gets even more complex if it is not built for social media

For example

1. Deleting Users from the Fediverse, that still exist on the blog.
2. Delete the whole blog from the fediverse, but take temporary plugin deactivations/deletions into account.
3. Caching by third party plugins.
4. Shared hosting.
5. Posts and Comments in different DB tables
6. Publish only a subset of posts

[pfefferle@mastodon.social]

7. Allow local comments and comments from the Fediverse, but don't mix them up.
8. Allow replies only for selected posts.
9. Follow the whole blog, selected autors or a mixture of all of them.
10. ...

...but it's still fun ...or perhaps precisely because of this

[nickbohle@mastodon.social]

@pfefferle Keep up your great work!

[pfefferle@mastodon.social]

thanks @NickBohle

[paul@oldfriends.live]

@pfefferle

I'm the one that opened that GitHub question about shutting my blog down and making a clean break from ActivityPub.

I decided to renew my SSL for another year on the domain, keep it up and give you a year to figure it out instead of just parking it for a while. 🤭

[pfefferle@mastodon.social]

@paul having an explicit action to do that is not the problem! https://github.com/Automattic/wordpress-activitypub/pull/552/files#diff-1916afa363050c8d1ac472b3d135f3076b5f4322874a4eeea8fb30da87ef7c3c

...but what about doing it on deactivating/deleting the plugin? do people expect that? what about people that simply deactivate the plugin to debug something?

THAT is tricky

[pfefferle@mastodon.social]

@paul it's so much easier and faster to deactivate a plugin, than to delete a mastodon instance!

[paul@oldfriends.live]

@pfefferle

Seems to me, making a clean exit from AP would be a priority because someone has made the explicit decision to leave AP & that gives the domain a clean AP start in the future for the next domain owner/operator.

Also, and this is out of my wheelhouse, the issue with deactivating and reactivating would be getting the Fediverse to start talking again to the WordPress blog. I know Mastodon stops trying after a certain period of failure but not sure its mechanism on reentry.

[paul@oldfriends.live]

@pfefferle

I appreciate your work on this and making WordPress/ActivityPub cabaple in the first place.

https://github.com/Automattic/wordpress-activitypub/pull/552

[paul@social.van.buu.re]

@pfefferle Do you like real world examples / challenges? Because I have one.

(and I would like some expert advice, please?)

[pfefferle@mastodon.social]

@paul it is not about re-trying, but (at least as far as I know) deletes seems to be irrevocable. If you delete a post from Mastodon, you can't re-send it... Mastodon will ignore it from then on and I would assume that this is the same with Users and/or the blog. So if we do send a delete by accident, this could cause some serious damage.

[pfefferle@mastodon.social]

@paul sure!

[manualdousuario@mastodon.social]

@pfefferle @paul maybe add a manual setting to differentiate temp deactivation (default) from deactivate+delete for good?

[erlend@writing.exchange]

@pfefferle could be a lot easier if all the WordPress site had to carry was the Actor ID:

https://writing.exchange/@erlend/112684879834557152

[khleedril@cyberplace.social]

@pfefferle @paul That could be fixed in AP by allowing an Undo action to carry a Delete action object.