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://discuss.systems/users/ocratato/statuses/113071624612854012",
"type": "Note",
"summary": null,
"inReplyTo": "https://mastodon.social/users/lutzhuehnken/statuses/113068463879916231",
"published": "2024-09-03T04:01:08Z",
"url": "https://discuss.systems/@ocratato/113071624612854012",
"attributedTo": "https://discuss.systems/users/ocratato",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://discuss.systems/users/ocratato/followers",
"https://mastodon.social/users/lutzhuehnken"
],
"sensitive": false,
"atomUri": "https://discuss.systems/users/ocratato/statuses/113071624612854012",
"inReplyToAtomUri": "https://mastodon.social/users/lutzhuehnken/statuses/113068463879916231",
"conversation": "tag:mastodon.social,2024-09-01:objectId=789130130:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.social/@lutzhuehnken\" class=\"u-url mention\">@<span>lutzhuehnken</span></a></span> OK, I am beginning to understand our different views. I can see some attraction in loosely coupled databases - up to the point where you want a reliable system.</p><p>Its been my experience that any data item whose value is an integration of changes is inevitably a point of failure. An entire database holding an integration of the events doesn't bare thinking about.</p><p>Perhaps a more concrete example would help.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.social/@lutzhuehnken\" class=\"u-url mention\">@<span>lutzhuehnken</span></a></span> OK, I am beginning to understand our different views. I can see some attraction in loosely coupled databases - up to the point where you want a reliable system.</p><p>Its been my experience that any data item whose value is an integration of changes is inevitably a point of failure. An entire database holding an integration of the events doesn't bare thinking about.</p><p>Perhaps a more concrete example would help.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://mastodon.social/users/lutzhuehnken",
"name": "@lutzhuehnken@mastodon.social"
}
],
"replies": {
"id": "https://discuss.systems/users/ocratato/statuses/113071624612854012/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://discuss.systems/users/ocratato/statuses/113071624612854012/replies?only_other_accounts=true&page=true",
"partOf": "https://discuss.systems/users/ocratato/statuses/113071624612854012/replies",
"items": []
}
},
"likes": {
"id": "https://discuss.systems/users/ocratato/statuses/113071624612854012/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://discuss.systems/users/ocratato/statuses/113071624612854012/shares",
"type": "Collection",
"totalItems": 0
}
}