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"
}
],
"id": "https://ruby.social/users/nirvdrum/statuses/112604664596651903",
"type": "Note",
"summary": null,
"inReplyTo": "https://ruby.social/users/braidn/statuses/112604381631820891",
"published": "2024-06-12T16:47:04Z",
"url": "https://ruby.social/@nirvdrum/112604664596651903",
"attributedTo": "https://ruby.social/users/nirvdrum",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://ruby.social/users/nirvdrum/followers",
"https://ruby.social/users/braidn",
"https://ruby.social/users/soulcutter"
],
"sensitive": false,
"atomUri": "https://ruby.social/users/nirvdrum/statuses/112604664596651903",
"inReplyToAtomUri": "https://ruby.social/users/braidn/statuses/112604381631820891",
"conversation": "tag:ruby.social,2024-06-12:objectId=47506987:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ruby.social/@braidn\" class=\"u-url mention\">@<span>braidn</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://ruby.social/@soulcutter\" class=\"u-url mention\">@<span>soulcutter</span></a></span> I guess I'm the odd one out that doesn't really care about linear history. I'll rebase commits before merge, but I like having a merge commit. It makes reverting considerably easier, should it become necessary. I suppose squash commits make reverting easy, too, but it also loses history.</p><p>I structure my commits so they're individually useful & rebase locally. I also write meaningful commit messages that explain the "why" rather than the "what" so history is meaningful.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ruby.social/@braidn\" class=\"u-url mention\">@<span>braidn</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://ruby.social/@soulcutter\" class=\"u-url mention\">@<span>soulcutter</span></a></span> I guess I'm the odd one out that doesn't really care about linear history. I'll rebase commits before merge, but I like having a merge commit. It makes reverting considerably easier, should it become necessary. I suppose squash commits make reverting easy, too, but it also loses history.</p><p>I structure my commits so they're individually useful & rebase locally. I also write meaningful commit messages that explain the "why" rather than the "what" so history is meaningful.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://ruby.social/users/braidn",
"name": "@braidn"
},
{
"type": "Mention",
"href": "https://ruby.social/users/soulcutter",
"name": "@soulcutter"
}
],
"replies": {
"id": "https://ruby.social/users/nirvdrum/statuses/112604664596651903/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://ruby.social/users/nirvdrum/statuses/112604664596651903/replies?only_other_accounts=true&page=true",
"partOf": "https://ruby.social/users/nirvdrum/statuses/112604664596651903/replies",
"items": []
}
},
"likes": {
"id": "https://ruby.social/users/nirvdrum/statuses/112604664596651903/likes",
"type": "Collection",
"totalItems": 2
},
"shares": {
"id": "https://ruby.social/users/nirvdrum/statuses/112604664596651903/shares",
"type": "Collection",
"totalItems": 0
}
}