Skip to content

Conversation

@thebaer
Copy link
Member

@thebaer thebaer commented Nov 26, 2019

Previously, fetching ActivityStreams data about a post via /api/posts/ID, instead of /api/collections/ALIAS/posts/SLUG wouldn't include the instance's base URL in the post's id, causing federation issues. This fixes that.

It also includes the related fix in #212.

Previously, this check would return a "user not found" error when
retrieving a collection post by its post ID, e.g. /api/posts/abc123
instead of /api/collections/demo/posts/my-slug -- this happens
particularly when `Announce`ing a post in the fediverse. This change
fixes that.
Previously, fetching ActivityStreams data about a post via
/api/posts/ID, instead of /api/collections/ALIAS/posts/SLUG wouldn't
include the instance's base URL. This fixes that.
@thebaer thebaer added this to the 0.11.2 milestone Nov 26, 2019
@thebaer thebaer requested a review from a user November 26, 2019 18:03
@thebaer thebaer changed the title Fix hostname fediverse Fix fediverse post IDs Nov 26, 2019
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good as well, tested both endpoints locally

@thebaer
Copy link
Member Author

thebaer commented Nov 27, 2019

Thanks! Merging now.

@thebaer thebaer merged commit 88a3ed7 into hotfix-0.11.2 Nov 27, 2019
@thebaer thebaer deleted the fix-hostname-fediverse branch November 27, 2019 22:02
@thebaer thebaer mentioned this pull request Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants