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",
"litepub": "http://litepub.social/ns#",
"directMessage": "litepub:directMessage",
"Hashtag": "as:Hashtag"
}
],
"id": "https://mastodon.thi.ng/users/toxi/statuses/114069677313552098",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2025-02-26T10:19:04Z",
"url": "https://mastodon.thi.ng/@toxi/114069677313552098",
"attributedTo": "https://mastodon.thi.ng/users/toxi",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.thi.ng/users/toxi/followers"
],
"sensitive": false,
"atomUri": "https://mastodon.thi.ng/users/toxi/statuses/114069677313552098",
"inReplyToAtomUri": null,
"conversation": "tag:mastodon.thi.ng,2025-02-26:objectId=1510168:objectType=Conversation",
"content": "<p>Anyone knows why the HTML versions of IETF RFCs are insisting on replicating the (unnecessary) page breaks from the plain text version? Also apart from being able to jump to bibliography and to document sections from the TOC, why aren't the HTML versions making proper use of internal hyperlinking? Feels like a grand missed opportunity to make these specs a lot more usable? Especially hard to use when trying to implement vs just using an RFC for a quick consult/check...</p><p><a href=\"https://mastodon.thi.ng/tags/RFC\" class=\"mention hashtag\" rel=\"tag\">#<span>RFC</span></a> <a href=\"https://mastodon.thi.ng/tags/IETF\" class=\"mention hashtag\" rel=\"tag\">#<span>IETF</span></a> <a href=\"https://mastodon.thi.ng/tags/HyperText\" class=\"mention hashtag\" rel=\"tag\">#<span>HyperText</span></a></p>",
"contentMap": {
"en": "<p>Anyone knows why the HTML versions of IETF RFCs are insisting on replicating the (unnecessary) page breaks from the plain text version? Also apart from being able to jump to bibliography and to document sections from the TOC, why aren't the HTML versions making proper use of internal hyperlinking? Feels like a grand missed opportunity to make these specs a lot more usable? Especially hard to use when trying to implement vs just using an RFC for a quick consult/check...</p><p><a href=\"https://mastodon.thi.ng/tags/RFC\" class=\"mention hashtag\" rel=\"tag\">#<span>RFC</span></a> <a href=\"https://mastodon.thi.ng/tags/IETF\" class=\"mention hashtag\" rel=\"tag\">#<span>IETF</span></a> <a href=\"https://mastodon.thi.ng/tags/HyperText\" class=\"mention hashtag\" rel=\"tag\">#<span>HyperText</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://mastodon.thi.ng/tags/rfc",
"name": "#rfc"
},
{
"type": "Hashtag",
"href": "https://mastodon.thi.ng/tags/ietf",
"name": "#ietf"
},
{
"type": "Hashtag",
"href": "https://mastodon.thi.ng/tags/hypertext",
"name": "#hypertext"
}
],
"replies": {
"id": "https://mastodon.thi.ng/users/toxi/statuses/114069677313552098/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.thi.ng/users/toxi/statuses/114069677313552098/replies?only_other_accounts=true&page=true",
"partOf": "https://mastodon.thi.ng/users/toxi/statuses/114069677313552098/replies",
"items": []
}
},
"likes": {
"id": "https://mastodon.thi.ng/users/toxi/statuses/114069677313552098/likes",
"type": "Collection",
"totalItems": 4
},
"shares": {
"id": "https://mastodon.thi.ng/users/toxi/statuses/114069677313552098/shares",
"type": "Collection",
"totalItems": 1
}
}