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://infosec.exchange/users/resingm/statuses/110859985936879902",
"type": "Note",
"summary": null,
"inReplyTo": "https://infosec.exchange/users/resingm/statuses/110859584543541646",
"published": "2023-08-09T13:52:20Z",
"url": "https://infosec.exchange/@resingm/110859985936879902",
"attributedTo": "https://infosec.exchange/users/resingm",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/resingm/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/resingm/statuses/110859985936879902",
"inReplyToAtomUri": "https://infosec.exchange/users/resingm/statuses/110859584543541646",
"conversation": "tag:infosec.exchange,2023-08-09:objectId=85854374:objectType=Conversation",
"content": "<p>Update #2 </p><p>IPv6 only is working rather easy and flawlessly thanks to nat64.net. However, the <a href=\"https://infosec.exchange/tags/docker\" class=\"mention hashtag\" rel=\"tag\">#<span>docker</span></a> <a href=\"https://infosec.exchange/tags/network\" class=\"mention hashtag\" rel=\"tag\">#<span>network</span></a> configuration is a different story. I can't find an easy solution to enforce <a href=\"https://infosec.exchange/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> in docker. Documentation is limited and the Internet suggests multiple different angles at it.</p><p>Postponing the docker network setup for now. My service is online for now :)</p>",
"contentMap": {
"en": "<p>Update #2 </p><p>IPv6 only is working rather easy and flawlessly thanks to nat64.net. However, the <a href=\"https://infosec.exchange/tags/docker\" class=\"mention hashtag\" rel=\"tag\">#<span>docker</span></a> <a href=\"https://infosec.exchange/tags/network\" class=\"mention hashtag\" rel=\"tag\">#<span>network</span></a> configuration is a different story. I can't find an easy solution to enforce <a href=\"https://infosec.exchange/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> in docker. Documentation is limited and the Internet suggests multiple different angles at it.</p><p>Postponing the docker network setup for now. My service is online for now :)</p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/docker",
"name": "#docker"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/network",
"name": "#network"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ipv6",
"name": "#ipv6"
}
],
"replies": {
"id": "https://infosec.exchange/users/resingm/statuses/110859985936879902/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/resingm/statuses/110859985936879902/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/resingm/statuses/110859985936879902/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/resingm/statuses/110859985936879902/likes",
"type": "Collection",
"totalItems": 2
},
"shares": {
"id": "https://infosec.exchange/users/resingm/statuses/110859985936879902/shares",
"type": "Collection",
"totalItems": 0
}
}