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://ipv6.social/users/litchralee_v6/statuses/114060020162728758",
"type": "Note",
"summary": null,
"inReplyTo": "https://masto.ai/users/BotFodder/statuses/114059184399124704",
"published": "2025-02-24T17:23:08Z",
"url": "https://ipv6.social/@litchralee_v6/114060020162728758",
"attributedTo": "https://ipv6.social/users/litchralee_v6",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://ipv6.social/users/litchralee_v6/followers",
"https://masto.ai/users/BotFodder"
],
"sensitive": false,
"atomUri": "https://ipv6.social/users/litchralee_v6/statuses/114060020162728758",
"inReplyToAtomUri": "https://masto.ai/users/BotFodder/statuses/114059184399124704",
"conversation": "tag:masto.ai,2025-02-24:objectId=240908571:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://masto.ai/@BotFodder\" class=\"u-url mention\">@<span>BotFodder</span></a></span> My homelab experiments are drafted in Ansible scripts, where the <a href=\"https://ipv6.social/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> prefix is drawn from a single file. That way, when I deploy, I can easily replace the prefix with the real one.</p><p>To that end, for initial testing, I randomly generate a suitably-sized prefix from my home's /48. IMO, the documentation prefix is only for writing example deployments, to be substituted in just prior to publishing. ULAs have too many hurdles to stand in lieu of GLAs.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://masto.ai/@BotFodder\" class=\"u-url mention\">@<span>BotFodder</span></a></span> My homelab experiments are drafted in Ansible scripts, where the <a href=\"https://ipv6.social/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> prefix is drawn from a single file. That way, when I deploy, I can easily replace the prefix with the real one.</p><p>To that end, for initial testing, I randomly generate a suitably-sized prefix from my home's /48. IMO, the documentation prefix is only for writing example deployments, to be substituted in just prior to publishing. ULAs have too many hurdles to stand in lieu of GLAs.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://masto.ai/users/BotFodder",
"name": "@BotFodder@masto.ai"
},
{
"type": "Hashtag",
"href": "https://ipv6.social/tags/ipv6",
"name": "#ipv6"
}
],
"replies": {
"id": "https://ipv6.social/users/litchralee_v6/statuses/114060020162728758/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://ipv6.social/users/litchralee_v6/statuses/114060020162728758/replies?only_other_accounts=true&page=true",
"partOf": "https://ipv6.social/users/litchralee_v6/statuses/114060020162728758/replies",
"items": []
}
},
"likes": {
"id": "https://ipv6.social/users/litchralee_v6/statuses/114060020162728758/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://ipv6.social/users/litchralee_v6/statuses/114060020162728758/shares",
"type": "Collection",
"totalItems": 0
}
}