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", "Hashtag": "as:Hashtag" } ], "id": "https://infosec.exchange/users/cmars/statuses/114404605822066639", "type": "Note", "summary": null, "inReplyTo": null, "published": "2025-04-26T13:55:48Z", "url": "https://infosec.exchange/@cmars/114404605822066639", "attributedTo": "https://infosec.exchange/users/cmars", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://infosec.exchange/users/cmars/followers" ], "sensitive": false, "atomUri": "https://infosec.exchange/users/cmars/statuses/114404605822066639", "inReplyToAtomUri": null, "conversation": "tag:infosec.exchange,2025-04-26:objectId=265316101:objectType=Conversation", "content": "<p><a href=\"https://infosec.exchange/tags/stigmerge\" class=\"mention hashtag\" rel=\"tag\">#<span>stigmerge</span></a> update!</p><p>The stigmerge-peer crate has been heavily refactored into an actor-based architecture, a very CSP-like design with supervisors. i have a strong aversion to frameworks, so I implemented my own model inspired by <a href=\"https://ryhl.io/blog/actors-with-tokio/\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"\">ryhl.io/blog/actors-with-tokio/</span><span class=\"invisible\"></span></a>.</p><p>I still need to implement much of that advice.. Deal with backpressure, etc. but...</p><p>Last night I sent a file through successfully with share announcer, resolver, seeder and fetcher actors!</p><p>Hoping for a new major version release in the next couple of weeks. It will likely be a protocol and CLI breaking change.</p><p><a href=\"https://infosec.exchange/tags/rust\" class=\"mention hashtag\" rel=\"tag\">#<span>rust</span></a> <a href=\"https://infosec.exchange/tags/veilid\" class=\"mention hashtag\" rel=\"tag\">#<span>veilid</span></a> <a href=\"https://infosec.exchange/tags/p2p\" class=\"mention hashtag\" rel=\"tag\">#<span>p2p</span></a></p>", "contentMap": { "en": "<p><a href=\"https://infosec.exchange/tags/stigmerge\" class=\"mention hashtag\" rel=\"tag\">#<span>stigmerge</span></a> update!</p><p>The stigmerge-peer crate has been heavily refactored into an actor-based architecture, a very CSP-like design with supervisors. i have a strong aversion to frameworks, so I implemented my own model inspired by <a href=\"https://ryhl.io/blog/actors-with-tokio/\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"\">ryhl.io/blog/actors-with-tokio/</span><span class=\"invisible\"></span></a>.</p><p>I still need to implement much of that advice.. Deal with backpressure, etc. but...</p><p>Last night I sent a file through successfully with share announcer, resolver, seeder and fetcher actors!</p><p>Hoping for a new major version release in the next couple of weeks. It will likely be a protocol and CLI breaking change.</p><p><a href=\"https://infosec.exchange/tags/rust\" class=\"mention hashtag\" rel=\"tag\">#<span>rust</span></a> <a href=\"https://infosec.exchange/tags/veilid\" class=\"mention hashtag\" rel=\"tag\">#<span>veilid</span></a> <a href=\"https://infosec.exchange/tags/p2p\" class=\"mention hashtag\" rel=\"tag\">#<span>p2p</span></a></p>" }, "attachment": [], "tag": [ { "type": "Hashtag", "href": "https://infosec.exchange/tags/stigmerge", "name": "#stigmerge" }, { "type": "Hashtag", "href": "https://infosec.exchange/tags/rust", "name": "#rust" }, { "type": "Hashtag", "href": "https://infosec.exchange/tags/veilid", "name": "#veilid" }, { "type": "Hashtag", "href": "https://infosec.exchange/tags/p2p", "name": "#p2p" } ], "replies": { "id": "https://infosec.exchange/users/cmars/statuses/114404605822066639/replies", "type": "Collection", "first": { "type": "CollectionPage", "next": "https://infosec.exchange/users/cmars/statuses/114404605822066639/replies?min_id=114404662885668703&page=true", "partOf": "https://infosec.exchange/users/cmars/statuses/114404605822066639/replies", "items": [ "https://infosec.exchange/users/cmars/statuses/114404662885668703" ] } }, "likes": { "id": "https://infosec.exchange/users/cmars/statuses/114404605822066639/likes", "type": "Collection", "totalItems": 3 }, "shares": { "id": "https://infosec.exchange/users/cmars/statuses/114404605822066639/shares", "type": "Collection", "totalItems": 3 } }