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", "litepub": "http://litepub.social/ns#", "directMessage": "litepub:directMessage" } ], "id": "https://infosec.exchange/users/dazo/statuses/114613627632241765", "type": "Note", "summary": null, "inReplyTo": "https://infosec.exchange/users/dazo/statuses/114604916096682150", "published": "2025-06-02T11:52:47Z", "url": "https://infosec.exchange/@dazo/114613627632241765", "attributedTo": "https://infosec.exchange/users/dazo", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://infosec.exchange/users/dazo/followers" ], "sensitive": false, "atomUri": "https://infosec.exchange/users/dazo/statuses/114613627632241765", "inReplyToAtomUri": "https://infosec.exchange/users/dazo/statuses/114604916096682150", "conversation": "tag:infosec.exchange,2025-05-31:objectId=276688025:objectType=Conversation", "content": "<p>It turned out it was some helper script for the git repo which resulted in this mess.</p><p><a href=\"https://lore.kernel.org/all/202505312300.95D7D917@keescook/\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">lore.kernel.org/all/2025053123</span><span class=\"invisible\">00.95D7D917@keescook/</span></a></p><p>Kees Cook has gained regained his privileges again.</p><p>Regardless of the \"why and how\" aspects if this incident, it illustrates the strength of git and how it is impossible to manipulate a git tree without triggering some kind of alarms - if you pay attention.</p>", "contentMap": { "en": "<p>It turned out it was some helper script for the git repo which resulted in this mess.</p><p><a href=\"https://lore.kernel.org/all/202505312300.95D7D917@keescook/\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">lore.kernel.org/all/2025053123</span><span class=\"invisible\">00.95D7D917@keescook/</span></a></p><p>Kees Cook has gained regained his privileges again.</p><p>Regardless of the \"why and how\" aspects if this incident, it illustrates the strength of git and how it is impossible to manipulate a git tree without triggering some kind of alarms - if you pay attention.</p>" }, "attachment": [], "tag": [], "replies": { "id": "https://infosec.exchange/users/dazo/statuses/114613627632241765/replies", "type": "Collection", "first": { "type": "CollectionPage", "next": "https://infosec.exchange/users/dazo/statuses/114613627632241765/replies?only_other_accounts=true&page=true", "partOf": "https://infosec.exchange/users/dazo/statuses/114613627632241765/replies", "items": [] } }, "likes": { "id": "https://infosec.exchange/users/dazo/statuses/114613627632241765/likes", "type": "Collection", "totalItems": 0 }, "shares": { "id": "https://infosec.exchange/users/dazo/statuses/114613627632241765/shares", "type": "Collection", "totalItems": 1 } }