activitypub 1.0.0-alpha26

Hello flexible entity sources!

This release adds support for allowing any content entity to be the source of content for an activity using the 'Public message' plugin. This uses to be limited to nodes and comments, but now allows any (relevant) content entity at the moment. Some have been excluded ('user', 'path_alias', 'shortcut', 'oauth2_token', 'activitypub_actor', 'consumer', 'menu_link_content', 'activitypub_timeline_item', 'file') as they do not make much sense to be used as content.

In a next release, a drupal recipe will be availble that will either ship with a couple of content types, or will use the activity entity as the source of content!

Contributors (2)

kinta, swentel

Changelog

Issues: 9 issues resolved.

Changes since 1.0.0-alpha25:

Bug

• #3515912: Multilanguage problems since D10.1
• #3321662: Do not get context for local content

Task

• #3577638: Allow any entity to be the source of an activity
• #3603962: Add extra validation to image upload in mastodon api
• #3319078: Handle 404 & 410 errors on outbox requests
• #3523584: Drupal now showing up after FediDB.org refresh, but missing data
• #3315832: Backfill inbox
• #3575172: Add an event dispatcher to act on incoming activities
• #3327812: Expose AP outbox element to form display