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.social/users/rreisman/statuses/109332498899749915/activity",
"type": "Create",
"actor": "https://mastodon.social/users/rreisman",
"published": "2022-11-12T19:32:18Z",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.social/users/rreisman/followers",
"https://techpolicy.social/users/mchris"
],
"object": {
"id": "https://mastodon.social/users/rreisman/statuses/109332498899749915",
"type": "Note",
"summary": null,
"inReplyTo": "https://techpolicy.social/users/mchris/statuses/109331765035212998",
"published": "2022-11-12T19:32:18Z",
"url": "https://mastodon.social/@rreisman/109332498899749915",
"attributedTo": "https://mastodon.social/users/rreisman",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.social/users/rreisman/followers",
"https://techpolicy.social/users/mchris"
],
"sensitive": false,
"atomUri": "https://mastodon.social/users/rreisman/statuses/109332498899749915",
"inReplyToAtomUri": "https://techpolicy.social/users/mchris/statuses/109331765035212998",
"conversation": "tag:techpolicy.social,2022-11-12:objectId=9077:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://techpolicy.social/@mchris\" class=\"u-url mention\">@<span>mchris</span></a></span> To Chris's comment, I would add that architectures do best separating where friction and scale fit and where not. The communication backbone scales, moderation does not. Some possible alternative architectures are suggested here: <a href=\"https://ucm.teleshuttle.com/2021/11/resolving-speech-biz-model-and-privacy.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">ucm.teleshuttle.com/2021/11/re</span><span class=\"invisible\">solving-speech-biz-model-and-privacy.html</span></a></p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://techpolicy.social/@mchris\" class=\"u-url mention\">@<span>mchris</span></a></span> To Chris's comment, I would add that architectures do best separating where friction and scale fit and where not. The communication backbone scales, moderation does not. Some possible alternative architectures are suggested here: <a href=\"https://ucm.teleshuttle.com/2021/11/resolving-speech-biz-model-and-privacy.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">ucm.teleshuttle.com/2021/11/re</span><span class=\"invisible\">solving-speech-biz-model-and-privacy.html</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://techpolicy.social/users/mchris",
"name": "@mchris@techpolicy.social"
}
],
"replies": {
"id": "https://mastodon.social/users/rreisman/statuses/109332498899749915/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.social/users/rreisman/statuses/109332498899749915/replies?only_other_accounts=true&page=true",
"partOf": "https://mastodon.social/users/rreisman/statuses/109332498899749915/replies",
"items": []
}
},
"likes": {
"id": "https://mastodon.social/users/rreisman/statuses/109332498899749915/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://mastodon.social/users/rreisman/statuses/109332498899749915/shares",
"type": "Collection",
"totalItems": 2
}
}
}