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",
"blurhash": "toot:blurhash",
"focalPoint": {
"@container": "@list",
"@id": "toot:focalPoint"
}
}
],
"id": "https://mastodon.social/users/ddoomen/statuses/113425219389479151",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2024-11-04T14:44:57Z",
"url": "https://mastodon.social/@ddoomen/113425219389479151",
"attributedTo": "https://mastodon.social/users/ddoomen",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.social/users/ddoomen/followers"
],
"sensitive": false,
"atomUri": "https://mastodon.social/users/ddoomen/statuses/113425219389479151",
"inReplyToAtomUri": null,
"conversation": "tag:mastodon.social,2024-11-04:objectId=839391737:objectType=Conversation",
"content": "<p>A successful codebase grows and changes every day. New features are added, refactorings are applied, and partial redesigns are inevitable. New developers, with different personal styles, join the team, while long-time members leave to pursue other projects or careers. The original "architects" of the codebase may have had a great vision, but that information often gets lost. As a senior developer, I recognize the desire to keep a codebase consistent... (cont'd)</p>",
"contentMap": {
"en": "<p>A successful codebase grows and changes every day. New features are added, refactorings are applied, and partial redesigns are inevitable. New developers, with different personal styles, join the team, while long-time members leave to pursue other projects or careers. The original "architects" of the codebase may have had a great vision, but that information often gets lost. As a senior developer, I recognize the desire to keep a codebase consistent... (cont'd)</p>"
},
"attachment": [
{
"type": "Document",
"mediaType": "image/png",
"url": "https://files.mastodon.social/media_attachments/files/113/425/210/483/974/458/original/c6f201824503176e.png",
"name": null,
"blurhash": "UCA2+_?Z4sNN%MazWCoe0PIX-,xrIwt5oeNI",
"width": 1200,
"height": 1200
}
],
"tag": [],
"replies": {
"id": "https://mastodon.social/users/ddoomen/statuses/113425219389479151/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.social/users/ddoomen/statuses/113425219389479151/replies?min_id=113425223839679942&page=true",
"partOf": "https://mastodon.social/users/ddoomen/statuses/113425219389479151/replies",
"items": [
"https://mastodon.social/users/ddoomen/statuses/113425223839679942"
]
}
},
"likes": {
"id": "https://mastodon.social/users/ddoomen/statuses/113425219389479151/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://mastodon.social/users/ddoomen/statuses/113425219389479151/shares",
"type": "Collection",
"totalItems": 0
}
}