ActivityPub Viewer

A small tool to view real-world ActivityPub objects as JSON! Enter a URL or username from Mastodon or a similar service below, and we'll send a request with the right Accept header to the server to view the underlying object.

Open in browser →
{ "@context": [ "https://www.w3.org/ns/activitystreams", "https://w3id.org/security/v1", { "Hashtag": "as:Hashtag", "sensitive": "as:sensitive", "manuallyApprovesFollowers": "as:manuallyApprovesFollowers", "alsoKnownAs": { "@id": "as:alsoKnownAs", "@type": "@id" }, "movedTo": { "@id": "as:movedTo", "@type": "@id" }, "toot": "http://joinmastodon.org/ns#", "featured": { "@id": "toot:featured", "@type": "@id" }, "Emoji": "toot:Emoji", "blurhash": "toot:blurhash", "votersCount": "toot:votersCount", "schema": "http://schema.org#", "PropertyValue": "schema:PropertyValue", "value": "schema:value", "ostatus": "http://ostatus.org#", "conversation": "ostatus:conversation" } ], "type": "Note", "id": "https://hexa.ninja/o/701b66a92ffb4c1e848a94eaf013e55f", "attributedTo": "https://hexa.ninja", "content": "<p><span class=\"h-card\"><a href=\"https://aaronparecki.com/aaronpk\" class=\"u-url mention\">@aaronpk@aaronparecki.com</a></span> Some servers don&#x27;t behave correctly, I noticed some of them sending the same <code>Delete</code> activity over and over, like hundreds of time per day, for days. Even when the server answers with 2XX status code (202 in my case).</p>\n", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://hexa.ninja/followers", "https://aaronparecki.com/aaronpk" ], "published": "2022-11-11T18:27:47Z", "context": "https://hexa.ninja/contexts/d5ace1c088ce4d90b9e6c5e15f6587ab", "conversation": "https://hexa.ninja/contexts/d5ace1c088ce4d90b9e6c5e15f6587ab", "url": "https://hexa.ninja/o/701b66a92ffb4c1e848a94eaf013e55f", "tag": [ { "type": "Mention", "href": "https://aaronparecki.com/aaronpk", "name": "@aaronpk@aaronparecki.com" } ], "summary": null, "inReplyTo": "https://aaronparecki.com/2022/11/11/51/activitypub", "sensitive": false, "attachment": [] }