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://masto.ai/users/ide/statuses/109383823690550692",
"type": "Note",
"summary": null,
"inReplyTo": "https://ruhr.social/users/bigmike/statuses/109383636016726132",
"published": "2022-11-21T21:04:52Z",
"url": "https://masto.ai/@ide/109383823690550692",
"attributedTo": "https://masto.ai/users/ide",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://masto.ai/users/ide/followers",
"https://ruhr.social/users/bigmike"
],
"sensitive": false,
"atomUri": "https://masto.ai/users/ide/statuses/109383823690550692",
"inReplyToAtomUri": "https://ruhr.social/users/bigmike/statuses/109383636016726132",
"conversation": "tag:ruhr.social,2022-11-21:objectId=14598316:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ruhr.social/@bigmike\" class=\"u-url mention\">@<span>bigmike</span></a></span> The only reason you'd *have to* use one of them is if there is some technical limitation, but in that case the interpreter should inform you accordingly.</p><p>E.g. you can't hash a list/set as they are mutable, you can't mutate a tuple, you can't slice or order a set.</p><p>Now there are some cases where one is more efficient, but this only comes into play when dealing with huge collections and even then it follows basic data structure logic (e.g. sets are most efficient for membership tests)</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ruhr.social/@bigmike\" class=\"u-url mention\">@<span>bigmike</span></a></span> The only reason you'd *have to* use one of them is if there is some technical limitation, but in that case the interpreter should inform you accordingly.</p><p>E.g. you can't hash a list/set as they are mutable, you can't mutate a tuple, you can't slice or order a set.</p><p>Now there are some cases where one is more efficient, but this only comes into play when dealing with huge collections and even then it follows basic data structure logic (e.g. sets are most efficient for membership tests)</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://ruhr.social/users/bigmike",
"name": "@bigmike@ruhr.social"
}
],
"replies": {
"id": "https://masto.ai/users/ide/statuses/109383823690550692/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://masto.ai/users/ide/statuses/109383823690550692/replies?only_other_accounts=true&page=true",
"partOf": "https://masto.ai/users/ide/statuses/109383823690550692/replies",
"items": []
}
}
}