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",
"Hashtag": "as:Hashtag"
}
],
"id": "https://mastodon.social/users/ddoomen/statuses/113425224402463086",
"type": "Note",
"summary": null,
"inReplyTo": "https://mastodon.social/users/ddoomen/statuses/113425223839679942",
"published": "2024-11-04T14:46:13Z",
"url": "https://mastodon.social/@ddoomen/113425224402463086",
"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/113425224402463086",
"inReplyToAtomUri": "https://mastodon.social/users/ddoomen/statuses/113425223839679942",
"conversation": "tag:mastodon.social,2024-11-04:objectId=839391737:objectType=Conversation",
"content": "<p>We made that decision about two years ago, but we rarely touched the existing tests. Instead, we decided that the new conventions should apply to new tests and aimed to follow the Campground Rule ("leave the campground cleaner than you got there"). Does that mean I allow codebases to become messy? Not exactly. I'm very conscious of the internal <a href=\"https://mastodon.social/tags/boundaries\" class=\"mention hashtag\" rel=\"tag\">#<span>boundaries</span></a> within my codebases and strive to keep each boundary consistent. Just as I use those boundaries as natural seams for unit testing... (cont'd)</p>",
"contentMap": {
"en": "<p>We made that decision about two years ago, but we rarely touched the existing tests. Instead, we decided that the new conventions should apply to new tests and aimed to follow the Campground Rule ("leave the campground cleaner than you got there"). Does that mean I allow codebases to become messy? Not exactly. I'm very conscious of the internal <a href=\"https://mastodon.social/tags/boundaries\" class=\"mention hashtag\" rel=\"tag\">#<span>boundaries</span></a> within my codebases and strive to keep each boundary consistent. Just as I use those boundaries as natural seams for unit testing... (cont'd)</p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://mastodon.social/tags/boundaries",
"name": "#boundaries"
}
],
"replies": {
"id": "https://mastodon.social/users/ddoomen/statuses/113425224402463086/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.social/users/ddoomen/statuses/113425224402463086/replies?min_id=113425225115667369&page=true",
"partOf": "https://mastodon.social/users/ddoomen/statuses/113425224402463086/replies",
"items": [
"https://mastodon.social/users/ddoomen/statuses/113425225115667369"
]
}
},
"likes": {
"id": "https://mastodon.social/users/ddoomen/statuses/113425224402463086/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://mastodon.social/users/ddoomen/statuses/113425224402463086/shares",
"type": "Collection",
"totalItems": 0
}
}