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://fosstodon.org/users/emilis/statuses/109507005723728786",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2022-12-13T15:11:41Z",
"url": "https://fosstodon.org/@emilis/109507005723728786",
"attributedTo": "https://fosstodon.org/users/emilis",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://fosstodon.org/users/emilis/followers"
],
"sensitive": false,
"atomUri": "https://fosstodon.org/users/emilis/statuses/109507005723728786",
"inReplyToAtomUri": null,
"conversation": "tag:fosstodon.org,2022-12-13:objectId=68690482:objectType=Conversation",
"content": "<p>@cipher In the words of E.W. <a href=\"https://fosstodon.org/tags/Dijkstra\" class=\"mention hashtag\" rel=\"tag\">#<span>Dijkstra</span></a> :</p><p>> We could, for instance, begin with cleaning up our language by no longer calling a bug a bug but by calling it an error. It is much more honest because it squarely puts the blame where it belongs, viz. with the programmer who made the error...</p><p><a href=\"https://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://www.</span><span class=\"ellipsis\">cs.utexas.edu/~EWD/transcripti</span><span class=\"invisible\">ons/EWD10xx/EWD1036.html</span></a></p>",
"contentMap": {
"en": "<p>@cipher In the words of E.W. <a href=\"https://fosstodon.org/tags/Dijkstra\" class=\"mention hashtag\" rel=\"tag\">#<span>Dijkstra</span></a> :</p><p>> We could, for instance, begin with cleaning up our language by no longer calling a bug a bug but by calling it an error. It is much more honest because it squarely puts the blame where it belongs, viz. with the programmer who made the error...</p><p><a href=\"https://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://www.</span><span class=\"ellipsis\">cs.utexas.edu/~EWD/transcripti</span><span class=\"invisible\">ons/EWD10xx/EWD1036.html</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://fosstodon.org/tags/dijkstra",
"name": "#dijkstra"
}
],
"replies": {
"id": "https://fosstodon.org/users/emilis/statuses/109507005723728786/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://fosstodon.org/users/emilis/statuses/109507005723728786/replies?only_other_accounts=true&page=true",
"partOf": "https://fosstodon.org/users/emilis/statuses/109507005723728786/replies",
"items": []
}
},
"likes": {
"id": "https://fosstodon.org/users/emilis/statuses/109507005723728786/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://fosstodon.org/users/emilis/statuses/109507005723728786/shares",
"type": "Collection",
"totalItems": 0
}
}