search

fediverse-devnet / feditest-tests-fediverse

The tests for the fediverse testsuite
MIT License
5 stars 4 forks source link

Test `Create` delivered to user's inbox #14

Open snarfed opened 6 months ago

snarfed commented 6 months ago

Deliver a Create of a Note to a user's inbox. Check that it returns HTTP 200 or 202, and that it's visible to the user when they search for it by the Note's id. https://www.w3.org/TR/activitypub/#delivery

steve-bate commented 1 month ago

When defining a test for this, be aware that most Fediverse servers (Mastodon, for example) do not implement an inbox collection. They implement an inbox API endpoint, but there is no inbox data structure to query after a Create has been submitted. Mastodon returns a 404 status for inbox GET requests.

Also, if you submit a Create activity with URI https://publisher.example/activity to a server at domain consumer.example, you generally won't be able to determine if consumer.example can view the publisher.example activity without using an implementation-specific API or scraping a web UI. If you dereference the activity URI, you will obviously retrieve it from publisher.example rather than consumer.example. When using an application-specific API, like Mastodon's, you may need to use an app-specific identifier (which was not communicated to the publisher) rather than an AP activity or object URI to query the application.