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

[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.

Add/User Delete activities by mediaformat · Pull Request #552 · Automattic/wordpress-activitypub

Adds a Server class for processing server activities, such as Federating a delete_user action Fixes #566 https://gdpr.eu/right-to-be-forgotten/ Proposed changes: Adds a Server class for processi...

GitHub (github.com)

[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:

Erlend Sogge Heggen (@[email protected])

https://socialhub.activitypub.rocks/t/fep-7952-roadmap-for-actor-and-object-portability/4332?u=erlend_sh I think this is the most important (WIP) Fediverse Enhancement Proposal of this year for the #ActivityPub protocol: FEP-7952: Roadmap for Actor and Object Portability — by @[email protected] and @[email protected] It ties a lot of elementary building blocks for #nomadicidentity neatly together, most succinctly summed up by one particularly magic feature: Bring-your-own Actor ID! 🪪💫 Actor profiles can now be hosted separately from the instance (including as a static JSON object (…)

Writing Exchange (writing.exchange)

[khleedril@cyberplace.social]

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