janboddez / addon-for-activitypub Goto Github PK

Not sure how far along the main plugin is in this respect, but maybe we could have a simple associative array for the "profile fields," for instance?

return array(
  'Blog' => 'https://jan.boddez.net',
  'Location' => '🇧🇪🇳🇱',
); 

Like, not accept likes, but federate them, i.e., turn Like posts into ActivityPub Like activities with a (remote) URL as their object.

Oughta be very similar to reposts. Like, transform Create activity into Like ... and exclude from outbox etc. Deletion of a Like post should result in an Undo of the Like activity.

To detect we're "in an ActivityPub endpoint."

E.g., here:

We should probably move this to a helper function, to be honest.

Stop using WordPress' subdir in

And instead just use the first two or so characters of the hash.

Also, don't base the hash on the image URL (which may change when an actor updates their avatar) and instead base it off the actor URL (which should be unique). That should allow us to keep up with future updates (by simply overwriting any existing image, as the actor URL and thus hash should not change).

To always have all metadata and taxonomy terms in place before scheduling.

There's a filter in the main plugin somewhere, but it doesn't prevent, e.g., Mastodon from GETting the post.

Requires some changes to the ActivityPub plugin, first. Unless it doesn't.

In general, the plugin needs "disabled" in three different places:

• POST requests need stopped to disable "active" federation
• "Content negotiation" (for GET requests) needs bypassed so as not to return JSON
• "Local-only" posts need to be excluded from outboxes and "featured" collections

Look for a u-in-reply-to URL. If one is found, and it's a page on our very own site, set an inReplyTo property accordingly.

If it isn't, fetch the remote page in the background. If it supports ActivityPub, set an inReplyTo property accordingly.

In fact, the second approach should cover also pages on our own site, so maybe we should prioritize it.

Anything microformats will be using php-mf directly, rather than depend on IB translating.

Going to be more difficult for the image store/cache. Not sure I want all that code duplicated across multiple plugins.

Unless I could somehow extract it out into an actual PHP library (i.e., a Composer package). But that would also mean getting rid of all the WP functions.

Could be me, but while boosts lead to a notification on the server of the person whose toot got boosted, I don't see them appear on another server (where I have an account that follows the blog).

Not super important, but ...