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://mastodon.cc/users/jgarber/statuses/113532765928193215",
"type": "Note",
"summary": null,
"inReplyTo": "https://ruby.social/users/davetron5000/statuses/113532649363289272",
"published": "2024-11-23T14:35:27Z",
"url": "https://mastodon.cc/@jgarber/113532765928193215",
"attributedTo": "https://mastodon.cc/users/jgarber",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.cc/users/jgarber/followers",
"https://ruby.social/users/davetron5000"
],
"sensitive": false,
"atomUri": "https://mastodon.cc/users/jgarber/statuses/113532765928193215",
"inReplyToAtomUri": "https://ruby.social/users/davetron5000/statuses/113532649363289272",
"conversation": "tag:ruby.social,2024-11-23:objectId=59647708:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ruby.social/@davetron5000\" class=\"u-url mention\">@<span>davetron5000</span></a></span> That’s the sort of affordance the library (React, in this case) gives you “for free” (spoiler: not free).</p><p>But of course, you’re correct. Checking that child nodes exist is part of the work if you want a resilient Web Component.</p><p>I’ll sometimes do:</p><p>this.configured = elementOne && elementTwo</p><p>…then check that value in other methods as needed.</p><p>Not sure if there’s a better pattern, but it’s worked for me.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ruby.social/@davetron5000\" class=\"u-url mention\">@<span>davetron5000</span></a></span> That’s the sort of affordance the library (React, in this case) gives you “for free” (spoiler: not free).</p><p>But of course, you’re correct. Checking that child nodes exist is part of the work if you want a resilient Web Component.</p><p>I’ll sometimes do:</p><p>this.configured = elementOne && elementTwo</p><p>…then check that value in other methods as needed.</p><p>Not sure if there’s a better pattern, but it’s worked for me.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://ruby.social/users/davetron5000",
"name": "@davetron5000@ruby.social"
}
],
"replies": {
"id": "https://mastodon.cc/users/jgarber/statuses/113532765928193215/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.cc/users/jgarber/statuses/113532765928193215/replies?min_id=113532771538851809&page=true",
"partOf": "https://mastodon.cc/users/jgarber/statuses/113532765928193215/replies",
"items": [
"https://mastodon.cc/users/jgarber/statuses/113532771538851809"
]
}
},
"likes": {
"id": "https://mastodon.cc/users/jgarber/statuses/113532765928193215/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://mastodon.cc/users/jgarber/statuses/113532765928193215/shares",
"type": "Collection",
"totalItems": 0
}
}