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", { "ostatus": "http://ostatus.org#", "atomUri": "ostatus:atomUri", "inReplyToAtomUri": "ostatus:inReplyToAtomUri", "conversation": "ostatus:conversation", "sensitive": "as:sensitive", "toot": "http://joinmastodon.org/ns#", "votersCount": "toot:votersCount" } ], "id": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415/activity", "type": "Create", "actor": "https://mastodon.social/users/nateberkopec", "published": "2024-10-23T14:00:01Z", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://mastodon.social/users/nateberkopec/followers" ], "object": { "id": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415", "type": "Note", "summary": null, "inReplyTo": null, "published": "2024-10-23T14:00:01Z", "url": "https://mastodon.social/@nateberkopec/113357094995299415", "attributedTo": "https://mastodon.social/users/nateberkopec", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://mastodon.social/users/nateberkopec/followers" ], "sensitive": false, "atomUri": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415", "inReplyToAtomUri": null, "conversation": "tag:mastodon.social,2024-10-23:objectId=829610722:objectType=Conversation", "content": "<p>&quot;ASAP&quot; or &quot;high&quot; is a bad queue name. Every job *feels* urgent. Is it? </p><p>In my &quot;SLO-based&quot; queue naming system (&quot;within_5_minutes&quot;, &quot;within_1_day&quot;), you can call this the &quot;within_0_seconds&quot; queue.</p><p>Make the decision concrete: does it need to be done &quot;within zero seconds&quot;? In practice, this queue&#39;s SLO is the same as a web request.</p>", "contentMap": { "en": "<p>&quot;ASAP&quot; or &quot;high&quot; is a bad queue name. Every job *feels* urgent. Is it? </p><p>In my &quot;SLO-based&quot; queue naming system (&quot;within_5_minutes&quot;, &quot;within_1_day&quot;), you can call this the &quot;within_0_seconds&quot; queue.</p><p>Make the decision concrete: does it need to be done &quot;within zero seconds&quot;? In practice, this queue&#39;s SLO is the same as a web request.</p>" }, "attachment": [], "tag": [], "replies": { "id": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415/replies", "type": "Collection", "first": { "type": "CollectionPage", "next": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415/replies?only_other_accounts=true&page=true", "partOf": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415/replies", "items": [] } }, "likes": { "id": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415/likes", "type": "Collection", "totalItems": 15 }, "shares": { "id": "https://mastodon.social/users/nateberkopec/statuses/113357094995299415/shares", "type": "Collection", "totalItems": 7 } } }