We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Fetching a status by it’s id gives non-ActivityPub data.
To Reproduce Steps to reproduce the behavior:
Accept: application/activity+json
curl -H 'Accept: application/activity+json' https://cloud.beepboop.ga/apps/social/@dirb/15464603731806653100
Expected behavior The ActivityPub object should be returned (see the specification or other ActivityPub software).
Server details Not my instance, and I have no knowledge about nextcloud and there is no nodeinfo. So this is why I even put the URLs.
The text was updated successfully, but these errors were encountered:
please try with Accept: application/ld+json or wait for 0.1.2: https://github.com/nextcloud/social/pull/290/files
Accept: application/ld+json
Sorry, something went wrong.
I'm the owner of that box, it's running on: PHP 7.2.10-0ubuntu0.18.04.1 Nextcloud 15.0.0 nextcloud/social 65dc245
so the "compare Accept Header from a list" is pull request already merged
Sorry, I should have noted that I did try with application/ld+json so it’s not a duplicate.
application/ld+json
No branches or pull requests
Describe the bug
Fetching a status by it’s id gives non-ActivityPub data.
To Reproduce
Steps to reproduce the behavior:
Accept: application/activity+json
. Here:curl -H 'Accept: application/activity+json' https://cloud.beepboop.ga/apps/social/@dirb/15464603731806653100
Expected behavior
The ActivityPub object should be returned (see the specification or other ActivityPub software).
Server details
Not my instance, and I have no knowledge about nextcloud and there is no nodeinfo. So this is why I even put the URLs.
The text was updated successfully, but these errors were encountered: