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

Matthias Pfefferle

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

Matthias Pfefferle

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

Nick Bohle 🇪🇺

@pfefferle Keep up your great work!

Matthias Pfefferle

thanks @NickBohle

Paul Chambers

@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. 🤭

Matthias Pfefferle

@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

Matthias Pfefferle

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

Paul Chambers

@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 Chambers

@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 van Buuren

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

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

Matthias Pfefferle

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

Matthias Pfefferle

@paul sure!

Rodrigo Ghedin

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

Erlend Sogge Heggen

@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

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