Conversation
- Add Tag handler with basic tag lookup from WordPress taxonomy - Register GET /api/v1/tags/:name route with rewrite rule - Add mastodon_api_tag filter for extensibility - Ensure numeric ID remapping on mastodon_api_tag_timeline responses - Default tag timeline limit to 5 (currently ignored by tags.pub integration due to HTTP round-trip costs per item)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GET /api/v1/tags/:nameendpoint returning a Tag entity with data from WordPress taxonomymastodon_api_tag_timelineresponses (fixes URL-based account IDs being returned to clients like Tusky)Context
This is the EMA side of tags.pub integration. The ActivityPub plugin side (fetching the tags.pub outbox and converting Announces to statuses) is in Automattic/wordpress-activitypub#3151.
Test plan
GET /api/v1/tags/wordpressreturns a valid Tag entity