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://social.wildeboer.net/users/jwildeboer/statuses/114516937863847771", "type": "Note", "summary": null, "inReplyTo": "https://social.wildeboer.net/users/jwildeboer/statuses/114516429319640686", "published": "2025-05-16T10:03:18Z", "url": "https://social.wildeboer.net/@jwildeboer/114516937863847771", "attributedTo": "https://social.wildeboer.net/users/jwildeboer", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://social.wildeboer.net/users/jwildeboer/followers" ], "sensitive": false, "atomUri": "https://social.wildeboer.net/users/jwildeboer/statuses/114516937863847771", "inReplyToAtomUri": "https://social.wildeboer.net/users/jwildeboer/statuses/114516429319640686", "conversation": "tag:social.wildeboer.net,2025-05-16:objectId=11318904:objectType=Conversation", "content": "<p>The argument raised by some commenters that using ClientAuth is &quot;abusing&quot; LE/Certs and that I should instead set up my own CA (Certification Authority) and PKI (Public Key Infrastructure) might be technically sound, but pragmatically wrong, IMHO. Running my own CA *adds more security risks*, IMHO. Being forced to do that because Google decides to refuse to trust certificates with ClientAuth set? Because they reduce the scope of certs to web browser/server communications? That feels abusive to me</p>", "contentMap": { "en": "<p>The argument raised by some commenters that using ClientAuth is &quot;abusing&quot; LE/Certs and that I should instead set up my own CA (Certification Authority) and PKI (Public Key Infrastructure) might be technically sound, but pragmatically wrong, IMHO. Running my own CA *adds more security risks*, IMHO. Being forced to do that because Google decides to refuse to trust certificates with ClientAuth set? Because they reduce the scope of certs to web browser/server communications? That feels abusive to me</p>" }, "attachment": [], "tag": [], "replies": { "id": "https://social.wildeboer.net/users/jwildeboer/statuses/114516937863847771/replies", "type": "Collection", "first": { "type": "CollectionPage", "next": "https://social.wildeboer.net/users/jwildeboer/statuses/114516937863847771/replies?min_id=114523495213787345&page=true", "partOf": "https://social.wildeboer.net/users/jwildeboer/statuses/114516937863847771/replies", "items": [ "https://social.wildeboer.net/users/jwildeboer/statuses/114523495213787345" ] } }, "likes": { "id": "https://social.wildeboer.net/users/jwildeboer/statuses/114516937863847771/likes", "type": "Collection", "totalItems": 14 }, "shares": { "id": "https://social.wildeboer.net/users/jwildeboer/statuses/114516937863847771/shares", "type": "Collection", "totalItems": 2 } }