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.
{
"@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/heatsink/statuses/114687693075014064/replies",
"type": "Collection",
"first": {
"id": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/replies?page=true",
"type": "CollectionPage",
"next": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/replies",
"items": [
{
"id": "https://infosec.exchange/users/heatsink/statuses/114687705338146490",
"type": "Note",
"summary": null,
"inReplyTo": "https://infosec.exchange/users/heatsink/statuses/114687693075014064",
"published": "2025-06-15T13:51:43Z",
"url": "https://infosec.exchange/@heatsink/114687705338146490",
"attributedTo": "https://infosec.exchange/users/heatsink",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/heatsink/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/heatsink/statuses/114687705338146490",
"inReplyToAtomUri": "https://infosec.exchange/users/heatsink/statuses/114687693075014064",
"conversation": "tag:infosec.exchange,2025-06-14:objectId=281123574:objectType=Conversation",
"content": "<p>This also makes me wonder where it thinks it was working before. It couldn't have been on the persistent volume claim, that wasn't writable. It must have been in the container's local storage which explains why it went away on a pod restart.</p>",
"contentMap": {
"en": "<p>This also makes me wonder where it thinks it was working before. It couldn't have been on the persistent volume claim, that wasn't writable. It must have been in the container's local storage which explains why it went away on a pod restart.</p>"
},
"attachment": [],
"tag": [],
"replies": {
"id": "https://infosec.exchange/users/heatsink/statuses/114687705338146490/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/heatsink/statuses/114687705338146490/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/heatsink/statuses/114687705338146490/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/heatsink/statuses/114687705338146490/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://infosec.exchange/users/heatsink/statuses/114687705338146490/shares",
"type": "Collection",
"totalItems": 0
}
}
]
}
}